Skip to content

Make Docker the recommended Panel install - #226

Closed
lancepioch wants to merge 2 commits into
mainfrom
docs-docker-first
Closed

lancepioch wants to merge 2 commits into
mainfrom
docs-docker-first

Conversation

@lancepioch

@lancepioch lancepioch commented Oct 13, 2026 •

Copy link
Copy Markdown
Member

Based on the direction proposed in #172 (thanks @felinusfish). Stacked on #225; it will retarget to main once that merges.

  • New top-level Getting Started page: requirements, the virtualization check, installing Docker, starting it on boot, and swap (built from guides/docker.mdx, which is removed)
  • The Docker guide moves to /docs/panel/install and is now the recommended method
  • Standalone pages move to /docs/panel/standalone/* under a "Standalone" sidebar category
  • Inbound links, the homepage Install button, the footer, and the FAQ are updated
  • Redirects for every old URL: guides/docker, panel/advanced/docker, panel/getting-started, panel/webserver-config, panel/panel-setup, panel/optional-config

Wings stays a binary + systemd install.

npm run build passes with onBrokenLinks: "throw".

Note

Make Docker the recommended Panel install and restructure docs

Reorganizes the docs site to present a top-level Getting Started page and a Panel installation page built around Docker, replacing the former Panel setup and Docker guide pages.

  • Updates the sidebar in sidebars.ts: adds Getting Started at the top level, adds a Standalone category, and removes the old Docker pages from Advanced and Guides.
  • Adds redirects in docusaurus.config.ts for six legacy URLs (Docker guide, Panel Docker guide, standalone getting-started, webserver config, Panel setup, optional config) to their new paths.
  • Updates all internal links across the guide pages, the FAQ, and the homepage Install button to point to the new paths.
  • Risk: external sites linking to the old Docker guide or webserver config URLs depend on the new redirects in docusaurus.config.ts; verify all six entries match the old slugs.

Macroscope summarized 6d74fb7.

Summary by CodeRabbit

  • Documentation
    • Reorganized installation guidance around Docker as the recommended approach, with a separate path for installing Pelican directly on a server.
    • Expanded Getting Started with Linux server requirements, virtualization guidance, and links to the next installation steps.
    • Updated migration, SSL, troubleshooting, and advanced setup guides to point to the relevant current instructions.
    • Updated navigation and redirects to help readers reach the revised documentation from existing links.

@coderabbitai

coderabbitai Bot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 58 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 36043086-7a4b-4cfe-832d-529aa9fa1a29
Commits

Reviewing files that changed from the base of the PR and between 5bc2d54 and 6d74fb7.

Files selected for processing: 1

  • docs/panel/install.mdx

No actionable comments were generated in the recent review.

Walkthrough

The documentation now presents Docker as the recommended Panel installation method and direct installation as a standalone option. The sidebar, redirects, site entry links, and related guide links use the revised documentation paths.

Changes: Panel installation documentation

Layer / File(s) Summary
Installation entry points
docs/getting-started.mdx, docs/panel/install.mdx, docs/panel/standalone/getting-started.mdx, docusaurus.config.ts, src/pages/faq.mdx, src/pages/index.tsx
Getting Started adds Docker prerequisites and next steps. The Panel installation page recommends Docker and links to standalone installation. Site links and the standalone page title are updated.
Standalone navigation and paths
sidebars.ts, docusaurus.config.ts, docs/panel/standalone/panel-setup.mdx, docs/panel/update.mdx, docs/versioning.mdx
The sidebar groups standalone pages and removes the former Docker entries. Redirects and related page references use the revised paths.
Guide reference updates
docs/guides/*, docs/panel/advanced/cloudflare-tunnel.mdx, docs/panel/advanced/podman.mdx, docs/wings/install.mdx
Migration, SSL, troubleshooting, Cloudflare Tunnel, Podman, and Wings documentation links point to the revised installation pages.

Estimated code review effort: 2 (Simple) | ~12 minutes

Change: Other

Merge Risk: Minimal · previous review 5bc2d

The revised installation path and legacy documentation links show no concrete change-specific failure; normal site checks are sufficient before merging.

Pre-merge checks: Passed 4 · Failed 1

Failed Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 3 files. (13 skipped: 1… Write docstrings for the functions missing them to satisfy the coverage threshold.
Passed Passed checks (4 passed)

Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly and concisely describes the main change: making Docker the recommended Panel installation method. It matches the documentation reorganization and updated links, navigation, and redir…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 3 files. (13 skipped: 13 unsupported.)

Finishing Touches

🧪 Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

A rabbit checked the docs at dawn,
Then hopped where Docker guides were drawn.
“Standalone paths are clear,” it said,
And tucked the links beneath its bed.
It nibbled carrots, pleased and fed.

ℹ️ Recent review info

⚙️ Run configuration

  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: eefe170d-7f35-4fef-a929-708cdc186877
📥 Commits

Reviewing files that changed from the base of the PR and between 0159e42 and 5bc2d54.

📒 Files selected for processing (18)

  • docs/getting-started.mdx
  • docs/guides/migrating-from-pterodactyl.mdx
  • docs/guides/ssl.mdx
  • docs/guides/troubleshooting.mdx
  • docs/panel/advanced/cloudflare-tunnel.mdx
  • docs/panel/advanced/podman.mdx
  • docs/panel/install.mdx
  • docs/panel/standalone/getting-started.mdx
  • docs/panel/standalone/optional-config.mdx
  • docs/panel/standalone/panel-setup.mdx
  • docs/panel/standalone/webserver-config.mdx
  • docs/panel/update.mdx
  • docs/versioning.mdx
  • docs/wings/install.mdx
  • docusaurus.config.ts
  • sidebars.ts
  • src/pages/faq.mdx
  • src/pages/index.tsx

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details

🧰 Additional context used

🪛 LanguageTool

docs/getting-started.mdx

[style] ~22-~22: Consider an alternative to avoid wordiness and to strengthen your wording.
Context: ...ntainers. kvm and bare metal (none) work without issues. To check what your server uses, run: ...

(WORKS_WITHOUT_PROBLEMS)

macroscopeapp[bot]
macroscopeapp Bot previously approved these changes Oct 13, 2026
@macroscopeapp

macroscopeapp Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Approvability

Verdict: Approved at 6d74fb7

Macroscope's review found this PR approvable — Makes Docker the recommended installation path while retaining standalone instructions and redirects for old documentation URLs. Changes affect documentation and example configuration, without automatically modifying existing deployments or data.

You can add or adjust custom eligibility rules. Learn more.

@lancepioch
lancepioch added this pull request to stack #227 October 13, 2026 17:45
@netlify

netlify Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for pelica ready!

Name Link
🔨 Latest commit 6d74fb7
🔍 Latest deploy log https://app.netlify.com/projects/pelica/deploys/6aee1f310705b36f9034e7f0
😎 Deploy Preview https://deploy-preview-226--pelica.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Base automatically changed from docs-welcome-cleanup to main October 13, 2026 17:48
Add a top-level Getting Started page (requirements, virtualization check,
installing Docker) built from the old Docker guide, promote the Docker
Panel guide to panel/install, and move the standalone pages under
panel/standalone. Update inbound links, the homepage Install button and
the footer, and redirect every old URL.

Based on the direction proposed in #172.

Co-authored-by: Erik Balchunas <felinusfish@gmail.com>
@macroscopeapp
macroscopeapp Bot dismissed their stale review November 6, 2026 18:40

Dismissing prior approval to re-evaluate 6d74fb7

alexevladgabriel added a commit that referenced this pull request Nov 15, 2026
…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.
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.
@alexevladgabriel

Copy link
Copy Markdown
Member

Closing in favor of #234

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants