daniel/furtka
1
1
Fork 0
Code Issues 1 Pull requests Projects 1 Releases 13 Packages Wiki Activity Actions

feat(website): legal pages (Impressum/Datenschutz) + auto-deploy on push-to-main #1

Merged
daniel merged 1 commit from website-legal into main 2026-04-18 12:32:19 +02:00
Conversation 0 Commits 1 Files changed 9 +301 -1
daniel commented 2026-04-18 12:17:58 +02:00
Owner
Copy link

Two coupled changes that make sense to land together:

  1. Legal pages required under German law

    • /imprint/ + /de/impressum/ — §5 DDG disclosure (contact is email
      plus Forgejo-Issues as the second quick-contact channel, per ECJ
      C-298/07 no phone number required)
    • /privacy/ + /de/datenschutz/ — Art. 13 GDPR minimum: server-log
      processing (IP, UA, URL, retention ≤30 days), no cookies, no
      tracking, no third-party embeds. RLP Landesbeauftragter as the
      competent supervisory authority.
    • Footer partial linked from every page, localized per language.
    • DE versions are legally binding; EN versions are courtesy
      translations noting that.

  2. Auto-deploy wired up

    • New workflow .forgejo/workflows/deploy-site.yml fires on
      push-to-main with paths under website/**. Runs on the self-hosted
      runner, which is forge-runner-01 — so "deploy" is just a local
      rsync into /srv/furtka-site and a hugo build into
      /var/www/furtka.org. No SSH, no secrets.
    • website/deploy-ci.sh is the SSH-free counterpart of deploy.sh,
      invoked by the workflow.
    • compose.yml bind-mounts /srv/furtka-site and /var/www/furtka.org
      into the runner container at matching paths so the workflow can
      reach them. Requires a one-time docker compose up -d on the
      runner host to pick the mounts up.
    • deploy.sh is kept for out-of-band manual deploys (testing from a
      local branch, CI outage) but gets a header comment pointing at
      the CI path as the normal flow.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

Two coupled changes that make sense to land together: 1. Legal pages required under German law - /imprint/ + /de/impressum/ — §5 DDG disclosure (contact is email plus Forgejo-Issues as the second quick-contact channel, per ECJ C-298/07 no phone number required) - /privacy/ + /de/datenschutz/ — Art. 13 GDPR minimum: server-log processing (IP, UA, URL, retention ≤30 days), no cookies, no tracking, no third-party embeds. RLP Landesbeauftragter as the competent supervisory authority. - Footer partial linked from every page, localized per language. - DE versions are legally binding; EN versions are courtesy translations noting that. 2. Auto-deploy wired up - New workflow .forgejo/workflows/deploy-site.yml fires on push-to-main with paths under website/**. Runs on the self-hosted runner, which *is* forge-runner-01 — so "deploy" is just a local rsync into /srv/furtka-site and a hugo build into /var/www/furtka.org. No SSH, no secrets. - website/deploy-ci.sh is the SSH-free counterpart of deploy.sh, invoked by the workflow. - compose.yml bind-mounts /srv/furtka-site and /var/www/furtka.org into the runner container at matching paths so the workflow can reach them. Requires a one-time `docker compose up -d` on the runner host to pick the mounts up. - deploy.sh is kept for out-of-band manual deploys (testing from a local branch, CI outage) but gets a header comment pointing at the CI path as the normal flow. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
daniel added 1 commit 2026-04-18 12:17:59 +02:00
feat(website): legal pages (Impressum/Datenschutz) + auto-deploy on push-to-main
All checks were successful
CI / lint (pull_request) Successful in 1m2s
Details
CI / test (pull_request) Successful in 1m19s
Details
CI / validate-json (pull_request) Successful in 55s
Details
CI / markdown-links (pull_request) Successful in 27s
Details
b77ef80b56 
Two coupled changes that make sense to land together:

1. Legal pages required under German law
   - /imprint/ + /de/impressum/ — §5 DDG disclosure (contact is email
     plus Forgejo-Issues as the second quick-contact channel, per ECJ
     C-298/07 no phone number required)
   - /privacy/ + /de/datenschutz/ — Art. 13 GDPR minimum: server-log
     processing (IP, UA, URL, retention ≤30 days), no cookies, no
     tracking, no third-party embeds. RLP Landesbeauftragter as the
     competent supervisory authority.
   - Footer partial linked from every page, localized per language.
   - DE versions are legally binding; EN versions are courtesy
     translations noting that.

2. Auto-deploy wired up
   - New workflow .forgejo/workflows/deploy-site.yml fires on
     push-to-main with paths under website/**. Runs on the self-hosted
     runner, which *is* forge-runner-01 — so "deploy" is just a local
     rsync into /srv/furtka-site and a hugo build into
     /var/www/furtka.org. No SSH, no secrets.
   - website/deploy-ci.sh is the SSH-free counterpart of deploy.sh,
     invoked by the workflow.
   - compose.yml bind-mounts /srv/furtka-site and /var/www/furtka.org
     into the runner container at matching paths so the workflow can
     reach them. Requires a one-time `docker compose up -d` on the
     runner host to pick the mounts up.
   - deploy.sh is kept for out-of-band manual deploys (testing from a
     local branch, CI outage) but gets a header comment pointing at
     the CI path as the normal flow.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
daniel merged commit a511f5418d into main 2026-04-18 12:32:19 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: daniel/furtka#1
No description provided.
Delete branch "website-legal"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?