7 months ago
Hi all!
I'm work at Wasp, and we've recently introduced first-class support for Railway deployments.
This feature allows users to run a single command to:
Authenticate with Railway
Create a Railway project and link it to their Wasp project
Deploy and setup the Wasp app on Railway (client, server, db…)
We want to test this feature in our CI, which means we need a way to perform these steps:
Non-interactively
With team/workspace scope privileges
The main problem comes from railway init not working with a team/workspace-scoped token.
So, my question is: How can I create a railway project non-interactively with team-scoped authentication?
Even if we compromise and use account scope instead of team scope, railway init will ask for interactive user input when choosing the workspace.
More details on the issue: https://github.com/wasp-lang/wasp/issues/3022
Thanks for making Railway BTW, it's great!
Filip
8 Replies
7 months ago
Hello @Filip - I've added a --workspace flag to the init command, let me know if you think that addition will help you here.
Note: an account token is going to be required due to how the command fundamentally works, changing that would be out of scope for now.
Thanks!
Yes, that's great. Ideally we'd be able to use a workspace token, but this is a very reasonable compromise.
When can we expect to see it in the CLI?
7 months ago
I'll merge it now and then ask product to cut a release.
7 months ago
7 months ago
No problem! let us know if ya'll run into any other blockers!
7 months ago
!s
Status changed to Solved brody • 7 months ago