feat: add --file option to shipnode env command

Allows uploading a specific .env file instead of the default from config.

Author: devalade

src/cli/commands/env.ts

@@ -6,18 +6,19 @@ import { ui } from '../ui.js';
 
 export async function cmdEnv(
   cwd: string,
-  options: { config?: string },
+  options: { file?: string; config?: string },
 ): Promise<void> {
   await runRemoteCommand(
     cwd,
     async ({ config, executor }) => {
-      const localEnvPath = resolve(cwd, config.envFile);
+      const envFile = options.file ?? config.envFile;
+      const localEnvPath = resolve(cwd, envFile);
 
       if (!(await pathExists(localEnvPath))) {
-        throw new Error(`Environment file not found: ${config.envFile}`);
+        throw new Error(`Environment file not found: ${envFile}`);
       }
 
-      ui.info(`Uploading ${config.envFile} to server...`);
+      ui.info(`Uploading ${envFile} to server...`);
 
       const content = await readFile(localEnvPath);
       const b64 = content.toString('base64');

src/cli/commands/help.ts

@@ -20,7 +20,7 @@ ${chalk.bold('RELEASE MANAGEMENT')}
   ${chalk.green('migrate')}           Migrate existing deploy to zero-downtime structure
 
 ${chalk.bold('ENVIRONMENT')}
-  ${chalk.green('env')}               Upload local .env file to the server
+  ${chalk.green('env')} [--file <p>]   Upload local .env file to the server
   ${chalk.green('run')} <cmd>         Run a one-off command on the production server
 
 ${chalk.bold('PROCESS MANAGEMENT')}

src/cli/index.ts

@@ -88,6 +88,7 @@ program
 program
   .command('env')
   .description('Upload local .env file to the server')
+  .option('--file <path>', 'Path to .env file to upload (default: .env from config)')
   .option('--config <path>', 'Use a specific config file')
   .action((opts) => cmdEnv(process.cwd(), opts));