Dreadnot is a 'one click' deploy tool written in Node.js.
Dreadnot was heavily inspired by Etsy's Deployinator.
exportsconfig =// The name of this Dreadnot instance, used for displayname: 'Example Dreadnot'// Each Dreadnot instance supports one environment such as 'dev', 'staging'// or 'production'env: 'staging'// The data root Dreadnot will usedata_root: '/var/dreadnot'// Base URL to access dreadnot (used in IRC, email, Hipchat)default_url: ''// Dreadnot uses an htpasswd file (with support for bcrypt, md5 and sha1) for authhtpasswd_file: '/etc/dreadnot/htpasswd'// Each stack represents a code base that should be deployed to one or more regionsstacks:// For a stack named 'webapp', there should be a 'webapp.js' file in the// stacks directorywebapp:// What branch to look in for the latest revision of the code basetip: 'master'// How long to cache the latest revision of the code basetip_ttl: 120 * 1000// What regions this stack should be deployed toregions: 'ord1'// Stacks should implement dryrun for testingdryrun: true// The GitHub organization you provide is used to build URLs for your stacksgithub:organization: 'racker'// Plugins provide optional functionality such as notifications. Any plugins// that are not configured won't be used.plugins:// An IRC notification pluginirc:nick: 'staging-dreadnot'channels: 'irc.freenode.net': '#public-channel' '#private-channel pass'// An email notification pluginemail:server:user: 'firstname.lastname@example.org'password: ''host: 'smtp.example.com'ssl: trueto: 'email@example.com'from: 'firstname.lastname@example.org'// A Hipchat notification pluginhipchat:name: 'Dreadnot'apiKey: '123456789abcdefg'rooms:12345678;
Dreadnot looks in a directory (by default
./stacks, but this can be changed
file that exports
get_deployedRevisionfunction which takes an object containing
regionfields, and a callback taking
targetshash that maps target names to lists of task names. Currently, the only supported targets are
deploy, which defaults to
['task_preDeploy', 'task_deploy', 'task_postDeploy'], and
finallywhich does not have a default value. You should use the
finallytarget if there are any tasks you would like to run every time, regardless of the success or failure of the tasks in
deploy(i.e. re-enable monitoring alerts). The tasks in the
finallytarget itself are each dependent on the success of the last task in the target, so an error in one will prevent the rest from running.
task_. Each task function takes:
stackConfigwhich contains the config for this particular stack, and
configwhich contains the global config.
logfield with methods such as
errorthat can be used to log output to deployment log and web view.
user, each of which is a string.
In the configuration used by Rackspace Cloud Monitoring, a deployment looks something like:
Imporantly, Dreadnot knows nothing about the hosts to which it is deploying - if it did, we would have to modify our Dreadnot configuration every time we added or removed a machine from our environment. Instead, we rely on chef (although anything that knows about your servers will work) to give us an up-to-date list of all hosts in a given region. In smaller deployments it might be suitable to hardcode a list of hosts.
Does Dreadnot support SVN?
Dreadnot supports Node.js - you can use any technology or topology that suits you, as long as you can find a library for it.
Then visit http://localhost:8000
Log into the VM by running and running common commands:
vagrant sshsudo cat /var/log/upstart/dreadnot.log
npm install dreadnot -g
Alternatively, when developing, you can find a compiled dreadnot binary in the bin folder.
Dreadnot takes a number of options on the command line. The defaults are:
dreadnot -c ./local_settings.js -s ./stacks -p 8000
This will start dreadnot with the specified config file and stack directories, listening on port 8000.