Better documentation for local deploy

[dzonerzy]

Hi,

I'm opening this issue because documentation about local instance is not complete imo, I was able to run a local instance with:

python butler.py run_server

And then a bot instance using:

python butler.py run_bot --name my-bot /path/to/my-bot

And finally I tried with heartbleed example and it works like by documentation. Pretty easy till this point, anyway is not specified how to scale this "local" clusterfuzz instance for example I have multiple computer it's possible to run multiple bots connected to the main clusterfuzz instance? There is a way to start clusterfuzz and bots with systemd (as a service), a bot can run mutiple tasks? Can I specify which bot should run a specific task? There's a configuration file where I can set all those things? It's possible to access clusterfuzz from another PC in the same lan without port-forwarding / vnc or similar? I can't find an answer to those kind of question inside the documentation, can someone point me on the right way?

Thanks much

[mbarbella-chromium]

We didn't intend for the local instance instructions to be a starting point to scaling up, it's meant more as a simple proof of concept to demo ClusterFuzz. https://google.github.io/clusterfuzz/production-setup/ has the current documentation for the steps we expect people to follow for setups like the one you described.

That said, this has been a pretty common feature request. I think it's at least worth considering documenting a small local cluster, though the tools we're using such as App Engine's dev appserver aren't well suited to it. I'll keep this open for now, but at least in the short-term it's a fairly low priority.