Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| services:damselfly [2024/04/02 14:16] – willy | services:damselfly [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Damselfly ====== | ||
| - | |||
| - | **Note:** since i don't use this service anymore, this page might be not updated. | ||
| - | |||
| - | [[https:// | ||
| - | |||
| - | |||
| - | ===== Installation ===== | ||
| - | |||
| - | Installing Damselfly can be done on bare-metal, but the dev does not support it, so i will show you both ways. | ||
| - | |||
| - | In general you can find more installation information [[https:// | ||
| - | |||
| - | ==== Common installation steps ==== | ||
| - | |||
| - | Create a damselfly user and make it member of the //photos// group: | ||
| - | <code bash> | ||
| - | groupadd photos | ||
| - | useradd -d / | ||
| - | </ | ||
| - | |||
| - | Since Damselfly uses INotify triggers, you need to increase defaults or it will be unable to monitor large collections of photos (see [[https:// | ||
| - | |||
| - | Create the file **/ | ||
| - | <file damselfy.conf> | ||
| - | fs.inotify.max_user_instances=524288 | ||
| - | </ | ||
| - | |||
| - | And for it to be applied without a reboot: | ||
| - | <code bash> | ||
| - | | ||
| - | </ | ||
| - | |||
| - | |||
| - | ==== Bare Metal Installation (not recomended) ==== | ||
| - | |||
| - | Non-containerized install instructions [[https:// | ||
| - | |||
| - | Download and decompress the release: | ||
| - | <code bash> | ||
| - | su - damselfly | ||
| - | wget https:// | ||
| - | mkdir damselfly | ||
| - | cd damselfly | ||
| - | unzip damselfly-server-linux-4.1.0.zip | ||
| - | </ | ||
| - | (the release zip file requires a sub-folder to store neatly all files) | ||
| - | |||
| - | In order for Damselfly to work you need to install some dependencies, | ||
| - | |||
| - | There you go: | ||
| - | <code bash> | ||
| - | emerge -s media-fonts/ | ||
| - | </ | ||
| - | |||
| - | The supposed //libgmp1// dependency is satisfied by adding **openmp** useflag to GCC (see [[https:// | ||
| - | |||
| - | |||
| - | ==== Podman installation ==== | ||
| - | |||
| - | Create the following // | ||
| - | <file - docker-compose.yml> | ||
| - | version: " | ||
| - | |||
| - | name: damselfly | ||
| - | | ||
| - | services: | ||
| - | damselfly: | ||
| - | container_name: | ||
| - | image: webreaper/ | ||
| - | ports: | ||
| - | - 6363: | ||
| - | volumes: | ||
| - | - / | ||
| - | - / | ||
| - | - / | ||
| - | restart: unless-stopped | ||
| - | |||
| - | networks: | ||
| - | damselfly-net: | ||
| - | </ | ||
| - | |||
| - | And install it: | ||
| - | <code bash> | ||
| - | su - damselfly | ||
| - | podman compose pull | ||
| - | </ | ||
| - | |||
| - | |||
| - | ===== Reverse Proxy ===== | ||
| - | |||
| - | Damselfly do not support sub-paths, so you __must__ spin your own subdomain for it to work. Here is the relevant NGINX configuration file: | ||
| - | <file - damselfly.conf> | ||
| - | TBD | ||
| - | </ | ||
| - | |||
| - | |||
| - | ===== Startup ===== | ||
| - | |||
| - | |||
| - | ==== Bare Metal running | ||
| - | |||
| - | Start: | ||
| - | <code bash> | ||
| - | ./ | ||
| - | </ | ||
| - | |||
| - | You will need the usual script & / | ||
| - | |||
| - | ==== Podman running | ||
| - | |||
| - | Running is, as usual: | ||
| - | <code bash> | ||
| - | su - damselfly | ||
| - | podman compose up | ||
| - | </ | ||
| - | |||
| - | To run at boot, add the following lines to your **/ | ||
| - | < | ||
| - | podman network create damselfly-net | ||
| - | su - damselfly -c " | ||
| - | </ | ||
| - | |||
| - | and the following lines to **/ | ||
| - | < | ||
| - | su - damselfly -c " | ||
| - | </ | ||