Plusagency-v3.4.zip 🎉

# 3️⃣ Launch docker compose up -d

Happy building! 🚀

# 5️⃣ Optional – add a plugin cd plugins npx plusagency-plugin init my-plugin # develop, then restart backend docker compose restart backend You now have a fully functional PlusAgency v3.4 instance, a clear path to extend it with custom plugins, and a production checklist to keep it secure and performant. Dive in, experiment with the AI suggestions, and start modeling your content—your headless CMS adventure begins here. plusagency-v3.4.zip

cp .env.example .env # Edit with your favourite editor code .env Key variables you’ll likely tweak:

my-awesome-plugin/ ├─ src/ │ ├─ index.ts │ └─ routes.ts ├─ package.json └─ plusagency-plugin.json # metadata for marketplace # In the plugin directory npm install npm run dev # hot‑reload with ts-node The backend automatically discovers plugins in plugins/ at start‑up. If you add a new plugin while the stack is running, just restart the backend: # 3️⃣ Launch docker compose up -d Happy building

| Variable | Default | What to change | |----------|---------|----------------| | POSTGRES_PASSWORD | plusagency | Use a strong password for production | | PLUSAGENCY_ADMIN_EMAIL | admin@example.com | Your admin login | | PLUSAGENCY_ADMIN_PASSWORD | changeme | Strong password (will be required on first login) | | AI_PROVIDER | openai | Set to local if you run the bundled Ollama model | | OAUTH_CLIENT_ID / OAUTH_CLIENT_SECRET | — | Fill only if you enable SSO | Never commit the .env file to a public repo. For production, inject secrets via Docker secrets or a vault solution. 3.4 Spin Up the Stack docker compose up -d Docker will pull the official images (or build the local ones if you have a Dockerfile under backend/ / frontend/ ). Wait a few seconds, then check health:

plusagency/ ├─ backend/ # Node.js API service ├─ frontend/ # React admin UI (served via Nginx) ├─ plugins/ # Official + community plugins ├─ docker-compose.yml # Orchestrates all containers └─ .env.example # Sample environment file Copy the example file and adjust values for your environment: experiment with the AI suggestions

# 4️⃣ Verify open http://localhost:8080 # admin UI curl -X POST http://localhost:8080/graphql \ -H "Content-Type: application/json" \ -d '"query":" __schema queryType name "' | jq .

# 2️⃣ Configure cp .env.example .env # edit .env → set ADMIN_EMAIL/PASSWORD, POSTGRES_PASSWORD, etc.

# 3️⃣ Verify the layout tree -L 2 . You should see: