feat(templates): add systemprompt#1032
Open
Ejb503 wants to merge 2 commits into
Open
Conversation
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
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.
What is this PR about?
New PR of systemprompt — a self-owned AI control plane: a governance gateway for Claude, OpenAI, and Gemini with policy checks, audit trails, rate limits, and MCP orchestration.
blueprints/systemprompt/(docker-compose.yml, template.toml, meta.json, logo.svg, instructions.md)ghcr.io/systempromptio/systemprompt-template:0(multi-arch amd64/arm64)systemprompt, port 8080) +postgres:18-alpine, both with healthchecks and persistent volumestemplate.tomlgenerates a 32-char Postgres password, binds a domain tosystemprompt:8080, and derivesEXTERNAL_URLfrom itANTHROPIC_API_KEY/OPENAI_API_KEY/GEMINI_API_KEY), exposed as empty env vars to fill in before first deployinstructions.mdcovers the two setup requirements: a provider key before first deploy, and HTTPS enabled on the domain (the app validatesEXTERNAL_URLand rejects plain-http non-localhost origins)Checklist
Before submitting this PR, please make sure that:
Issues related (if applicable)
None.
Screenshots or Videos
Testing notes (fresh Dokploy install via install.sh on a 2GB VM):
https://<domain>/api/v1/health→ 200, admin UI loads.POST /v1/messages→ 200) with audit rows recorded.node build-scripts/generate-meta.js --checkpasses (494 templates), and bothbuild-scripts/validate-docker-compose.tsandvalidate-template.tspass on this blueprint.