Chef-like deploys

Chef, for those who don't know, is a framework for automating the deployment of servers and their provisioning. IRL, I use it a fair amount in deploying AWS servers and other such things. That being said, something like that may be interesting to port to Lua and ComputerCraft for deploying turtles to specification automatically.

The main concerns here are versioning of scripts, updating turtles, idempotence of updating, and automated creation of new turtles tasked to certain elements.

Ideally I want to get some form of GPS Sync as well so I can let the turtles know their nearest refueling stations. Combine that with making them a bit more autonomous so as to carry out routed tasks and it could become quite interesting indeed.

Granted this would be very likely to kill a server with the type of strain it'd put on the server itself, but it's worth a shot.

So how out there is this idea, and any one else want to give it a shot? I'd likely host it on my github and use cloning instead of pastebin as pastebin has some serious drawbacks in this type of approach.

Moved to General. Ask a Pro is for help with problems/errors you're getting in a script.

It likely wouldn't be the "server killer" you think - ComputerCraft only runs the code of one system at a time, so no matter how many you have going at once the total CPU load never goes above that which would be raised by a single one running "flat out".

RAM concerns are a different story, but it all comes down to how many systems you intend to deploy, what they're actually doing, and what else they have to compete with (eg half a dozen chunk-loaded MystCraft ages).

I guess a good start would be to check out the self-replicating turtle package and see how it compares to what you're thinking of. In my case, I took some extremely large shortcuts by setting up bees to provide free resources of the type I wanted.

https://github.com/baweaver/tortuga

There's the base of the project at least. This is going to be a long haul but it should be quite entertaining indeed. Could I get some feedback on the layout of the API and the naming convention? I'll start filling it in fairly quickly over the weekend, I just wanted a framework online first. Yes, it is a bit documentation heavy, but the bigger a program may be the more it's good to write it early.

You can never have too much documentation, in my book - so long as it's easy to navigate. Indeed, with that "naming convention" it'll be well warranted - too many pirate movies, for sure! ;)/>