##// END OF EJS Templates
rcstack: remove dependency for md5sum, this allows to run on macOS
rcstack: remove dependency for md5sum, this allows to run on macOS

File last commit:

r155:de27f912
r271:5cedb0ae
Show More
migration-to-docker.md
54 lines | 1.7 KiB | text/x-minidsrc | MarkdownLexer
/ docs / migration-to-docker.md

Quick list of actions to migrate old pre 4.28.0 installer based releases to docker stack

1. Decide on components use

By default, RhodeCode stack uses Redis and Postgres.
We recommend using those in Docker as things like
backup/restore are much easier, and possible to run by our installer

If you plan to use your own redis or DB, uncomment/disable those services in file:
docker-compose-services.override.yaml

Select your DB type by commenting postgres or mysql db in docker-compose-services.override.yaml
For Sqlite, comment out both DB types

2. launch stack based on get started

Run a quick start guide based on ./rcstack get-started

3. Copy over your old configuration into new shared config dir

cp rhodecode.ini to config/_shared/rhodecode_old.ini
cp vcsserver.ini to config/_shared/vcsserver_old.ini

Then compare the new files and adjust accordingly, most important are location of storages/redis/db connection
urls

4. make a db dump

If docker-based DB is selected
create a backup of your existing database, so it can be migrated to docker instance.
If you plan to use you old running DB, this step can be ommitted.
Adjust rhodecode.ini to point your docker rhodecode to old DB

5. restore db

If docker-based DB is selected
Restore the database into docker container running DB

mv repositories data to .custom/storage

mv gists data to .custom/storage

mv artifacts data to .custom/storage

mv tarball cache data to .custom/storage

./rcstack cli storage

move repos to /vol/repovolume

move artifacts data to /vol/datavolume

move tarballcache data to /vol/datavolume

cp rhodecode.ini to config/_shared/rhodecode.ini

cp vcsserver.ini to config/_shared/vcsserver.ini