Recently Browsing 0 members
- No registered users viewing this page.
I have been reading about Multisite, but it kinda bugs me that every topic talks about having both admin and database same for multiple sites.
I have a project where customer tests it by adding content to the site, while I still need to do some changes here and there in code, maybe some in database. If something crashes for a while, customer can't keep testing, which is a bit problematic.
Is there any way that I could have two separate versions of one site ("production" and development) that share the same database, but are otherwise independent? Just the thought of having to migrate database every time I want to show client something new gives me anxiety 😁
I wanted to post this thread to get some insight as to how others are migrating from a staging directory inside a live server to the actual root directory.
I typically develop a project locally using Mamp and then move into a staging environment on a staging server . There are some cases the project requires to move the site into a directory inside a live site to make deployment of the new project move faster.
When I move a project into a directory on the live server of domain.com/test/ I run into an issue of content links.
What I mean is that I look at the source code in the CKEDITOR for a field and the link will display:
The issue is, when I move to a live site, I have to go back and change tons of links from:
How are you guys making the link changes across the entire site at once?
Are you using SQL Commands? Something in ProcessWire? Any suggestions will help eliminate the manual process.
I am redesigning my site and set up a development version of the site (plain copy) using the same database.
During the redesign process I became interested in the CroppableImage module, which requires the dev version of PW.
I upgraded the files in my development sites, but want to check with you before I start installing the new modules in the test version:
Can this cause problems with the production site as long as it isn't using any of the new fields/modules?