27 Replies
dont close
the cli doesn't have this functionality, do you think you could share your usecase, maybe I would be able to come up with an alternative solution
Okay.
I have a discord bot running it fetches information from reddit and sends to discord, occasionally reddit will return an error, which my code isn't handling at the moment. The error interrupts the info stream to discord. While i figure out how to handle the error properly and investigate it with reddit, I've found that simply redeploying resumes the bot functionality.
So i just needed it to be redeployed easily and cli seemed faster to me had there been a single command, just more clicks on the website
gotcha, how were you planning to automate the restart?
Just hoping there was a command like "railway redeploy" or something
right but where would you be running that command from?
Probably more beneficial or productive to work in error handling than designing a function (on another client?) to monitor it and redeploy it every time.
I don’t disagree with doing a lot of things, but this just seems like a waste of time compared to prioritizing error handling.
I'm in major agreement with jack, but if you want to go down the route of just restarting the service, you would need to use Railways public API
Even so, if you wanna share the function snippet that’s not being handled, I’d be happy to look at it for you and see what I can do.
From my terminal?
Yeah i agree, this was just in the meantime while i get time to work on that code
Gotcha
Don't you think redeploy should be a functionality in the cli though?
Also, what's the difference between a redeploy and restart
Why not redeploy it on the site then?
Would be faster through the cli
Multiple clicks required on the website
Redeploy will pull the image again in another deployment (I believe) while restart will just restart your current deployment.
I see
I mean, so far the usecase is to get around improper error handling, so that doesn't bode too well as a reason to implement such a feature
In your case, you’d just need to restart it.
Nah, like outside of that
Thanks
Not a horrible idea for the future and expansion of the cli, but not a priority either.
Feel free to put that in #🤗｜feedback or open a feedback thread on https://help.railway.app/feedback
Yeah for sure. If its an interface, it should mirror most functionalities as on the website
Thanks
Curious to know why the disagreement on this? @Brody @Jack
The cli is not an interface, it’s designed to make CI/CD possible and allow developers to integrate things like local development and remote deploys. It’s not designed or upheld to be an alternative to the website or interface in any way.
I see
The cli is open source in addition, so feel free to also provide any feedback there for maintainers or community members to see, but unless there’s popular interest in something, it’s likely to get pushed away.
took the words off of my keyboard
Good to know!
nah let's just add one more command. more features is better 😁
Solution
sure sounds good to milo - https://github.com/railwayapp/cli/pull/510