I’m now ‘in the flow’ developing locally and pushing to the server… all according to Biff’s dark plan. Bwahaha. Never had more fun. Is there any clever way to push to a staging/“QA” server before prod using the soft-deploy command? Sometimes things glitch on the server that don’t locally and I’d like to be able to check things.
hmm... the easiest way, though not necessarily the cleanest way, would probably be to copy config.env to two separate files: config.prod.env and config.staging.env . in , edit DOMAIN to the domain for your staging server. Then when you want to deploy to staging, do cp config.staging.env config.env; clj -M:dev soft-deploy and vice-versa.
for convenience you could make a custom task in dev/tasks.clj like soft-deploy-staging that sets config.env to the staging config, runs the normal soft-deploy command, then sets config.env back to config.prod.env.
That would work! I’ll play with those scenarios. Thanks!