Automated Environment Variable Management

[SiFuMax09]

Managing environment variables manually can be error-prone and insecure, especially when handling sensitive credentials such as database passwords, API keys, and service configurations. This feature request proposes that Vito Deploy fully automate the management of environment variables, eliminating the need for developers to manually edit .env files.

Just like its in laravel cloud

How It Works:

• When a user creates a new database, storage bucket, or external service integration, Vito Deploy should automatically generate secure credentials and write them directly into the appropriate .env variable.
• The system should ensure that all environment variables are securely stored and managed, reducing human error and enhancing security.
• Developers should never have to manually copy, edit, or expose environment variables, ensuring a seamless and secure deployment experience.

Key Benefits:

• Enhanced Security: Credentials are never manually copied or exposed.
• Reduced Human Error: No risk of misconfiguration due to manual edits.
• Streamlined Deployment: Developers can focus on coding without worrying about environment setup.
• Zero Manual Intervention: Vito Deploy handles everything behind the scenes automatically.

By implementing this feature, Vito Deploy would provide a more efficient, secure, and developer-friendly workflow for managing environment variables.

[eznix86]

environment injection is nice, but i think most of us want to have control over what we are doing, but i think it's a good idea, i believe maybe, the environments are injected but has a padlock on it, if it is unlocked it is copied to the .env, letting you do whatever you want with it !