Hi,
Just wondering if anyone has techniques they can share or a list of procedures for moving stageing website to production, just what files need to be copied from the stageing to the production?
Also, is it possible to install the stageing into another subdomain or directory and then easily move it production just by retargeting the root directory in config?
------------
Geoff
Techniques for Moving Stageing WS to Production
-
Woudloper
Re: Techniques for Moving Stageing WS to Production
As far as I know 'CMS Made Simple' is not working with a 'staging' and a 'production' environment. Both sites are the same and you can't switch instantly between 2 different sites.
Afaik. To make this available for 'CMS Made Simple' I think the whole logic and core development should be changed. 'CMS Made Simple' is more using dynamic websites and querying the database when it needs to have data...
Afaik. To make this available for 'CMS Made Simple' I think the whole logic and core development should be changed. 'CMS Made Simple' is more using dynamic websites and querying the database when it needs to have data...
-
Ashocka
Re: Techniques for Moving Stageing WS to Production
I can understand that in a product like this, especially when it's name is "CMS Made Simple",maybe has no users requesting a need to address such features. Still at first glance, this looks like a really nice Simple CMS for simple sites. But I need to redevelop a site, and I am sure that this type of need will come up with users in the future, even if they have to do a DB export and import with some basic modifications to the data and the config files. That also needs techniques for import and export.
It amazes me how many so called CMS's lock you into working on only a production site. Surely there is some need to address these issues in design.... but maybe not... maybe no one here has such requirements (which would leave me a little surprised).
There are basically three types of situations where there is a need for seperation between stageing and development;
1) The situation I have just outlined, where there is an old site running ACME CMS
2) Current site is using the same CMS as New Site in Development, but there needs to be a separation for presentation, but sharing of data
3) The need to manage workflow, where there are various levels of authoring and moderation
Maybe CMSMS finds no need to address any of these issues (except the last).
------------
Geoff
It amazes me how many so called CMS's lock you into working on only a production site. Surely there is some need to address these issues in design.... but maybe not... maybe no one here has such requirements (which would leave me a little surprised).
There are basically three types of situations where there is a need for seperation between stageing and development;
1) The situation I have just outlined, where there is an old site running ACME CMS
2) Current site is using the same CMS as New Site in Development, but there needs to be a separation for presentation, but sharing of data
3) The need to manage workflow, where there are various levels of authoring and moderation
Maybe CMSMS finds no need to address any of these issues (except the last).
------------
Geoff
Re: Techniques for Moving Stageing WS to Production
Yeah, I agree that this should be addressed someday. However, at the present scope of CMSMS, it's a little out of scope (does that make any sense?)
Basically, in order to move the site from staging to production now, do the following:
1. Back up your mysql database to a sql script (mysqldump)
2. Copy all files from staging server to prod server
3. Restore mysql backup (mysql < backup.sql)
4. Modify paths in config.php, change database details, etc
5. Clear cache (via Global Prefs -- you should be able to hit the admin after step 4)
People have done this many times and from what I hear, it's pretty snag-free.
Maybe someday someone can write a module to take all the content form a staging environment and move it to production? Would be kind of interesting...
Hope that helps!
Basically, in order to move the site from staging to production now, do the following:
1. Back up your mysql database to a sql script (mysqldump)
2. Copy all files from staging server to prod server
3. Restore mysql backup (mysql < backup.sql)
4. Modify paths in config.php, change database details, etc
5. Clear cache (via Global Prefs -- you should be able to hit the admin after step 4)
People have done this many times and from what I hear, it's pretty snag-free.
Maybe someday someone can write a module to take all the content form a staging environment and move it to production? Would be kind of interesting...
Hope that helps!
-
Ashocka
Re: Techniques for Moving Stageing WS to Production
Yes, thanks that's helpful. Yes, the normal procedure I'd expect, but it's reassuring to know that others use this method without problems.
There's probably no need to address the issue of Stageing/Production at this stage, as most likely everyone is pretty happy with CMSMS as it is. What I like (from building just one test web site), is that, not only is it pretty straight forward for a web standards based developer, and easily allows one's own templates, but it does have a nice clean UI for clients to manage content. This is a big plus.
I guess you just need to keep such issues in mind as you are developing the software architecture, so that you can integrate such features if a lot of users start asking for them.
There's probably no need to address the issue of Stageing/Production at this stage, as most likely everyone is pretty happy with CMSMS as it is. What I like (from building just one test web site), is that, not only is it pretty straight forward for a web standards based developer, and easily allows one's own templates, but it does have a nice clean UI for clients to manage content. This is a big plus.
I guess you just need to keep such issues in mind as you are developing the software architecture, so that you can integrate such features if a lot of users start asking for them.
