Back
Similar todos
Make it possible to review and modify environment variables before migrating existing code to a new server #shipnix
Let users review environment variables before deploying an exisiting project #shipnix
MVP manage environment variables from server dashboard #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
Setup dev environment for #shipnix on new laptop so I can continue working while travelling
Get working staging environment for #shipnix up and running, using #shipnix
Add toggle for auto-deploying after updating environment variables, using HTMX instead of Elm or JavaScript for the first time #shipnix
Make big breaking changes while I can, and move environment file folder to be /etc/ship-nix instead of living in home folder #shipnix
Successfully deploy a test instance of ship-nix #shipnix
Slightly improve provisioning time with easy fix #shipnix
Work on a node.js dev environment #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
Work on provisioning and shipping #shipnix with it's own software
Fight with shell scripting intricacies, but finally be able to provision a server and right after perform actions on the server programmatically #shipnix
Programmatically provision a NixOS server from web dashboard #shipnix
Explore how to enable staging environments with promising results #shipnix
Make ship-nix starters firewall only open the ports they actually need #shipnix
First steps in moving #shipnix into production
Fix persistent user sessions on #shipnix and it's IHP boilerplate