Difference between revisions of "Deployment research"
(Moving "deployment research" off of the internal teamspace page) |
(Fixing "jurisdiction management" link to point to teamspace) |
||
| Line 5: | Line 5: | ||
== Fabric? == | == Fabric? == | ||
| − | (Old stuff from [ | + | (Old stuff from [http://teamspace.creativecommons.org/Jurisdiction_Management Jurisdiction Management]) |
=== On live === | === On live === | ||
Revision as of 20:58, 16 March 2011
In the future, deployment will happen at the touch of a button. If you want a new server set up, you will just touch this button, several magical woodland fairies will be sacrificed to the elder gods, and a server will just appear set up for you, completely automagical. When something goes wrong, you just destroy the server, and maybe send apologetic cards to the families of the etherial woodland creatures. This will greatly improve our scalability.
However we have no idea how this will happen yet. Watch here for details as this is researched.
Fabric?
(Old stuff from Jurisdiction Management)
On live
Perhaps in a future time, the follow will replace the above steps:
$ fab staging deploy
On staging
Perhaps in a future time, the following can replace the above steps:
$ fab production deploy $ fab idot imgsplat '''XXX It'd be nice to have this maintained in a fab file so we don't need extended instructions; maybe we need a repo of "deployment tools" that contain these scripts? Feels a bit like a inappropriate mixing of concerns'''
