Feat: add a self hosted photon service for the dawarich instance

[33Fraise33]

Dawarich requires a reverse geocode service. I would prefer to self host this but as the database can be quite big I would prefer to host this on the media server where there are no backups of the disk.

• Add a role for photon service on BEOKPDCOVM02
• Make the role minimal and put it in the dawarich playbook.
• Write tests for the role
• allow to set the path of the photon database in a variable
• follow dawarich and photon advise: https://dawarich.app/docs/self-hosting/configuration/reverse-geocoding/

[33Fraise33]

/oc plan analyze this request and propose an implementation plan

[opencode-agent]

Repository analysis

• playbooks/dawarich.yml currently deploys Valkey and Dawarich only to BEOKPDCOVM01.
• Dawarich is containerized in roles/dawarich; its web and Sidekiq containers have duplicated environment configuration and currently rely on the public reverse-geocoding default.
• BEOKPDCOVM02 has an explicit-drop firewall policy, so publishing Photon’s port alone would not make it reachable from Dawarich.
• The repository has one Docker-driver Molecule scenario under molecule/dawarich, which provides the pattern for the new tests.
• Host addressing in group variables identifies BEOKPDCOVM01 as 10.10.48.34 (@VM01) and BEOKPDCOVM02 as 10.10.48.35 (@VM02).

Implementation plan

1. Create a minimal photon Galaxy-style role

   • Add:
     • roles/photon/defaults/main.yml
     • roles/photon/tasks/main.yml
     • roles/photon/handlers/main.yml
     • roles/photon/meta/main.yml
     • roles/photon/README.md
   • Define configurable variables for:
     • Photon database host path, such as photon_database_path
     • Image and tag
     • Published API port, defaulting to Photon’s 2322
     • Container state for Molecule/debugging
     • Recommended update interval and strategy
   • Create the database directory idempotently.
   • Deploy rtuszik/photon-docker with community.docker.docker_container.
   • Bind photon_database_path to /photon/photon_data.
   • Publish port 2322, set the recommended Photon update settings, use an explicit restart policy/state, pull the image, and disable Traefik exposure.
   • Document the large initial database download, parallel-update disk requirements, and the fact that this path should reside on non-backed-up media storage.

2. Configure the target media server

   • Update playbooks/host_vars/beokpdcovm02.yml to:
     • Set photon_database_path to the intended media-disk location, e.g. /media/photon.
     • Add an nftables input rule permitting TCP 2322 only from @VM01, where Dawarich runs.
   • Preserve the existing firewall variable composition and explicit-drop behavior.

3. Add Photon to the Dawarich playbook

   • Add a first play in playbooks/dawarich.yml targeting BEOKPDCOVM02.
   • Apply the photon role with a photon tag.
   • Keep the existing BEOKPDCOVM01 Valkey/Dawarich play afterward so Photon is declared before its consumer.

4. Point Dawarich at the self-hosted Photon instance

   • Add host-specific Dawarich Photon settings to playbooks/host_vars/beokpdcovm01.yml, using 10.10.48.35, port 2322, and HTTP.
   • Add the documented Photon variables to both dawarich_app and dawarich_sidekiq:
     • PHOTON_API_HOST
     • PHOTON_API_PORT
     • PHOTON_API_USE_HTTPS
   • Keep deployment-specific addressing out of the Dawarich role defaults.

5. Add Molecule coverage for Photon

   • Create molecule/photon/ with Docker-driver scaffolding:
     • molecule.yml
     • prepare.yml
     • converge.yml
     • verify.yml
     • cleanup.yml
   • Use a lightweight HTTP mock image during CI to avoid downloading Photon’s very large production database while still exercising the role’s container, bind mount, port, restart policy, and idempotency declarations.
   • Include the required post-convergence pause.
   • Verify:
     • The container is running.
     • The configured image, bind mount, environment, port mapping, and restart policy are correct.
     • An HTTP request to the published endpoint succeeds.
     • Container logs contain no runtime errors or warnings.
   • Clean up the test container and test database path.

6. Extend Dawarich integration tests

   • Supply Photon host/port/protocol values in molecule/dawarich/converge.yml.
   • Extend molecule/dawarich/verify.yml to assert that both the web and Sidekiq containers receive the expected self-hosted Photon environment variables.

7. Validation

   • Run secret-free local checks from the repository root:
     • pre-commit run --all-files
     • yamllint for changed YAML
     • ansible-lint for the new role, modified role, Molecule files, and playbook
     • Syntax-check playbooks/dawarich.yml with a non-production inventory
     • molecule test -s photon
     • molecule test -s dawarich

github run

[33Fraise33]

/oc build implement the required changes and make a merge request when done

[opencode-agent]

Created PR #11

github run