rax-maas / dreadnot

deploy without dread
Apache License 2.0
631 stars 61 forks source link

Documentation for dreadnot #15

Open prangana opened 12 years ago

prangana commented 12 years ago

Hi I need some help in using the open source tool "dreadnot". I downloaded the tool . My goal is to use dreadnot for automatic deployment of software, configuration, test. If that's possible with dreadnot - I need to know the steps to set up the same . Where do I click to see the documentation for the tool? ( User manual, Installation guide etc )

Thanks PR

dispalt commented 12 years ago

Right now the project is pretty young. But most of the documentation is in the README and example deployments. We are working on expanding those examples in the future.

prangana commented 12 years ago

Thank you - I will go through the README and get back if there are difficulties

Date: Thu, 12 Jan 2012 06:57:14 -0800 From: reply@reply.github.com To: rmini69@hotmail.com Subject: Re: [dreadnot] Documentation for dreadnot (#15)

Right now the project is pretty young. But most of the documentation is in the README and example deployments. We are working on expanding those examples in the future.


Reply to this email directly or view it on GitHub: https://github.com/racker/dreadnot/issues/15#issuecomment-3464376

twojcik commented 12 years ago

Hi,

It would be great to see more complex example of deployment, for example to rackspace cloud or aws and with at least few target servers.

Cheers, Tadek

sandfox commented 12 years ago

@twojcik +1 for the more complex examples. It might be an idea to see if any non-RS examples could be found too (variety is the spice of life). At the moment I think there is a bit of gulf between what dreadnot was designed for, and what the examples gets you started doing, and the potential for going wildly off track is huge (or just throwing your toys out of the pram).

prangana commented 12 years ago

I 'm struggling how to use dreadnot in my product for deployment of builds on a daily basis after the builds are done . I'm not considering deployment in cloud currently. The script that i'm using currently needs heavy maintanence and it is very fragile Thought dreadnot would be a good alternative - but I have not even taken the first baby step - I dont know how to configure it. Can some of the experts help here ? thanks PR

Date: Wed, 8 Feb 2012 01:53:55 -0800 From: reply@reply.github.com To: rmini69@hotmail.com Subject: Re: [dreadnot] Documentation for dreadnot (#15)

@twojcik +1 for the more complex examples. It might be an idea to see if any non-RS examples could be found too (variety is the spice of life). At the moment I think there is a bit of gulf between what dreadnot was designed for, and what the examples gets you started doing, and the potential for going wildly off track is huge (or just throwing your toys out of the pram).


Reply to this email directly or view it on GitHub: https://github.com/racker/dreadnot/issues/15#issuecomment-3865117

tritonrc commented 12 years ago

Here is the stack we use: https://gist.github.com/1791382 Our asset build currently depends on some information seeded into the database which is why the db:drop et al are in there.

russellhaering commented 12 years ago

@prangana I'll put in some work on docs as soon as I get the chance, I've heard from quite a few people who are interested in Dreadnot, but not sure how to use it. In the meantime, check out the gist posted above. The general idea is to create a node.js file full of 'tasks', then create lists of tasks that make up a deployment.

@tritonrc When I get around to documenting this, do you mind if I include a Heroku example based on yours?

prangana commented 12 years ago

sure. If I can get it to work the way I want using dreadnot , I will share my experience. Looking forward to the starter kit . Thanks for reaching out.

Date: Fri, 10 Feb 2012 10:36:17 -0800 From: reply@reply.github.com To: rmini69@hotmail.com Subject: Re: [dreadnot] Documentation for dreadnot (#15)

@prangana I'll put in some work on docs as soon as I get the chance, I've heard from quite a few people who are interested in Dreadnot, but not sure how to use it. In the meantime, check out the gist posted above. The general idea is to create a node.js file full of 'tasks', then create lists of tasks that make up a deployment.

@tritonrc When I get around to documenting this, do you mind if I include a Heroku example based on yours?


Reply to this email directly or view it on GitHub: https://github.com/racker/dreadnot/issues/15#issuecomment-3911852

tritonrc commented 12 years ago

@russellhaering Yep that is fine by me.

sinopower commented 12 years ago

@russellhaering can you show a full example of dreadnot.The default example is so simple.You'd better explain the origin that includes many hosts. origin1 => ['ip1','ip2'] . How to push it to production environment. If we use svn,is there any example? Thanks....

dodwyer commented 11 years ago

any more progress on creating some fuller examples?

dwradcliffe commented 10 years ago

I know this is old, but I'd still be interested in seeing an example of a stack that does a deploy on a remote host or hosts.

ingf commented 10 years ago

+1