Improve Interactive Setup with Environment Variables and Startup Commands

[finneh4249]

Currently, the interactive setup process for Aometry is limited in its ability to handle different environments (e.g., development, production). This issue proposes enhancing the setup to allow for the creation of environment-specific variables and startup commands.

Proposed Changes:

Environment Variables:

• [ ] Modify the setup to generate different .env files for various environments (e.g., .env.production.local, .env.local).
• [ ] Allow users to specify values for environment-specific variables during the interactive setup.
• [ ]

Startup Commands:

• [ ] Create new startup commands that target specific environments based on the corresponding .env file (e.g., npm run start:production, npm run start:local).

Re-run Setup:

• [ ] Add an option to re-run the interactive setup.
• [ ] When re-running, clear any existing .env files and regenerate them based on user input.

Benefits:

• Improved flexibility for managing different environments.
• Simplified workflow for switching between environments.
• Easier setup and configuration for developers.

Example Usage:

# Run the interactive setup
npm run setup

# Start the application in production mode
npm run start:production

# Start the application in local development mode
npm run start:local