2 posts tagged with "Operations"

In part 5 you ran Hydra by hand: build the images, run a stage with dev-run.sh, label an issue. That is the right way to learn Hydra, but it is not how it runs day to day. In production nobody starts containers from a terminal. Instead a scheduled flow notices the labelled issue and has each stage run for it, with no one at the keyboard. This part explains that path, where the pre-built images fit in, and the three deployment models behind it.

The first four parts were about concept, pipelines, gates and skills. Time to actually run. On your own machine you run Hydra's stages as containers: one stage at a time, or the whole chain against a throwaway repo. A real run on a real app starts with a label, and the flows from part 7 carry it from there. This part covers both, with the practical pitfalls: credentials, the forge setting, and images.