It’s possible. Ensure the migration folder is copied to the Nostream container, and change the entrypoint so knex migrations command is run right before Nostream is run and you’ll be good to go.
nostr:npub1qqqqqqyz0la2jjl752yv8h7wgs3v098mh9nztd4nr6gynaef6uqqt0n47m or nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj is there any way to run nostream entirely off of pre-baked docker images?
I see this, and it seems to work, but I notice that it’s missing the migrations service. Is that strictly necessary? What happens if that service isn’t there? Help this smooth brain understand!
https://github.com/vimagick/dockerfiles/blob/master/nostream/docker-compose.yml
For context my goal is to run all my services across all my hosts from Portainer—it makes things so much simpler and easier for me to see what’s going on (again, smooth brain), and I can’t manage a container in Portainer that wasn’t created by Portainer.
#asknostr
Discussion
So this is where I reveal how smooth my brain really is but… how can I tell whether the jorijn/nostream image is doing that?
This is the repo that said image is built from; a fork of yours. Would the answer be in one of these files?
It’s not doing that. I’ve checked.
You can get around it by running the migrations once manually yourself: clone the repo, ensure the knexfile.js file has the credentials to connect to your PostgreSQL database instance, and run the knex migrate command.
The migrations create the tables Nostream needs to operate.
I recommend you run nostr-rs-relay instead of Nostream because it will be easier for your Portainer workflow.