Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions
Justin Hunter
@polluterofminds
I was all in on Railway, but I've had way too many frustrations with it. Things that SHOULD just work often don't and debugging is hard since you don't have access to the shell console for the server (which originally I thought was a great thing). I've moved as much of my backend code to Cloudflare workers and if I need long-running processes, I'm back on Digital Ocean.
6 replies
1 recast
11 reactions
Stephan
@stephancill
What’s your digitalocean setup for long running tasks?
1 reply
0 recast
2 reactions
Justin Hunter
@polluterofminds
As an example, for Orbiter, we use digital ocean for setting up nginx configs for each site with a custom domain and issuing ssl certs. Granted that's about more than long-running processes (we need access to disk). But I also use DO for cron jobs and background processes or API endpoints I know will take a long time to return.
1 reply
0 recast
1 reaction
Stephan
@stephancill
so do you just run it directly? no self hosting framework like coolify?
1 reply
0 recast
1 reaction
Justin Hunter
@polluterofminds
Just run it myself. SSH in, pull down the code, start the server, then use pm2 or systemctl to monitor and restart automatically
0 reply
0 recast
1 reaction