You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The current setup process for Evershop requires manual input of configuration values such as DB_HOST,DB_port,etc for setting up database when running the installation script. This manual input process complicates automation, particularly in continuous integration (CI) workflows using GitHub Actions. Without a streamlined approach to automate the setup process within GitHub Actions, maintaining consistent integration pipelines becomes challenging.
Describe the solution you'd like
I propose implementing GitHub Actions workflow to automate the installation process. This would involve modifying the workflow to prompt for necessary configuration values as secrets or environment variables, allowing for a seamless setup without manual intervention.
Describe alternatives you've considered
One alternative is to continue using manual input for setup, but this approach is prone to errors and is not scalable, especially in CI/CD environments. Another option is to automate the setup using a separate script within the repository integrating the script into the GitHub Actions workflow.
Additional context
By combining setup automation with automated testing within GitHub Actions, we can create a robust integration pipeline that not only accelerates the integration process but also enhances the reliability and stability of our software.
The text was updated successfully, but these errors were encountered:
Hey @treoden , can you update the installation script to automate prompting values for DB_HOST, DB_PORT, DB_NAME, etc instead of manually giving the values?
Is your feature request related to a problem? Please describe.
The current setup process for Evershop requires manual input of configuration values such as DB_HOST,DB_port,etc for setting up database when running the installation script. This manual input process complicates automation, particularly in continuous integration (CI) workflows using GitHub Actions. Without a streamlined approach to automate the setup process within GitHub Actions, maintaining consistent integration pipelines becomes challenging.
Describe the solution you'd like
I propose implementing GitHub Actions workflow to automate the installation process. This would involve modifying the workflow to prompt for necessary configuration values as secrets or environment variables, allowing for a seamless setup without manual intervention.
Describe alternatives you've considered
One alternative is to continue using manual input for setup, but this approach is prone to errors and is not scalable, especially in CI/CD environments. Another option is to automate the setup using a separate script within the repository integrating the script into the GitHub Actions workflow.
Additional context
By combining setup automation with automated testing within GitHub Actions, we can create a robust integration pipeline that not only accelerates the integration process but also enhances the reliability and stability of our software.
The text was updated successfully, but these errors were encountered: