you can auto fill PUBLIC_APP_URL with "https://${{RAILWAYPUBLICDOMAIN}}" instead of asking the user to fill it in

you can auto fill PUBLIC_APP_URL with "https://${{RAILWAYPUBLICDOMAIN}}" instead of asking the user to fill it in

Thanks @brody, updated.

also noticed you use this with a turso database but you don't have a volume, thus no data will be persisted between deploys

Does the /data in Volume mount refer to the root of the app or root of the system? Would setting the default SQLite URL to file:data/sqlite.db and mount for /data work in this case?

the mount point given is mounted at the root of the container, I'm not too sure on the syntax for the file url though, you'd have to play around with that doing redeploys until you don't get errors and until data does persist

Thanks, I'm gonna inspect the container locally and check

@brody just confirming I was able to adjust the config and persist the SQLite, thank you for the help! Supso works now straight a way after 1-click deploy and Plunk API key paste 🙌

Supso seems cool. A̶n̶y̶ r̶e̶a̶s̶o̶n̶ y̶'a̶l̶l̶ w̶e̶n̶t̶ w̶i̶t̶h̶ P̶l̶u̶n̶k̶ a̶s̶ o̶p̶p̶o̶s̶e̶d̶ t̶o̶ a̶n̶ o̶p̶e̶n̶-̶s̶o̶u̶r̶c̶e̶ a̶u̶t̶h̶ s̶o̶l̶u̶t̶i̶o̶n̶?̶

I misread. Plunk seems to only be used to send emails?

Exactly, and post-MVP I'll add an option to provide SMTP config if someone doesn't want to use Plunk

awesome that you got the data persisting!

instead of asking for a SECRET_SQLITE_KEY you can use ${{secret(32)}} to auto generate a random 32 length string on template deployment.

https://docs.railway.app/guides/create#template-variable-functions