docs: add community Railway self-hosting option - #111
Conversation
6ba6180 to
c0f4248
Compare
sorcerai
left a comment
There was a problem hiding this comment.
Current head fails the repository gate on exact main+#153: pnpm ci:check reports a Prettier violation in README.md. Please format the README change and rerun ci:check; the Railway documentation content and security warning otherwise look safe.
Link the community Railway one-click template from the README and add a short self-hosting guide covering volume persistence, local_noauth, and update tips.
Co-authored-by: Cursor <cursoragent@cursor.com>
c0f4248 to
74e6cb8
Compare
|
Rebased onto latest main and fixed the Prettier formatting in README.md. I re-ran pnpm ci:check and it passes. |
|
Closing because this is default not secure since Railway doesn't have a "Cloudflare Access" type feature. I'm working on a better way to deploy to services like Railway securely, just may be a few weeks. |
|
Updated the community template so it's password-gated by default (Gate service + SITE_PASSWORD in front of OpenSEO). Docs in this PR match that. Reopened for another look. |
Summary
docs/SELF_HOSTING_RAILWAY.mdcovering the GHCR image +/app/.wranglervolume, DataForSEO key,local_noauthsecurity note, and Image Auto UpdatesContext
OpenSEO already ships a Docker self-host path (
ghcr.io/every-app/open-seo). This template wraps that same image on Railway so people can one-click deploy with persistence. Happy to adjust wording/placement if you'd rather keep Railway out of the main README or link only from Discord.Test plan
docs/SELF_HOSTING_RAILWAY.mdlinks resolve