staging

I want to set up a staging environment on Google App Engine and have found good guidance for this in the following question: How to set up a staging environment on Google App Engine The only unanswered question I have is how to handle Cron jobs in this case. Ideally I'll just have to change the version to deploy to production, however I fear that that would mean that all cron jobs also run on the staging version, or is this not the case? If you're using a different version approach you need to pay attention to this : If the target parameter has been set for a job, the request is sent to the

I have a production server running an app that uses CouchDB as its main database. I'd like to set up a staging server that has a CouchDB instance that I can always sync back up to the production instance and get a clean copy. A naive solution would be simply to have the staging server continuously replicate the production server's database, and just use that. The problem of course is that in the course of testing on the staging server, I may do things that modify the database. Functionally correct would be for me to delete the database every time and re-replicate from production; but obviously

What do I change to switch from production to staging.. etc.. and where.. Bootstrap ? Also, Curious if anyone has configured their Zend Framework to automatically switch from production, staging, test.. etc based on Host information.. example.. if (hostname = 'prodServer') ... blah if (hostname = 'testServer') ... blah I'm new to Zend but I typically configure my projects to automatically switch run environments based on the host information. thanks Assuming that you are using APPLICATION_ENV as part of Zend_Application, then you could add this in either your .htaccess or main Apache config

Suppose that there are 3 databases for Production Staging Dev As far as I know, Staging database need to be in sync with Production database But, When we are developing, we can do whatever we want with Dev database and change schema. Now here comes the Chicken & Egg problem. To test in Staging, Staging database schema need to be changed according to changes made in Dev database. But the Staging database need to be in sync with Production. How do you guys get around this problem? Staging needs to be in sync with production, only up to the point where you are deploying new changes. That or make

I currently have two environments in which I work: development locally and production on Heroku. I would like to add a staging environment on Heroku to see that everything goes as expected before pushing the app live to users. Preferably, the staging environment should have the exact same settings and data as the production environment. What are the steps needed to accomplish the above? berislavbabic First the predispositions, i like to have my heroku git remotes set up as staging and production so you can easily use git push staging/production to deploy to each one of them. I'll be using that

When you modify a file in your working directory, git tells you to use "git add" to stage. When you add a new file to your working directory, git tells you to use "git add" to start tracking. I am a bit confused about these 2 concepts because i assumed tracking a file for changes is different from staging it for commit Git has a concept known as 'the index'. To create a new commit, you fill the index with the contents you'd like to have in the next commit. That means that you have to explicitly tell Git which changes you want to appear in the next commit by using git add . ( git add -p to add

I ran "git status" and listed below are some files that were modified/or under the heading "changes not staged for commit". It also listed some untracked files that I want to ignore (I have a ".gitignore" file in these directories). I want to put the modified files in staging so I can commit them. When I ran "git add .", it added the modified files AND the files I want to ignore to staging. How do I add only the modified files and ignore the untracked files if presented with the git status below. Also, are my ".gitignore" files working properly? $ git status # On branch addLocation # Changes