Is Your Feature Request Related to a Problem? Please Describe.
Yes, the application's flexibility in a self-hosted environment can be enhanced. While deploying it in self-hosted environment, there is no feature that would allow the user to set password and passphrase generation rules via environment variables. This limitation requires manual interaction for each password generation, which can be cumbersome for batch operations or when aiming for consistency across deployments.
Describe the Solution You'd Like
I would like the application to support the usage of environment variables in the Docker run command to control the password and passphrase settings as defaults. For example, allowing settings like docker run -d -e INCLUDE_DIGITS=true to be used for both passwords and passphrases. This enhancement would streamline the process of setting defaults for password generation, particularly in environments where automation and configuration management tools are utilized.
Describe Alternatives You've Considered
A workaround involves manually configuring each password or passphrase upon generation. However, this approach is not scalable and does not leverage the automation capabilities inherent in containerized environments.
Additional Context
The software utilizes Docker and already supports an environment variable for disabling API checks (NO_API_CHECK). Extending this configuration approach to include password generation settings would significantly improve usability and deployment flexibility.
User Story
As a self-hosted environment administrator, I want to define default settings for password and passphrase generation using environment variables, so that I can automate and standardize the deployment process across different setups.
Acceptance Criteria
Users can set default password and passphrase generation settings using environment variables when running the Docker container.
The application reads these environment variables at startup and applies the specified settings as defaults for password and passphrase generation.
Documentation is updated to include a list of supported environment variables and examples of how to use them.
Implementation Notes
This feature requires adding logic to read and apply settings from environment variables during application startup.
Care should be taken to validate environment variable values to ensure they conform to expected formats and ranges.
Potential Challenges
Ensuring that the application's behavior remains predictable and secure when defaults are overridden via environment variables.
Providing clear documentation on how to use and set these environment variables correctly.
Is Your Feature Request Related to a Problem? Please Describe.
Yes, the application's flexibility in a self-hosted environment can be enhanced. While deploying it in self-hosted environment, there is no feature that would allow the user to set password and passphrase generation rules via environment variables. This limitation requires manual interaction for each password generation, which can be cumbersome for batch operations or when aiming for consistency across deployments.
Describe the Solution You'd Like
I would like the application to support the usage of environment variables in the Docker run command to control the password and passphrase settings as defaults. For example, allowing settings like
docker run -d -e INCLUDE_DIGITS=trueto be used for both passwords and passphrases. This enhancement would streamline the process of setting defaults for password generation, particularly in environments where automation and configuration management tools are utilized.Describe Alternatives You've Considered
A workaround involves manually configuring each password or passphrase upon generation. However, this approach is not scalable and does not leverage the automation capabilities inherent in containerized environments.
Additional Context
The software utilizes Docker and already supports an environment variable for disabling API checks (
NO_API_CHECK). Extending this configuration approach to include password generation settings would significantly improve usability and deployment flexibility.User Story
As a self-hosted environment administrator, I want to define default settings for password and passphrase generation using environment variables, so that I can automate and standardize the deployment process across different setups.
Acceptance Criteria
Implementation Notes
Potential Challenges
Priority
Medium
Labels
enhancement, usability, Backend, Docker
Other
Origin: https://www.reddit.com/r/selfhosted/comments/1bozfo9/comment/kx8sqod/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button