staging

I work for a company that does sites for the pharma industry and we often need to get legal approval before we push any changes live. So, I'd like to migrate a lot of our work to a CMS environment, specifically wordpress but we need the ability to have a staging environment. Is it possible to instead of publishing a page have it publish to a staging environment that someone can browse as with a link as a site. So basically have 2 sites, one staging one live? Generally speaking the above "answers" are correct, there are alternatives to wordpress that have better built-in support for staging

I thought I'd do a simple yet potentially very useful thing, and create another symlink called live, that points to an arbitrary release, and leave current at the head where it usually is: 20120519235508 20120521004833 20120521024312 <-- live 20120521025150 20120521030449 <-- current I then configured www.mysite.com to hit live/public and stage.mysite.com to hit current/public Unfortunately both hosts seem to run the same app, and not 2 different apps. I've confirmed the httpd.conf has the correct settings and restarted it. However no change, they're both still running the same app, the app

I recently launched a service, meaning I can no longer work directly on the site, or I do so at a risk. I haven't been able to find any "standard" or "best" way to make a development server. The two things I have seen are a) Using a GIT or SVN to host the data (this doesn't quite solve my problem, I need to be able to develop somewhere, preferably not my home computer) b) Capistrano (for Rails, is there something for PHP?) The current solution I'm looking at is putting a complete copy of the server on "development.domain.com", which would then allow me to work on everything, and I can simply

To use git effectively (and as intended) I make small atomic commits, while I do have longer sessions where I do change not only one thing. Thus, I make heavy use of git add -p . This doesn't work for completely new files, though, because I tend to forget them later on. What I want to do is, tell git that there is a new file, I want it to track, but not stage it : Example: Running git status produces: # On branch my-current-branch # Your branch is ahead of 'origin/my-current-branch' by 2 commits. # # Changes to be committed: # <<STAGED SECTION>> // A # # Changes not staged for commit: # (use

So I'm new to ROR and Heroku and need a little help. I've created an app and have deployed it; however, I'd like to clear out the database associated with it. Meaning I'd like to clear any users (and their attached data) that have been created thus far. I've basically created several phony accounts to test out whether the database on the production site works, but now i'd like to clear this out, and start with a fresh database. Is this possible without deleting the database entirely? Any help would be sincerely appreciated. Thank you very much for your time! You can use heroku pg:reset

Currently my website (production server) already have a lot of code in it. And now I want to start using Git for my projects and setup a staging server for my team. Can anybody give me any advise? Here is the picture in my mind: Production - Production server which already have codes ↑ Staging - New staging server, will install Trac too ↗↙ ↖↘ Developer1 Developer2 - Local development My question is, how should I start? Here are some steps in my mind: do a git init in production server (is this safe?) clone the repo from production to staging server developers clone the repo from the staging to