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
Once we have a working container for the app (#26), we should add a docker-compose.yml file that spins up the Shiny app container and configures the necessary environment variables to run the app on the GAE.
Set up docker-compose.yml
Add .env file to configure the necessary environment variables
.env should be added to .gitignore to avoid exposing secrets
Have a .env.sample file that acts like a template
Testing
No response
Documentation
Document which environment variables need to be defined to run the service
Once we have a working container for the app (#26), we should add a docker-compose.yml file that spins up the Shiny app container and configures the necessary environment variables to run the app on the GAE.
Set up docker-compose.yml
Add .env file to configure the necessary environment variables
.env should be added to .gitignore to avoid exposing secrets
Have a .env.sample file that acts like a template
Testing
No response
Documentation
Document which environment variables need to be defined to run the service
💭 If we want to be fancy, could have a self-hosted GHA runner on the GAE that automatically redeploys the app when a new release is created. Though not sure i self-hosted runners are an option on GAE.
Definition of Done / Acceptance Criteria
Once we have a working container for the app (#26), we should add a
docker-compose.yml
file that spins up the Shiny app container and configures the necessary environment variables to run the app on the GAE.docker-compose.yml
.env
file to configure the necessary environment variables.env
should be added to.gitignore
to avoid exposing secrets.env.sample
file that acts like a templateTesting
No response
Documentation
Dependencies
Details and Comments
No response
The text was updated successfully, but these errors were encountered: