Replies: 3 comments 2 replies
-
I've only ever seen this when a user thinks they are referencing one app but actually are pushing to another app. Can you verify that you don't have two slightly mis-named apps by running |
Beta Was this translation helpful? Give feedback.
-
Yes, that seems to have been the case (they had the wrong git remote)!
I'm waiting for confirmation.
I was VERY surprised that attempting a push without a preexisting app
(ie; created w/ apps:create) succeeds!! I just tested that a push to
"zzz" works without a pre-existing zzz app.
|
Beta Was this translation helpful? Give feedback.
-
Thanks for your help! |
Beta Was this translation helpful? Give feedback.
-
I've been using Dokku for a couple of years, and ran into two app configuration issues in two days:
Both of the following were seen under dokku version 0.34.9:
The first is that when running a shell script I wrote to apply configuration via
config:set
for a Django app and then git push the code, is that for one user, the configuration isn't present in the environment. and runningmanage.py collectstatic
fails. Usingdocker exec
to run a shell in the build container, the config is not in the environment, and there is a /app/.env file, also missing the config. When I run the script, the configuration is present, andcollectstatic
runs. [disclaimer: we have not (yet) tried to have the other developer run the script again, tho they will tomorrow, but they had run it MANY times before I ran it]The second is that an app (launched with the above script), new config was not taking effect, and I'm seeing a
/app/.env
file with old configuration, and newlyconfig:set
config present in the environment. In this case, I can see that perhaps our app should detect it's running under Dokku, and ignore the .env file.TIA
Beta Was this translation helpful? Give feedback.
All reactions