Skip to content

docs: deploy pages align setup wording and name every persistent volume (issue #57) - #66

Merged
SebConejo merged 3 commits into
mainfrom
fix/issue-57-deploy-wording
Aug 18, 2026
Merged

SebConejo merged 3 commits into
mainfrom
fix/issue-57-deploy-wording

Conversation

@SebConejo

@SebConejo SebConejo commented Aug 15, 2026 •

Copy link
Copy Markdown
Member

Applies the recommended options of #57 (batch pass, 2026-08-15):

  1. Seven deploy pages (gcp, coolify, aws, digitalocean, render, koyeb, railway) adopt the setup-screen wording heroku and easypanel already ship: "Fresh installs redirect to /setup; the first account you create becomes the admin."
  2. Coolify names the request-logs volume in "What Gets Provisioned" and the backup note covers both volumes.
  3. GCP gains a "Request logs" note (private Cloud Storage bucket, recording_bucket output) and a teardown bullet (contents retained; export or delete before deploystack uninstall).

Coherence: GREEN. Closes #57.

…me (issue #57)

Seven pages adopt the setup-screen wording heroku and easypanel already
ship. Coolify names its second volume (request logs) in provisioning and
backup. GCP documents the provisioned Cloud Storage bucket and its
retained contents at teardown.
The path is internal plumbing; backing up a Coolify volume or managing
the GCP bucket doesn't need it. The recording_bucket output name stays.
Also merges main.
@SebConejo
SebConejo merged commit 5a22857 into main Aug 18, 2026
1 check passed
@SebConejo
SebConejo deleted the fix/issue-57-deploy-wording branch August 18, 2026 09:57
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.

Docs audit — deploy platforms — 2026-08-13

1 participant