ref: fd257d616e8ae37157a13d1f85408d4f91f46568 damn-deploy/README.md -rw-r--r-- 7.5 KiB
fd257d61Jiri Vlasak Remove contribution section, add mailing list 4 months ago

#Damn deploy

Divide and map. Now. -- the damn project -- helps mappers by dividing some big area into smaller squares that a human can map.

The damn-deploy repository contains the complete docker-compose-based deployment, including this deployment guide.


This project is published under MIT License.


Use the mailing list for the discussion.


#How to deploy

Prerequisities for deployment are git, docker and docker-compose. The guide is tested on Debian 10. You need some domain name directing to the server.

Then, you need to clone the damn deploy repository:

git clone https://git.sr.ht/~qeef/damn-deploy
cd damn-deploy

The most common usecase is autostart server and clients. The following sections consider server setup, setup for clients (client and manager), chat, autostart, and update. Also, see Damn upkeep section for periodic database upkeep scripts.

#Server setup

  1. Set environment variables in .env file. The following is the meaning:

    • POSTGRES_PASSWORD: Password to PostgreSQL database.

    • JWT_SECRET: Secret for generating, signing, and decrypting JSON Web Tokens.

    • SESSION_SECRET: Secret for cookies (I think).

    • OAUTH_CONSUMER_KEY: API key, get from osm.org.

    • OAUTH_CONSUMER_SECRET: API secret, get from osm.org.

    • DOMAIN_NAME: Use your domain.

    The following are optinal settings. You don't need to change them. The defaults work good.

    • SERVER_SUB: The subdomain for the server.
    • DAMN_SERVER_VERSION: Choose the version of the server.
    • DAMN_CLIENTS: Allow origins clients.
    • DB_HOST: Alias of db docker service, keep that value.
  2. Set proper email address in traefik.yml file.

  3. Create acme.json file and set 600 permissions:

    touch acme.json
    chmod 600 acme.json
  4. You may run the damn server now.

    docker-compose -f server.yml up

#Setup for clients

In addition to Server setup, you may want to run a client and a manager, too.

  1. Set environment variables in .env file. The following are optinal settings. You don't need to change them. The defaults work good. There is the meaning of the customization settings:

    • DEFAULT_LANG: The default language.
    • DEFAULT_AREAS_VIEW: Show areas on first page by default as grid or list?
    • DEFAULT_WEB_EDITOR: Set the default editor to id or rapid-esri.

    And the meaning of the optional settings for the clients:

    • CLIENT_SUB: The subdomain for the client.
    • DAMN_CLIENT_REPO: Link to client git repository.
    • DAMN_CLIENT_VERSION: Version of the client.
    • MANAGER_SUB: The subdomain for the manager.
    • DAMN_MANAGER_REPO: Link to the manager git repository.
    • DAMN_MANAGER_VERSION: Version of the manager.
  2. You may run the damn server with clients now.

    docker-compose -f server.yml -f clients.yml up

#Setup for chat

In addition to Server setup, you may want to run a chat server.

  1. Set environment variable in .env file.

    • CHAT_SUB: The subdomain for the chat.
  2. Run the chat server with the server:

    docker-compose -f server.yml -f chat.yml up

    or also with clients:

    docker-compose -f server.yml -f clients.yml -f chat.yml up

#Autostart with systemd

I assume that the damn deploy repository is cloned to /root/damn-deploy/.

  1. Create systemd unit for docker-compose:

    cat << EOF >> /etc/systemd/system/damn.service
    Description=Damn server app
    After=network.target docker.service
    ExecStart=/usr/bin/docker-compose -f /root/damn-deploy/server.yml -f /root/damn-deploy/clients.yml up
    ExecStop=/usr/bin/docker-compose -f /root/damn-deploy/server.yml -f /root/damn-deploy/clients.yml down

    Remove -f /root/damn-deploy/clients.yml when running server only.

  2. Enable and run damn service:

    systemctl start damn.service
    systemctl enable damn.service

#How to update

  1. If use systemd autostart, stop the damn service first:

    systemctl stop damn.service
  2. Stash the configuration:

    git stash
  3. Pull new version of the damn deploy repository:

    git pull
  4. Pop stashed changes (renew the configuration):

    git stash pop
  5. Maybe rebuild some docker images, but it depends on update changes:

    docker-compose -f server.yml build --no-cache api
    docker-compose -f server.yml build --no-cache upkeep
    docker-compose -f clients.yml build --no-cache client
    docker-compose -f clients.yml build --no-cache manager
    docker-compose -f chat.yml build --no-cache chat
  6. Start the damn service again:

    systemctl start damn.service

#Update database structure

The database structure is rarely to change but it may happen. For new deployments, there is nothing to do.

However, if you are upgrading from an existing database, you need to run the upgrade script manually.

All the scripts related to the database structure are stored in damndb directory, starting at 70_.... Which script should be run when updating the database structure is always noted in the [changelog][].

#Upgrade to v0.6.0

Stop the damn service and update the repository:

systemctl stop damn.service
git stash
git pull
git stash pop

Run the database:

docker-compose up -d db

Run the database upgrade script (you will be asked for the password stored in .env file):

export DB_HOST=$(docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' damndb)
psql -h $DB_HOST -d damndb -U damnuser < damndb/71_areas_squares_stats.sql

Stop the database container:

docker-compose down

Finally, there is no need to build the database container again. The database is created only once anyway, so run the damn service again:

systemctl start damn.service

#Upgrade to v0.7.0

When the upgrade is finished, update the current_commits in the database. Connect to the database (the password is in .env file):

export DB_HOST=$(docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' damndb)
psql -h $DB_HOST -d damndb -U damnuser

Run update query:

update current_commits set type='splitted' where message='The square was splitted';

#Damn upkeep

Damn upkeep docker image contains scripts that run periodically. Periodic run must be set with cron or systemd. The following example uses systemd.

An example of upkeep script is square unlock when there is no activity in two hours.

  1. Create systemd unit and timer for damn upkeep:

    cat << EOF >> /etc/systemd/system/damn_upkeep.service
    Description=Run damn upkeep
    ExecStart=/usr/bin/docker-compose -f /root/damn-deploy/server.yml run --rm upkeep
    cat << EOF >> /etc/systemd/system/damn_upkeep.timer
    Description=Run damn upkeep every 15 minutes
  2. Enable and run damn upkeep service and timer:

    systemctl enable damn_upkeep.timer
    systemctl enable damn_upkeep.service
    systemctl start damn_upkeep.timer