Skip to content
Snippets Groups Projects
Commit e57c1e83 authored by Nico Vermaas's avatar Nico Vermaas
Browse files

add documentation

parent 6cb51d41
No related branches found
No related tags found
No related merge requests found
......@@ -2,11 +2,21 @@
### Apertif Task Database for LOFAR Data Valorization
Test Environment:
* https://sdc.astron.nl:5554/atdb/
* https://sdc.astron.nl:5554/atdb/admin/
### Confluence
Confluence Page:
* https://support.astron.nl/confluence/display/LDV/LOFAR+Data+Valorization+Home
#### Diagrams (under construction)
These are still mostly the original ATDB diagrams. They will be adapted and kept in sync once the ATDB-LDV structure solifies a bit more.
Workflow:
This diagram roughly serves as the specs for adapting ATDB for LDV.
* https://support.astron.nl/confluence/display/LDV/WORKFLOW
#### Overview Diagrams (under construction)
These diagrams are the core of the ATDB documentation.
Currently they are still mostly the original ATDB diagrams. They will be adapted and kept in sync once the ATDB-LDV structure solifies a bit more.
Context Diagram:
* https://drive.google.com/file/d/1ltmzFMgOI24kIgPtaKrYl-j__ATOI3m6/view?usp=sharing
......@@ -21,12 +31,23 @@ Deployment Diagram:
* https://drive.google.com/file/d/1_j9Fp505pZTxcmzAEdgftdPkoIFrKfAX/view?usp=sharing
### Manual deploy in Docker
#### initial
> cd ~/my_docker
> cd atdb-ldv
> git clone https://git.astron.nl/astron-sdc/atdb-ldv.git
#### update:
> export DOCKER_BUILD_DIR=$HOME/my_docker/atdb-ldv/atdb-ldv/atdb
> export DOCKER_COMPOSE_DIR=$DOCKER_BUILD_DIR/docker
> cd $DOCKER_COMPOSE_DIR
> docker-compose -p atdb up -d
### Database migrations
When the `models.py` is changed, then the database must be migrated.
This is how to do that manually for a persistent database in a Docker container.
> docker exec -it atdb-ldv python manage.py makemigrations --settings atdb.settings.docker_sdc
> docker exec -it atdb-ldv python manage.py migrate --settings atdb.settings.docker_sdc
......
......@@ -39,7 +39,8 @@ DATABASES = {
# database runs locally in postgres
# 'NAME': 'atdb_trunk',
'NAME': 'atdb_04oct2019',
#'NAME': 'atdb_04oct2019',
'NAME': 'atdb_ldv',
'HOST': 'localhost',
'PORT': '',
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment