Skip to content

Add Genealogy LXC - #2515

Closed
vlevshits wants to merge 3 commits into
community-scripts:mainfrom
vlevshits:feat/genealogy
Closed

vlevshits wants to merge 3 commits into
community-scripts:mainfrom
vlevshits:feat/genealogy

Conversation

@vlevshits

Copy link
Copy Markdown

✍️ Description

Genealogy is a modern, private, self-hosted family tree web application with living-person privacy protection, Slavic patronymic support, and zero-proxy native port 80 web serving. The installation provisions PostgreSQL 16, configures dedicated systemd permissions (CAP_NET_BIND_SERVICE) to bind directly to port 80 without root, marks packages to prevent clean-lxcs autoremoval, and registers the in-container update command. Tested on a Proxmox VE 8.x host in an unprivileged Debian 12 LXC container using both Default and Advanced installation modes.

🔗 Related PR / Issue

Link: #

✅ Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No breaking changes – Existing functionality remains intact.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🏗️ arm64 Support (X in brackets)

  • arm64 supported - Tested and supported on arm64.
  • arm64 not tested - Assumed to work on arm64, but testing has not been done.
  • arm64 not supported - Confirmed upstream dependencies or binaries do not support arm64.

🖥️ Tested on (X in brackets)

  • Proxmox VE – Created on a Proxmox VE host and the app works.
  • Incus – Created on an Incus host and the app works.

Application containers run on both; tick what you actually tested. VMs and host tools are Proxmox only.


🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • ✨ New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

🔍 Code & Security Review (X in brackets)

  • Follows CODE-AUDIT.md & CONTRIBUTING.md guidelines
  • Uses correct script structure (AppName.sh, AppName-install.sh, AppName.json)
  • No hardcoded credentials
  • No Docker / Docker Compose – The application is installed bare-metal; Docker is not used.
  • No git pull – Updates use fetch_and_deploy_gh_release, fetch_and_deploy_codeberg_release, fetch_and_deploy_gl_release, or fetch_and_deploy_from_url instead of git pull.

📋 Additional Information (optional)

Web interface listens directly on port 80 (HTTP). On first launch, navigating to http://<CT_IP>:80 opens the First-Run Setup Wizard to create the admin account, set credentials (passkey/password), and name the family archive. Tested in-container update command and verified resilience against clean-lxcs sweeps.


📦 Application Requirements (for new scripts)

⚠️ Do not remove this section.
It is used by automated PR validation checks.
If this PR is not a new script submission, leave the checkboxes unchecked.

Required for 🆕 New script submissions.
Pull requests that do not meet these requirements may be closed without review.

  • The application is at least 6 months old
  • The application is actively maintained
  • The application has 1,000+ GitHub stars
  • Official release tarballs are published
  • I understand that not all scripts will be accepted due to various reasons and criteria by the community-scripts ORG

🌐 Source

https://github.com/vlevshits/genealogy


🤖 AI Assistance (X in brackets)

If you used an AI tool (GitHub Copilot, Claude, ChatGPT, etc.) to write or generate any scripts in this PR, you must confirm compliance below.
Select exactly one option.

  • No AI used – Scripts were written without AI assistance.
  • AI was used – I confirm the scripts were built using AGENTS.md and .github/agents/pve-script-creator.agent.md as guidance, and the output has been reviewed and corrected to match those guidelines.

Please describe to which degree, if any, an LLM was used in creating this pull request. Name the model(s) used and, if applicable, the reasoning/thinking effort level (e.g. "Claude Sonnet 4.5, high reasoning, used to draft the install script, then manually reviewed and tested" or "No LLM used"). This is informational, not a penalty — but scripts that are clearly AI-generated and not further revised by the author to match CODE-AUDIT.md / CONTRIBUTING.md may be closed without review.

Antigravity (Gemini 3.8 Flash, medium reasoning) was used to adapt the application installer into DevScripts modular format (ct/genealogy.sh, install/genealogy-install.sh, json/genealogy.json) following AGENTS.md and CODE-AUDIT.md rules (Line 2 _CS_DEFAULT_URL pinning, var_arm64, $STD apt install, cleanup_lxc), followed by manual review, linting, and testing on a Proxmox VE 8.x host.

@vlevshits
vlevshits requested a review from a team as a code owner November 9, 2026 12:15
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Try this script

ct/genealogy.sh, run in the Proxmox VE shell or on an Incus host:

COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/vlevshits/genealogy-scripts/feat/genealogy \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/vlevshits/genealogy-scripts/feat/genealogy/ct/genealogy.sh)"

COMMUNITY_SCRIPTS_URL is not optional for ct/. Fetching the ct/ script from a
branch does not tell the engine where that branch is — with bash -c "$(curl …)"
there is no file on disk for the scripts root to be derived from, so it would fall
back to upstream main and look for the install script there.

Against a core branch as well

Add COMMUNITY_SCRIPTS_CORE_URL=https://raw.githubusercontent.com/OWNER/core/BRANCH
to test an engine change at the same time. The two resolve independently.

Useful flags while testing

dev_mode=net logs every fetch with status and duration, so you can confirm the
branch is really being used. dev_mode=keep stops a failed build from deleting
the container along with the evidence.

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

⚠️ Not ready for review yet

@vlevshits, this pull request is missing the following:

  • The application has 1,000+ GitHub stars

Edit the PR description to fix it — no new PR needed. This check runs again on every edit and clears itself once everything is in place.

Until then the PR is marked stale and will be closed in 7 days.


@community-scripts/contributor please take a look: close it, comment, or set keep-open to keep it.

@github-actions github-actions Bot added requirements missing PR description misses template items; closes after 7 days unless fixed or keep-open stale new script labels Nov 9, 2026
@vlevshits
vlevshits marked this pull request as draft November 9, 2026 12:17
@michelroegl-brunner

Copy link
Copy Markdown
Member

0 Stars, First release yesterday. Just a call to your own install.sh. Are you kidding right now? Why are you wasting peoples time when the requeremts are clearly written here?

@vlevshits
vlevshits deleted the feat/genealogy branch November 9, 2026 19:39
@vlevshits

Copy link
Copy Markdown
Author

0 Stars, First release yesterday. Just a call to your own install.sh. Are you kidding right now? Why are you wasting peoples time when the requeremts are clearly written here?

It was marked as draft for that exact reason. Take a breath and find somewhere else to project your issues.

@vlevshits
vlevshits restored the feat/genealogy branch November 9, 2026 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new script requirements missing PR description misses template items; closes after 7 days unless fixed or keep-open stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants