Comments on: Stage http://daryl.learnhouston.com/2008/07/01/stage/ Thu, 08 Jan 2009 11:16:49 +0000 http://wordpress.org/?v=2.7 hourly 1 By: daryl http://daryl.learnhouston.com/2008/07/01/stage/comment-page-1/#comment-1947 daryl Fri, 11 Jul 2008 00:19:56 +0000 http://daryl.learnhouston.com/?p=397#comment-1947 As yet, the only documentation is in the module itself. You don't have to have separate servers to stage on, but if you're staging site assets (templates, etc.), you probably already have a separate hostname and virtual host, at least. In testing, I used the same virtual host with a serveralias for my staged name, so it can be done without even using a separate virtual host. All this module does is to tap into drupal's existing revision system and let you deploy change sets (or batches) of revisions. The dev vs. production dichotomy is for now purely a naming convention, so that the site knows whether to display staged content or production content (and so that you can be redirected to the production hostname for edits). The module is very solidly ready for testing but has not been deployed in production yet and may not be ready for such a deployment yet. I hope you'll set it up on a test site and let me know of any issues you run into, though, as I'm trying to make this production ready. I'm also working on a module that'll let you stage non-node content (panels, blocks, etc.), incidentally, but it's even less ready for prime time than this one. As yet, the only documentation is in the module itself. You don’t have to have separate servers to stage on, but if you’re staging site assets (templates, etc.), you probably already have a separate hostname and virtual host, at least. In testing, I used the same virtual host with a serveralias for my staged name, so it can be done without even using a separate virtual host. All this module does is to tap into drupal’s existing revision system and let you deploy change sets (or batches) of revisions. The dev vs. production dichotomy is for now purely a naming convention, so that the site knows whether to display staged content or production content (and so that you can be redirected to the production hostname for edits). The module is very solidly ready for testing but has not been deployed in production yet and may not be ready for such a deployment yet. I hope you’ll set it up on a test site and let me know of any issues you run into, though, as I’m trying to make this production ready.

I’m also working on a module that’ll let you stage non-node content (panels, blocks, etc.), incidentally, but it’s even less ready for prime time than this one.

]]> By: westwesterson http://daryl.learnhouston.com/2008/07/01/stage/comment-page-1/#comment-1946 westwesterson Fri, 11 Jul 2008 00:02:17 +0000 http://daryl.learnhouston.com/?p=397#comment-1946 was wondering if there is any documentation on how to use this? I know you just hacked it together and i was wondering how it works. Do you need separate servers to stage content on? Is this module some kind of bridge between them? how do production hosts and development hosts connect with each other? is this non functional for now? I am looking for some kind of staging system, I am also looking at the revision moderation module, but I would rather be able to push a wide array of edits at the same time. thanks! was wondering if there is any documentation on how to use this?

I know you just hacked it together and i was wondering how it works.
Do you need separate servers to stage content on?
Is this module some kind of bridge between them?

how do production hosts and development hosts connect with each other?

is this non functional for now?

I am looking for some kind of staging system, I am also looking at the revision moderation module, but I would rather be able to push a wide array of edits at the same time.

thanks!

]]>