Repository navigation
feat(install): one-command install with Docker Swarm and Traefik (IP by default, HTTPS with a domain), and Docker-first docs (#226) - #241
Merged
alexevladgabriel merged 5 commits intoNov 15, 2026
Conversation
… Traefik and automatic HTTPS One command on a fresh server, in the spirit of Coolify and Dokploy: curl -fsSL https://pelican.dev/install.sh | sudo bash It checks the server (Linux, x86_64/arm64, virtualization, ports 80/443, DNS), installs Docker if missing, starts a one-node Swarm and deploys the "pelican" stack from /opt/pelican: Traefik on 80/443 (HTTP to HTTPS, Let's Encrypt on the first request, renewals on its own) and the Panel behind it (BEHIND_PROXY, TRUSTED_PROXIES set to the network it shares with Traefik). Profiles: quick (SQLite) or production (MariaDB 11.4 and Redis 7, passwords generated). With --wings it installs Wings as the docs do and routes its domain through Traefik. - Guided: asks for what's missing; with --yes every answer is an option, so automation and AI assistants can drive it. --dry-run shows the plan and writes the files without root and without touching the server. - Configurable afterwards: settings in pelican.env (0600), stack.yml reads them, deploy.sh applies them (and updates the Panel). A second run keeps APP_KEY and passwords and refuses to switch profiles over existing data. - Networks clear of Wings: docker_gwbridge is created on 10.204.0.0/24 before "swarm init" (it would take Wings' 172.18.0.0/16), and Swarm uses 10.203.0.0/16 rather than 10.0.0.0/x, which cloud private networks use. - Traefik in host-mode ports (real client IPs), readTimeout 600s for uploads, every service pinned to this node (local volumes). - Safe output: the swarm join token is never printed; the log is root-only; Let's Encrypt's forbidden example.com contacts are refused up front. Served as a root file (router/paths.mjs ROOT_FILES; the Hub's DocsBuildService::ROOT_FILES needs it too). Tested in scripts/install-sh.test.mjs (dry runs, generated stack parsed as YAML, deploy.sh with a stub docker, shellcheck) and end to end in an Ubuntu 24.04 VM.
Ports #226 (Lance) to the Fumadocs site: - guides/docker becomes the top-level Getting Started (requirements, the virtualization check, Docker, swap), now opening with the one-command install. - panel/advanced/docker becomes panel/install, the recommended install: the install script (profiles, options, files, changing settings, updating, Wings on the same server, troubleshooting, backups) and then Docker Compose by hand, with #226's plugins volume and the note on the old ghcr.io/pelican-dev path. - The install without Docker moves to panel/standalone/*. - Redirects for the six old paths (netlify.toml, which the Hub's redirects.json is built from), inbound links, the sidebar, the OG motifs, ui/nav.json. - The AI guide's recommended prompt now drives the install script (asks the questions, writes the command, dry run first); the old prompt becomes the "Standalone install" tab.
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
…, no domain needed Without --domain (or an empty answer), the Panel is served on http://<external IPv4> (found automatically, or --ip), with the quick profile and no other questions under --yes. A domain is still the way to HTTPS: give it at install, or later by running the script again with --domain/--email (keys, passwords and data kept) or setting PANEL_DOMAIN and LE_EMAIL and running deploy.sh. After the switch, plain HTTP to the old IP lands on the domain. - Traefik's routes now live in traefik/pelican.yml, written by deploy.sh from pelican.env (IP: the Panel on port 80 at any address; domain: HTTPS with Let's Encrypt, HTTP to HTTPS, Wings' domain). The Panel's APP_URL follows (PANEL_URL). Traefik no longer needs the Docker socket. - Wings without a domain is reached on http://<IP>:8080 (ufw opens it); with a panel domain it needs its own, as before. - The install waits for Swarm to finish rolling the services out before checking the Panel: a changed setting replaces the Panel, and the check used to reach the old one. - Traefik's healthcheck runs every 10s, so it counts as 1/1 sooner. Verified in the Ubuntu 24.04 VM: a fresh install with no domain, then adding a domain (and Wings on one), then back, checking the new Panel right after each.
…Traefik The model Coolify and Dokploy use: the installer runs straight through and anything not given takes its default. - No questions unless --interactive (or PELICAN_INTERACTIVE=1), which asks for each choice with explanations and needs a terminal. With no options it installs the Panel on the server's IP, quick profile, no Wings. A domain without an email, or Wings without its domain next to a Panel domain, stops with the option and the variable to set. --yes is still accepted, unused. - Every option can be an environment variable (PELICAN_DOMAIN, PELICAN_EMAIL, PELICAN_PROFILE, PELICAN_WINGS, PELICAN_WINGS_DOMAIN, PELICAN_IP, PELICAN_DIR, PELICAN_IMAGE, PELICAN_STAGING, PELICAN_SKIP_DNS_CHECK, PELICAN_DRY_RUN, PELICAN_INTERACTIVE); the option wins. With sudo they go after it: curl ... | sudo PELICAN_DOMAIN=panel.example.com PELICAN_EMAIL=... bash - Traefik pinned to v3.7.19 (was the moving v3 tag). Running the script again moves an install to the version it pins; PELICAN_TRAEFIK_IMAGE for another. Docs and the AI prompt drop --yes and list the variables. Verified in the VM: the script piped into sudo with variables re-ran an install with no questions and moved Traefik to 3.7.19; --interactive answered through a pseudo-terminal.
…et, dry runs, share image - Running again without --staging now moves a staging install to Let's Encrypt production (it kept the saved staging server). A CA set by hand is kept. Each CA gets its own certificate store (deploy.sh names it from LE_CA_SERVER), so staging certificates and the staging account don't carry over. - Re-running with Wings running no longer fails: the binary is downloaded to wings.new and renamed over the running one (writing to it gave "text file busy", curl exit 23, before the stack was deployed). - A second run keeps the PUBLIC_SUBNET saved in pelican.env (it reset it to 10.203.250.0/24, moving TRUSTED_PROXIES and the network) unless PELICAN_PUBLIC_SUBNET asks for another. - A dry run warns about example.com emails instead of stopping, so the docs' dry-run example works; a real run still refuses them. - The panel/install share image quotes lines that are on the page (it was dropped). New lib/og-motifs.test.mjs checks every motif against its page. Verified in the VM: a running /usr/local/bin/wings blocks the old download (curl exit 23) and not the new one; staging, then a run without --staging, switches caServer and the store to production.
alexevladgabriel
marked this pull request as ready for review
November 15, 2026 19:40
alexevladgabriel
added a commit
that referenced
this pull request
Nov 15, 2026
…th an AI assistant (#240) * feat(docs): style the docs like the Hub's redesigned pages The docs shared the header idea and tokens with the Hub's pages but still drew hard offset shadows, rounded Fumadocs chrome and white code, so they read as another site. They now use the Hub's pieces: square corners, 3px edges on cards and controls, 2px rules, no offset shadows, navy code in both themes, sky only as an accent. - Top bar: the Hub nav's buttons, theme switch and search input; navy ground and a slate line in the dark theme. - Sidebar and TOC: the Hub's app sidebar (light sky current item, sky edge) and the plugin page's section links. - Page: the plugin page's kicker and title; the Hub's prose links, inline code chips, square lists, Markdown tables (3px edge, sky head). - Code blocks: the egg page's navy install script, with Shiki's dark colours. - Callouts: the Hub's alerts (3px edge, 8px tone edge). Tabs: the plugin page's tabs. "Your setup": a Hub card with its form fields. - Page footer, search dialog: square, edged, no shadows. Mermaid: classic look in the site's colours. - ui/tokens.css: the Hub's page roles as --pl-* tokens (additive). Everything is scoped to .dt-root (or :root:has(.dt-root) for the search dialog), so the interim landing pages are pixel-identical. * feat(docs): copy pages for AI assistants, and a guide to installing with one Every docs page gets three actions under its title: - Copy page: the page as Markdown (/docs/md/<page>.md). When the reader has filled in "Your setup", a "My setup: ..." line goes on top, so an assistant answers for their install; the page text itself is not changed. - Copy all docs: /llms-full.txt, every page in one file (~60k tokens). - Open: Fumadocs' menu (GitHub, Markdown, ChatGPT, Claude, Cursor, Scira). New page guides/ai-assistant ("Installing with an AI Assistant"): how to give an assistant the docs (the buttons, llms.txt, llms-full.txt, <page>.md), a prompt for a production Panel install (asks for OS, domain, web server, database and Wings first, one step at a time, no secrets in chat, and ends on a checklist: HTTPS with renewal, firewall ports, queue worker and cron, permissions, APP_KEY kept off the server, backups and updates), prompts for Wings, troubleshooting and updating, and rules for agents with shell access. Linked from Getting Started. Code blocks: a `wrap` flag (lib/shiki-setup.ts) wraps long lines, used by the prompts; empty lines in plain-text blocks keep their height (they collapsed). * fix(docs): show wrapped prompts in full, without the code block's 600px cap * feat(install): one-command install with Docker Swarm and Traefik (IP by default, HTTPS with a domain), and Docker-first docs (#226) (#241) * feat(install): pelican.dev/install.sh, the Panel on Docker Swarm with Traefik and automatic HTTPS One command on a fresh server, in the spirit of Coolify and Dokploy: curl -fsSL https://pelican.dev/install.sh | sudo bash It checks the server (Linux, x86_64/arm64, virtualization, ports 80/443, DNS), installs Docker if missing, starts a one-node Swarm and deploys the "pelican" stack from /opt/pelican: Traefik on 80/443 (HTTP to HTTPS, Let's Encrypt on the first request, renewals on its own) and the Panel behind it (BEHIND_PROXY, TRUSTED_PROXIES set to the network it shares with Traefik). Profiles: quick (SQLite) or production (MariaDB 11.4 and Redis 7, passwords generated). With --wings it installs Wings as the docs do and routes its domain through Traefik. - Guided: asks for what's missing; with --yes every answer is an option, so automation and AI assistants can drive it. --dry-run shows the plan and writes the files without root and without touching the server. - Configurable afterwards: settings in pelican.env (0600), stack.yml reads them, deploy.sh applies them (and updates the Panel). A second run keeps APP_KEY and passwords and refuses to switch profiles over existing data. - Networks clear of Wings: docker_gwbridge is created on 10.204.0.0/24 before "swarm init" (it would take Wings' 172.18.0.0/16), and Swarm uses 10.203.0.0/16 rather than 10.0.0.0/x, which cloud private networks use. - Traefik in host-mode ports (real client IPs), readTimeout 600s for uploads, every service pinned to this node (local volumes). - Safe output: the swarm join token is never printed; the log is root-only; Let's Encrypt's forbidden example.com contacts are refused up front. Served as a root file (router/paths.mjs ROOT_FILES; the Hub's DocsBuildService::ROOT_FILES needs it too). Tested in scripts/install-sh.test.mjs (dry runs, generated stack parsed as YAML, deploy.sh with a stub docker, shellcheck) and end to end in an Ubuntu 24.04 VM. * docs: Docker first, as in #226, with the install script Ports #226 (Lance) to the Fumadocs site: - guides/docker becomes the top-level Getting Started (requirements, the virtualization check, Docker, swap), now opening with the one-command install. - panel/advanced/docker becomes panel/install, the recommended install: the install script (profiles, options, files, changing settings, updating, Wings on the same server, troubleshooting, backups) and then Docker Compose by hand, with #226's plugins volume and the note on the old ghcr.io/pelican-dev path. - The install without Docker moves to panel/standalone/*. - Redirects for the six old paths (netlify.toml, which the Hub's redirects.json is built from), inbound links, the sidebar, the OG motifs, ui/nav.json. - The AI guide's recommended prompt now drives the install script (asks the questions, writes the command, dry run first); the old prompt becomes the "Standalone install" tab. * feat(install): serve the Panel on the server's external IP by default, no domain needed Without --domain (or an empty answer), the Panel is served on http://<external IPv4> (found automatically, or --ip), with the quick profile and no other questions under --yes. A domain is still the way to HTTPS: give it at install, or later by running the script again with --domain/--email (keys, passwords and data kept) or setting PANEL_DOMAIN and LE_EMAIL and running deploy.sh. After the switch, plain HTTP to the old IP lands on the domain. - Traefik's routes now live in traefik/pelican.yml, written by deploy.sh from pelican.env (IP: the Panel on port 80 at any address; domain: HTTPS with Let's Encrypt, HTTP to HTTPS, Wings' domain). The Panel's APP_URL follows (PANEL_URL). Traefik no longer needs the Docker socket. - Wings without a domain is reached on http://<IP>:8080 (ufw opens it); with a panel domain it needs its own, as before. - The install waits for Swarm to finish rolling the services out before checking the Panel: a changed setting replaces the Panel, and the check used to reach the old one. - Traefik's healthcheck runs every 10s, so it counts as 1/1 sooner. Verified in the Ubuntu 24.04 VM: a fresh install with no domain, then adding a domain (and Wings on one), then back, checking the new Panel right after each. * feat(install): ask nothing by default, take PELICAN_* variables, pin Traefik The model Coolify and Dokploy use: the installer runs straight through and anything not given takes its default. - No questions unless --interactive (or PELICAN_INTERACTIVE=1), which asks for each choice with explanations and needs a terminal. With no options it installs the Panel on the server's IP, quick profile, no Wings. A domain without an email, or Wings without its domain next to a Panel domain, stops with the option and the variable to set. --yes is still accepted, unused. - Every option can be an environment variable (PELICAN_DOMAIN, PELICAN_EMAIL, PELICAN_PROFILE, PELICAN_WINGS, PELICAN_WINGS_DOMAIN, PELICAN_IP, PELICAN_DIR, PELICAN_IMAGE, PELICAN_STAGING, PELICAN_SKIP_DNS_CHECK, PELICAN_DRY_RUN, PELICAN_INTERACTIVE); the option wins. With sudo they go after it: curl ... | sudo PELICAN_DOMAIN=panel.example.com PELICAN_EMAIL=... bash - Traefik pinned to v3.7.19 (was the moving v3 tag). Running the script again moves an install to the version it pins; PELICAN_TRAEFIK_IMAGE for another. Docs and the AI prompt drop --yes and list the variables. Verified in the VM: the script piped into sudo with variables re-ran an install with no questions and moved Traefik to 3.7.19; --interactive answered through a pseudo-terminal. * fix(install): Macroscope's review: staging, Wings re-runs, saved subnet, dry runs, share image - Running again without --staging now moves a staging install to Let's Encrypt production (it kept the saved staging server). A CA set by hand is kept. Each CA gets its own certificate store (deploy.sh names it from LE_CA_SERVER), so staging certificates and the staging account don't carry over. - Re-running with Wings running no longer fails: the binary is downloaded to wings.new and renamed over the running one (writing to it gave "text file busy", curl exit 23, before the stack was deployed). - A second run keeps the PUBLIC_SUBNET saved in pelican.env (it reset it to 10.203.250.0/24, moving TRUSTED_PROXIES and the network) unless PELICAN_PUBLIC_SUBNET asks for another. - A dry run warns about example.com emails instead of stopping, so the docs' dry-run example works; a real run still refuses them. - The panel/install share image quotes lines that are on the page (it was dropped). New lib/og-motifs.test.mjs checks every motif against its page. Verified in the VM: a running /usr/local/bin/wings blocks the old download (curl exit 23) and not the new one; staging, then a run without --staging, switches caServer and the store to production.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #240 (it builds on its Hub look and its AI guide): review and merge #240 first, then this PR's base becomes
feat/fumadocs-next.Why
Installing the Panel by hand (PHP, a web server, certificates, the queue worker, cron) is where most new installs get stuck. The goal Scai set is the Coolify/Dokploy experience: one command on a fresh server gets you a working Panel with HTTPS. Afterwards you can change it in one place, and an AI assistant can drive it through plain options. #226 already makes Docker the recommended install on the old Docusaurus site. This PR brings that structure to the Fumadocs site and adds the script that makes Docker the easy path.
What changes
1.
pelican.dev/install.sh(public/install.sh)The Coolify/Dokploy model: it asks nothing. Anything not passed takes its default: the server's IP, the
quickprofile, no Wings. Every option is also aPELICAN_*environment variable (the option wins when both are set), which suits cloud-init and provisioning tools.--interactive(orPELICAN_INTERACTIVE=1) asks for each choice with explanations, and needs a terminal. A domain without an email, or Wings without its own domain next to a Panel domain, stops with an error naming both the option and the variable.--yesis still accepted but does nothing.No domain needed (the default): the Panel is served on
http://<the server's external IPv4>. The script finds that address itself (--ipto choose another, e.g. behind NAT), and the summary explains that this is plain HTTP and how to add a domain. Adding one later means running the script again with--domain/--email(keys, passwords and data are kept), or settingPANEL_DOMAIN+LE_EMAILinpelican.envand runningdeploy.sh. The Panel then switches to HTTPS, and plain-HTTP visits to the old IP are redirected (302) to the domain, path and query kept.Checks the server before touching anything: root; Linux on x86_64/arm64; a virtualization Docker works on (
openvz/lxcstop it); ports 80/443 free (or already this stack's Traefik); DNS pointing at the server.Installs Docker with Docker's script if it's missing, and starts a one-node Swarm.
Deploys the
pelicanstack from/opt/pelican:traefik/pelican.yml, whichdeploy.shwrites frompelican.env. Without a domain: the Panel on port 80 at any address. With a domain: HTTPS with a Let's Encrypt HTTP-01 certificate on the first request (renewed by Traefik), and HTTP redirected to HTTPS. Traefik doesn't need the Docker socket.APP_URLfollowing the mode (https://<domain>orhttp://<IP>),BEHIND_PROXY=true, andTRUSTED_PROXIESset to the overlay network it shares with Traefik (10.203.250.0/24).Profiles:
quick(SQLite) orproduction(MariaDB 11.4 + Redis 7 on an internal overlay network, passwords generated).--wings: installs Wings the way the Wings docs do (binary and systemd unit, enabled, started once configured). Without a domain, Wings is onhttp://<IP>:8080, andufwopens 8080 and 2022. With a Panel domain, Wings needs its own: Traefik routes it to the host'sdocker_gwbridgeaddress on port 8080, so Wings gets HTTPS with no certbot.Changing it afterwards: settings live in
pelican.env(0600),stack.ymlreads every value from it, anddeploy.shapplies them; runningdeploy.shagain also updates the Panel. A second run of the installer keepsAPP_KEYand the passwords, and refuses to switch profiles over existing data.For automation and LLMs: every answer is an option or a variable, nothing is required, and errors name the missing option.
--dry-runshows the plan and writes the files without root or any change to the server.Network decisions found while building it:
docker_gwbridgeis created on10.204.0.0/24beforeswarm init. Otherwise Docker gives it172.18.0.0/16, which is Wings'pelican_nw(the "Pool overlaps" error in Troubleshooting).10.203.0.0/16, not10.0.0.0/x, which cloud private networks use.Found by running it:
readTimeoutis raised to 600s; v3 defaults to 60s, which breaks large uploads.v3.7.19(the latest v3 release; Dokploy pinsv3.6.25). Running the script again moves an install to the version it pins;PELICAN_TRAEFIK_IMAGEchooses another.example.comcontact addresses, so those are rejected up front. (Seen on the first VM run.)Registered as a root file in
router/paths.mjs, socheck-paths,pack-docsand the router serve it; the README tables are updated.2. Docker first, as in #226
guides/dockerbecomes the top-level Getting Started (requirements, the virtualization check, Docker, swap). It now opens with the one command.panel/advanced/dockerbecomespanel/install: first the install script (profiles, options, files, changing settings, updating, Wings on the same server, troubleshooting, backups and removal), then Docker Compose by hand, with Make Docker the recommended Panel install #226'spelican-pluginsvolume and its note on the oldghcr.io/pelican-dev/panelpath.panel/standalone/*("Standalone Install").netlify.toml.pack-docsbuilds the Hub'sredirects.jsonfrom it, and I checked that all six are in the packed output.meta.json), the OG motifs andui/nav.json("Get started" and "Install guide" now go to Getting Started) are updated. The interim landing pages (/,/faq) are untouched; the redirects catch their old links.3. The AI guide drives the script
The recommended prompt in
guides/ai-assistantnow has the assistant:--dry-runfirst;pelican.env, firewall, Wings).The old prompt becomes the "Standalone install" tab, and the prompt URLs follow the new paths.
Screenshots
Verification
bun test: 138 pass, 0 fail.scripts/install-sh.test.mjsadds 23 tests, andlib/og-motifs.test.mjsadds 34: each share-image motif must quote text that is on its page, which stops a motif from being dropped quietly. They run the real script in--dry-run, parse the generatedstack.ymlwithyaml, and rundeploy.shagainst a stubdocker. They also run shellcheck oninstall.shand thedeploy.shit writes. One of them caught a real bug:${SWARM_NODE_ID}inside a[...]YAML flow list. Docker reads the YAML before filling in variables, so a real deploy would have failed.bun run typecheckpasses.bun run buildpasses:check-content36 pages, andcheck-paths: okwithout/install.shbyte-identical topublic/install.sh.curl | sudo …shape):cat install.sh | sudo PELICAN_DOMAIN=panel.pelican.test PELICAN_EMAIL=… PELICAN_STAGING=1 PELICAN_SKIP_DNS_CHECK=1 bashre-ran an install with no questions (stdin not a terminal). It kept the keys and moved Traefik fromtraefik:v3totraefik:v3.7.19, which its log confirms. Afterwards HTTPS answers 200, and the IP redirects to the domain.--interactivethrough a pseudo-terminal: answering an empty domain,productionandygave the Panel on the IP, the production profile and Wings on:8080.5dde764and checked in the VM:/usr/local/bin/wingsmakes the old download fail (curlexit 23, "text file busy"), and the installer now replaces the binary anyway.--stagingrun, then a run without it, movescaServerand the certificate store (acme-…staging….json→acme.json) to production.PUBLIC_SUBNET, a custom CA being kept, and dry runs with anexample.comemail.install.sh --ip 192.168.5.4: exit 0./installeranswers 200 onhttp://192.168.5.4, also with any other Host header.APP_URLishttp://192.168.5.4, and all 31 asset URLs on the page use it. Traefik's only mounts areletsencryptand/opt/pelican/traefik; no Docker socket.detect_ipfound the public address the VM is seen from.--domain panel.pelican.test --email … --wings --wings-domain node.pelican.test --staging: right after exit,https://…/installeranswers 200 andAPP_URLishttps://panel.pelican.test.http://panel.pelican.test/redirects 301 to HTTPS;http://192.168.5.4/installer?x=1redirects 302 tohttps://panel.pelican.test/installer?x=1; Wings' domain reaches the stand-in on 8080.pelican.envand re-running switches back tohttp://192.168.5.4, answering 200 right after exit.traefik:v3. The run used the real script as root:--profile production --wings --wings-domain node.pelican.test --staging --skip-dns-check, with the test domains in/etc/hosts.pelican_traefik,pelican_panel,pelican_databaseandpelican_cacheall at 1/1.docker_gwbridge10.204.0.0/24,ingress10.203.0.0/24,pelican_public10.203.250.0/24,pelican_internal10.203.1.0/24. Wings' 172.18.0.0/16 stays free.http://panel.pelican.test/returns 301 to https;https://…/installerreturns 200 through Traefik, and the page's assets load ashttps://(proxy trust works).https://node.pelican.test/through Traefik, reached from Traefik'sdocker_gwbridgeaddress10.204.0.3.wings v1.0.0-rc.2is installed andwings.serviceis enabled.pelican.envis 600,stack.yml644,deploy.sh700.APP_KEYand both passwords (same hashes); recognises its own Traefik on 80/443; updates the four services in place. The new log is 600 with no join token.pack-docshands the Hub all 6 new redirects andinstall.shas a root file.Not checked
--domain/--email.http://<IP>first, and checking sessions and passkeys after the switch.--ipand the address detection are IPv4 only.config.ymlhasapi.ssl.enabled: false.quickprofile live: it's covered only by the unit tests; the VM ranproduction, which includes everythingquickruns.firewalld(onlyufwrules are added); an existing multi-node swarm.pelican/hub'sDocsBuildService::ROOT_FILESneedsinstall.shbeforepelican.dev/install.shis served from Forge. Not changed here..mdaddresses: they have no redirects (only the HTML paths do).Note
Add one-command Pelican installer with Docker Swarm, Traefik, and Docker-first docs
PELICAN_*environment variables.panel/standalone, the Docker guide removed, and legacy paths redirected in netlify.toml. Servesinstall.shat the site root via router/paths.mjs.Macroscope summarized 5dde764.