Add Cut (self-hosted URL shortener)#914
Open
MendyLanda wants to merge 1 commit 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 Cut — a small self-hosted URL shortener (owner-only admin behind a single password, with per-link passwords, expiries, and click limits).
The template runs the published image
ghcr.io/mendylanda/cutwith a private Redis for storage.template.tomlgenerates the domain and a strongADMIN_PASSWORD, then maps thecutservice to port 3000. Redis runs withnoevictionsince it holds the actual links rather than cache data, so it shouldn't drop keys when memory fills up. Cut reads the request host at runtime, so nothing else needs configuring.Added
blueprints/cut/(docker-compose.yml,template.toml,cut.svg) plus themeta.jsonentry, sorted withnode dedupe-and-sort-meta.js. Compose follows the requirements:ports: - 3000(no host mapping), matchingcutservice name, nocontainer_name, no custom network.Checklist
Note on testing: I verified the stack directly with Docker Compose — the image builds, the container serves
/and/admin(both 200), and a/api/keepalivewrite lands in Redis. I don't have a separate Dokploy instance on hand, so I'm relying on this PR's automatic preview deploy to exercise the template itself. Happy to import the preview Base64 and confirm end-to-end if you'd like.Issues related (if applicable)
None.
Screenshots or Videos
The app running from the same two-container stack (app +
redis:7-alpine); the Dokploy preview deploy will show it inside Dokploy.