a year ago
I want to enable automatic deployments to always happen. Right now I have to manually trigger them in the dashboard anytime someone puts up a pr or a pr is merged.
It seems there is a specific deployer roll but we have a few part time contributors that submit maybe 1 or 2 PR's per month. I have just moved all our environments to railway and it does not make sense to add 10-20 part time people to the team, not to mention the $20 per month cost for that too.
Not to mention they would then have access to all the different environments including production which is only allocated to 2 people in the enitre company, or CTO and me.
I tried searching but couldnt find a solution. Cheers
15 Replies
Its also annoying to have to manually click the deploy button for a PR environment
Hey
At this time it will be a feature request rather than something we can help you here.
However, you can circumvent that role bs by using the CLI with GitHub Actions to deploy your repo
a year ago
Cc @oldbettie We removed seat costs for this reason, are you on metal yet?
a year ago
We just paused migrations (capacity…) but once you move over, you should not be charged per seat
a year ago
Then you can add as many people as you want
There is also the other reason. Having everyone that contributes code to our project in the team just doesnt make sense. There is only 2-3 people that contribute often but we have 20 specialist people that from time to time work on specific features.
a year ago
I don’t know, I think it makes sense for all devs to see logs of what may have done wrong?
a year ago
If role is a concern, then that’s a different story
a year ago
The reason why we have this system in place was for security, so that only authorized employees trigger a deploy.
Most projects have rules in Github that protect us. IE can only be merged to production if one of the full time staff approves the PR. We should not have to 1. Approve PR 2. merge the PR 3 go to another site and deploy the latest changes. Its just added steps that will be forgotten. It sounds like I can setup github actions to do it so that is likely the path forward for us
a year ago
i've gone ahead and removed the requirement for approvals on your team
a year ago
!s
Status changed to Solved brody • 11 months ago