8 ms·
One persistent issue I keep having is preview environments for this kind of stuff. I have the full setup, migrations, database seeding, etc. But having it run o
by xmonkee 5mo ago
One persistent issue I keep having is preview environments for this kind of stuff. I have the full setup, migrations, database seeding, etc. But having it run off a PR is still kind of a mess with spinning up 2 services, databases, redis etc. Do you guys run into this problem?
- yzhong94 5mo agoWe use firebase which supports the preview environments. It's mainly for front end changes though. Are you looking for a solution for backend changes as well?
- ManuelKiessling 5mo agoI‘ve built https://github.com/dx-tooling/productbuilding-orchestration https://github.com/dx-tooling/productbuilding-orchestration for more or less the same use case as Broccoli, but in my case a) the „frontend“ is Slack, not a ticket system (but the agent people talk to in Slack manages the ticket system under the hood), and b) everytime there is a new commit on a PR, a preview system is bootstrapped or updated, and the codebase that is to be previewed explains how it wants to be deployed for preview. This works really well.
- yzhong94 5mo agoI think it totally depends on the team on what the correct workflow is. The agentic workflow should accelerate what you have instead of asking your team to adopt something new. This is why we think it helps to own the orchestration yourself so you have that level of control!