altf4arnold/datatracker
1
0
Fork 0
Code Issues Pull requests Actions 3 Packages Projects Releases Wiki Activity
datatracker/docker
History
Lars Eggert dec56ffb96 Merge my bs5 changes over. 
There is definitely still quite some breakage, my main focus during
the conflict resolution was not to drop any changes made by others.
 - Legacy-Id: 19632
2021-11-11 13:09:23 +00:00
..
build MacOS X fix from Mark Donnelly 2021-10-15 13:56:44 +00:00
copydb MacOS X fix from Mark Donnelly 2021-10-15 13:56:44 +00:00
docker-init.sh Merged in [19541] from lars@eggert.org: 2021-11-08 17:55:12 +00:00
Dockerfile Merge my bs5 changes over. 2021-11-11 13:09:23 +00:00
README.md Update docker/README.md to reflect the merge of Lars' branch. Commit ready for merge. 2021-11-09 11:52:50 +00:00
rsync-extras MacOS X fix from Mark Donnelly 2021-10-15 13:56:44 +00:00
run Make Cygwin tests work again 2021-10-20 18:14:52 +00:00
settings_local.py Improve proceedings display with new title block, configurable host logos, and additional PDF or URL materials. Fixes #3147. Commit ready for merge. 2021-08-30 17:02:49 +00:00
updatedb MacOS X fix from Mark Donnelly 2021-10-15 13:56:44 +00:00

README.md

Datatracker Development in Docker

Getting started

  1. Set up Docker on your preferred platform.

  2. If you have a copy of the datatracker code checked out already, simply cd to the top-level directory.

    If not, check out a datatracker branch as usual. We'll check out trunk below, but you can use any branch:

    svn co https://svn.ietf.org/svn/tools/ietfdb/trunk
cd trunk

  3. TEMPORARY: Until a pre-built docker image is available for download, you will need to build it locally:

    docker/build

    This will take a while (15 to 30m), but only needs to be done once.

  4. Use the docker/run script to start the datatracker container. You will be dropped into a shell from which you can start the datatracker and execute related commands as usual, for example

    ietf/manage.py check; ietf/manage.py runserver 0.0.0.0:8000

    to start the datatracker.

    You can also pass additional arguments to docker/run, in which case they will be executed in the container (instead of a shell being started.)

    If you do not already have a copy of the IETF database available in the data directory, one will be downloaded and imported the first time you run docker/run. This will take some time.

    Once the datatracker has started, you should be able to open http://localhost:8000 in a browser and see the landing page.

Troubleshooting

  • If the database fails to start, the cause is usually an incompatibility between the database that last touched the files in data/mysql and the database running inside the docker container.

    The solution is to blow away your existing database (rm -rf data/mysql). A fresh copy will be retrieved and imported next time you do docker/run, which should resolve this issue.