Deployment Tip: Maintenance Page
February 24th, 2007 — 8:47 pm —
While we don’t use capistrano we’re stealing a page from their book in how we deploy apps. Because we need to stop and start services when upgrading slate we have a “down for maintenance” page we put up before working on anything. This way users aren’t just left hanging when slate goes away. One of the interesting problems with slate though is the fact that users using our sites have no idea that they’re using slate. Hopefully we’ve been able to explain what’s going on properly.
So how to do this?
1. Put the following in your Apache config:
# Check for maintenance file. Let apache load it if it exists
RewriteCond %{DOCUMENT_ROOT}/system/maintenance.html -f
RewriteRule . /system/maintenance.html [L]
2. Make sure that you put a stand-by file in %{DOCUMENT_ROOT}/system/ called maintenance1.html or something
3. Before you perform maintenance rename maintenance1.html to maintenance.html
We have step 3 automated and I’m sure you’ll want to do something similar. Cap will take care of that for you as well.
About slate
slate is a content management system (CMS) developed using Ruby on Rails focused on rapid production of traditional websites created by WVU Web Services. Read more about why we created slate and a longer list of features of slate. You can also check out a list of sites using slate. If you have questions or comments let us know but if it's a question about open sourcing slate have a look at this article first.Archives
Recent articles
- No Wonder Rails Is Default in Mac OS X Server...
- Good News: An Open Sourced slate Is Coming
- The WVU Open Source License
- Implementation idea: .do templates
- Keeping slate Humming - Part 1
- Campfire for Design & Keeping Your Tag Cloud Running
- Custom configuration settings made easy
- HOW-TO: Add a Gallery to Your Site
- JSONRequest.post Example
- Miscellaneous
Articles
Add comment
You are adding a new comment