Add settings.json and Dockerfile COPY — implement missing PR #2 changes

[Copilot]

PR #2 ("Add persistent settings.json for Etherpad") was merged but its sole commit was an empty "Initial plan" — settings.json was never created and Dockerfile was never updated. Settings were still being wiped on every Appliku redeploy.

Changes

• settings.json — Adds full Etherpad config committed to the repo:

  • Colibris skin, "title": "Invisible Notes", dark mode enabled
  • DB connection via ${DB_*} env-var placeholders (set in Appliku dashboard)
  • Admin/user accounts keyed to ${ADMIN_PASSWORD} / ${USER_PASSWORD} env vars
  • Pad defaults, rate limiting, cookie config, SSO client stubs

• Dockerfile — Adds the COPY that was always the point of this work:

  FROM etherpad/etherpad:2.6.1
  COPY settings.json /opt/etherpad-lite/settings.json

Without this COPY, the base image's default settings.json overwrites any edits on every redeploy. With it, the committed config is baked into the image and survives redeployments.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[Copilot]

Pull request overview

Adds a committed Etherpad settings.json and ensures it is baked into the container image so configuration no longer resets on redeploys (addressing the missing implementation from PR #2).

Changes:

• Add a full settings.json configuration for the Etherpad instance (title/skin/db/auth/rate limits/etc.).
• Update the Dockerfile to COPY the repository’s settings.json into /opt/etherpad-lite/settings.json.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
settings.json	Introduces the intended persistent Etherpad configuration (env-var-driven DB creds, UI defaults, auth/user stubs).
Dockerfile	Bakes the committed settings.json into the Etherpad image to prevent resets on redeploy.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The default password fallback ${ADMIN_PASSWORD:null} / ${USER_PASSWORD:null} will evaluate to the literal string "null" when the env var is missing, which creates a well-known weak credential if the deployment is misconfigured. Prefer having no default (so startup/login fails clearly) or choose a non-guessable default and document that ADMIN_PASSWORD/USER_PASSWORD must be set in the deployment environment.

Suggested change

	"password": "${ADMIN_PASSWORD:null}",
	"is_admin": true
	},
	"user": {
	"password": "${USER_PASSWORD:null}",
	"password": "${ADMIN_PASSWORD}",
	"is_admin": true
	},
	"user": {
	"password": "${USER_PASSWORD}",