hmmm, i'm getting some like:

Mozilla/5.0 (iPod; U; CPU iPhone OS 4_3 like Mac OS X; as-IN) AppleWebKit/532.43.7 (KHTML, like Gecko) Version/3.0.5 Mobile/8B119 Safari/6532.43.7
Opera/9.82.(X11; Linux i686; mg-MG) Presto/2.9.176 Version/11.00
Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10_11_5; rv:1.9.5.20) Gecko/3574-09-12 00:50:37.474434 Firefox/3.6.2
Mozilla/5.0 (X11; U; Linux ppc; fr; rv:1.9.2.12) Gecko/20101027 Ubuntu/10.10 (maverick) Firefox/3.6.12

I posted this in the Terranix channel, but am hoping to get more eyes on it - sorry for double posting!

The high level idea I have is as follows:

1. Orchestrator flake: sources all other flakes using input following. Hydra builds this flake, and some cron job regularly runs flake update to pick up new changes to all packages in the pipeline.
2. Pipeline flake: a set of impure builds with a sequential dependency chain that are responsible for executing terraform plan and apply for each stage. These builds would use something like fixed output derivations with a fake hash to skirt network sandboxing. Integration tests would also be represented this way.
3. Infrastructure flake: defines the terranix infrastructure, gets used by the various pipeline stages for deployment.
4. Application flakes: flakes that define how to build and package application code, these get used by the infrastructure flake.

Then configure Hydra, and one machine should be able to act as a full devops pipeline?

This should let developers easily work on any subset of the system in a local workspace by modifying the flake inputs, as well as allowing things like manual deployments for rollbacks or emergency situations. There might be flaws with this idea, but I am curious to hear what folks think