Add one-click deploy button (on Railway) to README

[morgangallant]

Gives users an additional method of deploying tclip, and arguably, an easier one than many other methods. Template is pre-configured with a disk & correct mount paths, simply need to copy+paste value for TS_AUTHKEY and should be good to go.

Also note: Railway has a kick-back program and this link technically has my referral code in it. Opened this PR not for this reason (don't expect any kickback whatsoever nor do I care about this), but because I legitimately think Railway is the most convenient way to deploy stuff like this :)

[Xe]

Does that Railway template save data? tclip uses sqlite and IIRC Railway uses the Heroku model where there's the implicit suggestion of no persistent state on disk.

[morgangallant]

Yep — that template configures & mounts a persistent disk to the service automatically! Recent ship by our friends at Railway <3

…

On Wed, Sep 20 2023 at 11:20 AM, Xe Iaso < ***@***.*** > wrote: Does that Railway template save data? tclip uses sqlite and IIRC Railway uses the Heroku model where there's the implicit suggestion of no persistent state on disk. — Reply to this email directly, view it on GitHub ( #38 (comment) ) , or unsubscribe ( https:/notifications/unsubscribe-auth/ACAFA32PBZHKBPBJCS2HB6TX3MXXNANCNFSM6AAAAAA5AJ4JW4 ). You are receiving this because you authored the thread. Message ID: <tailscale-dev/tclip/pull/38/c1728226923 @ github. com>

[Erisa]

Hi @morgangallant, sorry for the extreme delay here!

I was looking into this, and noticed that the Railway template doesn't expose all of the configuration options available (many are new) in tclip: https:/tailscale-dev/tclip?tab=readme-ov-file#configuration - if these could be added that would be great.

I also realised that Railway templates don't seem to be stored in a public version-control system like I thought they once were, and there is no way for me to propose changes to it. I did notice it's possible by manual request to transfer ownership of a template, but not certain this helps too much.

In the meantime while I deliberate how best to handle that problem going forward, would you be able to add support for the new configuration variables to the existing template? Then we can probably have it on the README. Thank you!