Search the Community
Showing results for tags 'production'.
Summary: If I have a site sitting on a server called testing.com, then on the server change it to mycompany.com, do I have to modify any settings in ProcessWire? After building several processwire for clients, the one question that I haven't had is about moving a processwire site from an old (temporary) domain to a new domain. For instance, I typically setup development sites for clients and register a temporary domain (and lock with a password). For instance, thee client can go test.com and get all their content finalized, change wording, add news, swap out photos -- everything to make the site production read. Next, on my hosting account I can have testing.com renamed to theircompany.com - and change the nameservers. A simple question here. If I have a hosting company rename the account from testing.com to theircompany.com, change my nameservers whereas going to theircompany.com loads the production site, Is there anything I need to change in the processwire configuration or in the PW database? In the past, I've just manually copied the site, and fresh-installed PW, and imported the data. Seems like a lot of hassle. I have a second part question about updating the PW core, however, after consideration I'll post it as a new topic.
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 everybody, So it turns out PW works on IIS pretty well. Had very little issues in getting it to run and not many issues in getting it setup.... in a localhost environment. I've been given a Windows Hyper-V server for the uses of my intranet that I've been building with PW. The only problem is now, I seem to be having issues whenever trying to log in. It doesn't recognize the admin user I created during installation, it simply redirects back to the /login/ page, with no error message. Debugging shows the following message on the frontend login screen (not the backend). Localhost does not show this When moving the dev machine to production, here are the steps I followed: Copied wwwroot from development machine to the production server Exported by site's database using SQL Front and importing on the production server Allowed access on the production server Edited site/config and wire/config to add in the hosts - appname.domainname.co.nz, localhost, 188.8.131.52 Now this is the real kicker: I can goto http://localhost on the production machine, and get full access and it works fine... However when I try using appname.domainname.co.nz, I keep getting this weird "blank" redirect. I would really appreciate any help anyone would be able to give me. I have looked all thru the PW forums for something similar around this to no avail.
Hey Everybody, As I was trying to move an exsisting site form my local dev (xampp) to a production server, the following error appeared: Error: session_start(): Failed to initialize storage module: user (path: /usr/local/www/services/.../data/tmp) (line 103 of /home/.../html/wire/core/Session.php) This error message was shown because /install.php still exists. Error has been logged. I searched the forum for help, but the only related topic I could find is this one: Problems with ProcessWire on Cloud Hosting https://processwire.com/talk/topic/5089-problems-with-processwire-on-cloud-hosting/ The thread says, that it might have something to do with some isses in the master branch of pw. So I downloaded the dev branch (2.4), and made a fresh install. There are no problems with the requirements, nor with mod_rewrite. In the last installation step, after the admin user creation the error message from above appears again. Is it usual, that pw creates a tmp/data diretory? I changed the file permissions for the assets and changed the htaccess, but still there is no change. Thanks for any hints on that. And thnaks for that lovely CMS