Content
@
0 reply
0 recast
0 reaction
Samuel ツ
@samuellhuber.eth
Whats the best Vercel like deployment experience using your own servers? vServers or something like Hetzner Cloud I want to quickly have PoC's up and updated via CI/CD including previews for different branches easy view of console.log() / console.error() output would be a lovely bonus
5 replies
0 recast
6 reactions
Paul Dowman 🔴✨
@pauldowman.eth
Try feature flags instead of long lived branches and then you won’t need the branch deployment thing. It sounds counter intuitive but once you really embrace continuous deployment you’ll never go back. The branch deployment thing doesn’t work at scale anyway.
1 reply
0 recast
0 reaction
Samuel ツ
@samuellhuber.eth
oh I only need that for previews on merge requests and the dev branch having a dev branch + seperate master for prod is helpful when working with multiple devs
1 reply
0 recast
0 reaction
Paul Dowman 🔴✨
@pauldowman.eth
Maybe a hot take (though it’s standard in “big tech”), but IMHO a dev branch is an anti-pattern, as is any long-lived branch. Going all-in on continuous deployment is the only thing that scales. (Also works well even on small teams and projects, but requires some automated tests and other practices)
2 replies
0 recast
0 reaction
Samuel ツ
@samuellhuber.eth
one question that comes up now that I am mapping it out is how do you go for a complete redesign? thats also a feature branch that then closes? staging environment also not needed or basically just a shortlived branch too? one may want deployments of that to pass around to customer before going to master
1 reply
0 recast
0 reaction
Paul Dowman 🔴✨
@pauldowman.eth
I wouldn't go all the way without solid automated tests (and if at scale you need "canary" deployment too) so staging is still useful in the meantime, but only for testing the main branch before it goes live. For showing a version that's not rolled out I recommend feature flags.
1 reply
0 recast
0 reaction
