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
Following #896, it's time to update our setup script to use 🐳 Docker based deployment. This has many benefits among them easier and more stable upgrades (always using updated dependencies) and more standard setup across different platforms.
New setup script
Once we move to use Docker, the setup script will do:
Install Docker & Docker Compose.
Download docker-compose.yml file and other supporting files.
Start services.
Done.
New upgrade script
The upgrade script will probably be something along the lines of:
Get latest version Docker image tag reference.
Update docker-compose.yml.
Rebuild services.
Stop services.
Apply migrations if needed.
Start services.
Documentation
Will have to update documentation accordingly. Mainly:
While controlling, checking logs, etc, can be done with the docker-compose command we should consider streamlining the process with a single control script.
I'm not 100% sure this is needed, but it can improve end user (admin) experience. On the otherhand, it makes the knowledge less portable.
This is an outline of the work required and some initial thoughts. Any feedback is welcome. Specially from users who already use Docker/Docker Compose for their Redash deployment.
The text was updated successfully, but these errors were encountered:
Following #896, it's time to update our setup script to use 🐳 Docker based deployment. This has many benefits among them easier and more stable upgrades (always using updated dependencies) and more standard setup across different platforms.
New setup script
Once we move to use Docker, the setup script will do:
docker-compose.yml
file and other supporting files.New upgrade script
The upgrade script will probably be something along the lines of:
docker-compose.yml
.Documentation
Will have to update documentation accordingly. Mainly:
Control script
While controlling, checking logs, etc, can be done with the
docker-compose
command we should consider streamlining the process with a single control script.I'm not 100% sure this is needed, but it can improve end user (admin) experience. On the otherhand, it makes the knowledge less portable.
This is an outline of the work required and some initial thoughts. Any feedback is welcome. Specially from users who already use Docker/Docker Compose for their Redash deployment.
The text was updated successfully, but these errors were encountered: