OpenAtlas

• Windows 10
• WSL 2 activated
• Docker Desktop (from Microsoft) installed
• PyCharm for get some debug

• cd to repository of openatlas
• docker compose up -d

With some trouble, but not not attributable to developers. Caused by git, that convert LF to CRLF, and that is cause that scripts like SQLs and entrypoint.sh are not well interpreted inside linux docker.

• repeat all proces and trust
• try export and import process
• try upgrade process

I would like decide directory or place of installation. In my context (git in Windows) has intalled postgres database in 'data' directory inside repo of git

Take in acoount that I'm not an expert in dockers, and I understand the concept, but I'm not a master of dockers

Agghh !!

I wanted to be sure that I could reproduce setup.

I have stopped services, deleted db created before. But no success.
When I try to repeat:

C:\Users\rodellas\GITHUBenricapbes\OpenAtlas> docker compose up -d

I got:

/var/www/openatlas /

2023-02-12T20:11:33.637401000Z psql: error: could not connect to server: Connection refused
2023-02-12T20:11:33.637430600Z     Is the server running on host "postgres" (172.19.0.2) and accepting
2023-02-12T20:11:33.637436900Z     TCP/IP connections on port 5432?

If after previous execution of 'docker compose' I add

        - OVERWRITE_DATABASE=TRUE

in docker-compose.yaml in environment of services of openatlas and rexecute service openatlas.

After this web and db runs perfectly

Enric Rodellas wrote:

I would like decide directory or place of installation. In my context (git in Windows) has intalled postgres database in 'data' directory inside repo of git

I found no way to do this via variables, but you can play around with the postgis volumes in docer-compose.yml:

volumes:
   - ./data/db:/var/lib/postgresql/data

This ./data/db part is the path where the database is stored, just add an absolute path, where you want it to install.

Andi and I rewrote the script. Please pull the newest develop version and run

docker compose up --detach --build

Bernard,

I don't get recovered my last dump following instructions uncommenting

      # Uncomment to import SQL dump
      - ./files/export/dump.sql:/docker-entrypoint-initdb.d/dump.sql

and assuring (berfore executing) that ./files/export/dump.sql is last dump

I think would be very useful to add some external port to acces to database. Specially for adminsitrative tasks.

I test:

    ports:
      - "25432:5432" 

inside postgres section

Enric Rodellas wrote:

I don't get recovered my last dump following instructions uncommenting

With the last commit, I forgot to write a comment, that the installation scripts above has to be commented out. And you have to delete the /data/db folder or change the path of the variable:

./data/db:/var/lib/postgresql/data

Because, the scripts won't run if a database exists.

So to import a dump you have to do following steps:

1. Delete or rename database path (e.g. ./data/db_dump:/var/lib/postgresql/data)
2. Comment out installation scripts
   

   #      - ./install/extensions.sql:/docker-entrypoint-initdb.d/dump.sql
   #      - ./install/1_structure.sql:/docker-entrypoint-initdb.d/1_structure.sql
   #      - ./install/2_data_model.sql:/docker-entrypoint-initdb.d/2_data_model.sql
   #      - ./install/3_data_web.sql:/docker-entrypoint-initdb.d/3_data_web.sql
   #      - ./install/4_data_type.sql:/docker-entrypoint-initdb.d/4_data_type.sql
   

3. Uncomment path to dump script
   

   ./files/export/dump.sql:/docker-entrypoint-initdb.d/dump.sql
   

4. run docker compose up --detach --build

If the dump is quite large, it will take some time, and it may be, that you have to restart the postgis container.

Enric Rodellas wrote:

I think would be very useful to add some external port to acces to database. Specially for adminsitrative tasks.

I test:
[...]

inside postgres section

Yes and no. For debugging reason, yes. But I don't know you this will interfere with other installation processes (e.g. kubernetes). I wrote it in the composer file and commented it.

In my point of view, the composer file is the file, where the user can and should add personal installation options. This is the place to customize your installation and therefore, I don't want to fill it up with things, that are not necessarily needed. It will soon get bloated.

Bernhard,
Thank you very much for your notes.
I have carefully followed your instructions, ( but I can't initialize the database with the Dump file. In the process a Postgres BD is initialized, but does not create any of the openatlas tables and finally launch an error.

I comment and uncomment:

    volumes:
      - ./data/db:/var/lib/postgresql/data
#     Installation of an empty database
      #- ./install/extensions.sql:/docker-entrypoint-initdb.d/dump.sql
      #- ./install/1_structure.sql:/docker-entrypoint-initdb.d/1_structure.sql
      #- ./install/2_data_model.sql:/docker-entrypoint-initdb.d/2_data_model.sql
      #- ./install/3_data_web.sql:/docker-entrypoint-initdb.d/3_data_web.sql
      #- ./install/4_data_type.sql:/docker-entrypoint-initdb.d/4_data_type.sql
#      Import dump (comment install section above out)
      - ./files/export/dump.sql:/docker-entrypoint-initdb.d/dump.sql

And this is the log in openatlas docker:

2023-02-22 18:56:04 Traceback (most recent call last):
2023-02-22 18:56:04   File "/var/www/openatlas/install/upgrade/database_upgrade.py", line 50, in <module>
2023-02-22 18:56:04     settings = Settings.get_settings(cursor)
2023-02-22 18:56:04   File "/var/www/openatlas/openatlas/database/settings.py", line 14, in get_settings
2023-02-22 18:56:04     cursor.execute("SELECT name, value FROM web.settings;")
2023-02-22 18:56:04   File "/usr/lib/python3/dist-packages/psycopg2/extras.py", line 146, in execute
2023-02-22 18:56:04     return super(DictCursor, self).execute(query, vars)
2023-02-22 18:56:04 psycopg2.errors.UndefinedTable: relation "web.settings" does not exist
2023-02-22 18:56:04 LINE 1: SELECT name, value FROM web.settings;
2023-02-22 18:56:04                                 ^

Your dump file is named dump.sql and is in the folder ./files/export/ (this is in the OpenAtlas directory)?
The only way I get this error message is, that my dump.sql file doesn't exist.

So to import an SQL dump, please do the following things:

1. docker compose down

2. Delete or rename (if you want to keep it) the database folder. In your case ./data/db/
3. Move the dumped SQL file to ./files/export/.
4. Either rename the .sql file to dump.sql or change this path to your filename - ./files/export/ dump.sql :/docker-entrypoint-initdb.d/dump.sql

5. docker compose up -d

If everything went well, the services should start automatically. We implemented a health check (in the develop branch, not main), so the openatlas-openatlas-1 container will not start, if the openatlas-postgres-1 container is unhealthy (not ready)

If the error still occurs, I can only ask for you dump file, so I can check if everything is ok with it.