So a bit like having a staging and a production environment, then always deploy the non-main branches to staging, and staging environment is always accessible via the same subdomain (e.g. staging.example.com).
Is that what you mean?
I guess that could work as long as each developer had their own separate staging environment.
Hi 👋 Anna here! I post about cloud, opensource projects that interest me, and loosely related stuff. I also build weird and wonderful, mostly cloudy opensource projects when the mood takes me :)
Yeah I think fir solo devs it’s probably good enough to have just one staging env.
Though integrating route53 would be really awesome because you could send links to clients for them to test out work in progress, and have multiple preview branches live at the same time.
I’d love to see a simple and clear tutorial on how to use route53 in that way. Perhaps you can recommend one?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
So a bit like having a staging and a production environment, then always deploy the non-main branches to staging, and staging environment is always accessible via the same subdomain (e.g. staging.example.com).
Is that what you mean?
I guess that could work as long as each developer had their own separate staging environment.
Yeah pretty much though you could go as complicated or as simple as you want.
Yeah I think fir solo devs it’s probably good enough to have just one staging env.
Though integrating route53 would be really awesome because you could send links to clients for them to test out work in progress, and have multiple preview branches live at the same time.
I’d love to see a simple and clear tutorial on how to use route53 in that way. Perhaps you can recommend one?