This diary is about how the Divide and map. Now. is deployed.

Divide and map. Now. consists of multiple parts like server, JavaScript clients, JOSM plugin or web page. Each part is clearly separated and has its own repository. All are integrated within the damn-deploy, which has its own repository, too.

The dataflow of HTTP services

I am not a sysadmin. When I worked on the refactor deploy, I kept Docker and Systemd and Debian. I simplified dockerfiles, removed unnecessary ones, removed unused SQL code, added systemd units and rewrote the “How to deploy” and “How to upgrade” in the README.

I added damn-www-template with the hugo static site generator, simple blogging theme and an example content. If you care to run your own instance, you may get inspired. But don’t get limited – only a dockerfile serving your web page is expected.

I upgraded the Python from 3.7 to 3.11 by changing the version in the dockerfile. I upgraded the PostGIS from 11 to 15 also by changing the version in the dockerfile. I upgraded from Debian 10 to Debian 12 by backing up the database and copying it to a new droplet (VPS with the same parameters as the original one, 1 GB / 1 CPU and 25 GB SSD) where Divide and map. Now. was freshly deployed. It took longer to propagate DNS change than to deploy the Divide and map. Now.

Yeah. That was not a fair upgrade. However, I am not a sysadmin. The content of the database is the important thing and it’s good that backing-up and restoring works.

Divide and map. Now. – the damn project – helps mappers by dividing a big area into smaller squares that people can map together.

Login to leave a comment