Open
Conversation
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
Author
The The This duplicate in |
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.
Description
Adds a deployment template for Rustrak, an ultra-lightweight, self-hosted error tracking system compatible with Sentry SDKs.
abians7/rustrak-server:latest+abians7/rustrak-ui:latestServices
rustrakabians7/rustrak-server:latestuiabians7/rustrak-ui:latestWhat gets configured automatically
ui), one for the API (rustrak)SESSION_SECRET_KEY)CREATE_SUPERUSERrustrak-data:/data)SSL_PROXY=truesince Dokploy terminates SSL via its reverse proxyFiles added
Testing notes
Related
Greptile Summary
This PR adds a new Rustrak template (a self-hosted Sentry-compatible error tracking tool with a Rust backend and Next.js UI) to the Dokploy template library. The
template.tomland SVG logo are well-formed and follow project conventions, but there are three issues that need to be addressed before merging:portsinstead ofexposeindocker-compose.yml: Both therustrakanduiservices declareportsmappings, which is explicitly prohibited by the project guidelines. Dokploy manages all routing via its reverse proxy, soexposemust be used instead.abians7/rustrak-server:latestandabians7/rustrak-ui:latestuse:latest, violating the guideline to pin images to a specific version to prevent supply-chain attacks. Theversionfield inmeta.jsonshould also reflect the pinned tag rather than"latest".meta.jsonentry: The existing Strapi template entry was removed frommeta.jsonin this PR. The blueprint files still exist on disk but Strapi will be invisible to users until the entry is restored. This was likely an unintended side-effect of runningdedupe-and-sort-meta.jsor a manual merge conflict resolution.Confidence Score: 1/5
portsconvention violation must be fixed first.meta.jsonis a regression that would break an existing, working template for all users. Theportsdirective is a clear guidelines violation that would cause incorrect networking behaviour in Dokploy deployments.meta.json(Strapi deletion) andblueprints/rustrak/docker-compose.yml(ports→expose, unpinned images).Last reviewed commit: bc7879f
(2/5) Greptile learns from your feedback when you react with thumbs up/down!
Context used: