Search the Community
Showing results for tags 'staging'.
Found 2 results
I am running development server where I test and try the changes in fields and templates of ProcessWire. The php files are stored in git@bitbucket. The part of managing changes and versions of php code itself via git is quite straightforward, as I presume we all know. However, I have not been able to come up with decent way of moving the changes in fields, templates, modules and settings from development to production other than repeating them, step-by-step, manually in production environment via the admin back-end. Perhaps there is more sophisticated way of transferring these changes?
Hi Guys, 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: domain.com/test/whatever-the-link-is/ or domain.com/test/assets/file.pdf or domain.com/test/assets/image.jpg The issue is, when I move to a live site, I have to go back and change tons of links from: domain.com/test/whatever-the-link-is/ to domain.com/whatever-the-link-is/ 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.