11 Replies
Nope. They have to be rebuilt/redeployed. If you have a lengthy build process, you should build the image and push it to a registry instead. That makes it faster to switch to a new one
thank you!
might be possible if we use
.env then you can stop and start your container. try if this works
No it does not work. You have to do
docker compose up command for that to take effect. Start and stop will not change the variableok then i might be wrong
I was a bit unsure about that case, so I just tested it
But env file isn't something that would work with Dokploy? Where should we put it?
I have see few templates using env_file for example plausible
so i thought if thats added then there must be some usecase within dokploy
you should put that in the raw compose
You're absolutly rigth. I took a look at the source and indeed it builds a
.env file. I didn't know that.here's a test file which i found might be useful
https://github.com/Dokploy/dokploy/blob/0a6382a731a901e57830235a27b8fe00426e9333/apps/dokploy/__test__/compose/compose.test.ts#L411
That will be quite usefull for a few projects. Learn something new every day
yeah, even i do explore and learning slowly