Back
Similar todos
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
Automatically store timestamped copies of environment variables for each change through the UI since I read someone was concerned about this in Laravel Forge #shipnix
review dev environment 
#thundercontent
Explore how to enable staging environments with promising results #shipnix
Get working staging environment for #shipnix up and running, using #shipnix
add env vars for standardized devops 
#buildingo
Set up preliminary view for creating and pushing server configuration to Github repo #shipnix
Make plans and research to tighten security for generated ssh keys before letting more test users in #shipnix
Write docs for how to make an exisiting project #shipnix compliant and let testers know docs.ship-nix.com/docs/ship-n…
Have more information and actions available when running a deploy event #shipnix
Write documentation and explore how to differentiate between a production and a staging environment in a configuration.nix #shipnix
Work on a node.js dev environment #shipnix
Setup dev environment for #shipnix on new laptop so I can continue working while travelling
Write documentation for safely adding SSH host keys for custom git providers on production servers #shipnix
Trim whitespace from deploy key so no illegal characters are shipped from the shell output #shipnix