Back
Similar todos
Let users review environment variables before deploying an exisiting project #shipnix
Make it possible to review and modify environment variables before migrating existing code to a new server #shipnix
MVP manage environment variables from server dashboard #shipnix
Properly load environment variables via systemd #shipnix
Add toggle for auto-deploying after updating environment variables, using HTMX instead of Elm or JavaScript for the first time #shipnix
Create default ship_env file on all new server starters that stores information on whether the server environment is production, stage or something else #shipnix
Require users with MFA enabled to enter OTP before accessing environment variables #shipnix
Remove old ENV vars that have since moved to Rails credentials 
#startupjobs
set environment vars for sentry.io on Heroku
✏️ I wrote about environment variables and dotenv files micro.webology.dev/2024/03/13…
Add beautiful timestamps to build log lines #shipnix
fix a bug when env variables became duplicated instead of updated by launching the deployment via API
Implement zero downtime deployment for Laravel Forge gist.github.com/osbre/a7bec19…
implementing system-variables, so that users don't have to copy configs everywhere @ 
#steadyapp
split local and prod environment variable management tools (boring but had to do) 
#skillmap
Sharing .env variables between my laptops 
#supernuxt
Update README with all env vars #wip2slack