Recently Browsing 0 members
- No registered users viewing this page.
Here are the step by step to install and setup ProcessWire with the help of a server management tool - https://cloudstick.io/
1. Create your Vultr compute.
2. Select the Operating system Ubuntu 16.04/18.04/20.04 LTS >> Enter your server root password then click on Deploy now!
3. Create an account in CloudStick and connect your server:
Click on connect server >> Enter your server login details >> Add this server.
4. Your server setup will be done in couple of minutes - The setup will finish less than 8 minutes. Then select your server:
5. Create an account to host/upload ProcessWire: Click on Accounts >> Create an account >> Create Custom Web application:
6. Enter the web application details, such as the email address which you would like to receive the SFTP login details >> web application name >> Domain name >> username then >> select the web application stack >> nginx + apache >> then create web application.
7. Now select the web application then install SSL:
8. Open your email account, and find the login details to connect the server over SFTP >> then upload the source code of ProcessWire:
9. Let us open the domain in browser once the upload finish.
10. Select the profile and click next:
11. Click next to proceed further: Now, you will see an incompatibility issue with PDO-Mysql which can be install in 2 clicks.
12. Go back to the summary page >> Click on easy PHP >> Select the PHP version of your web account:
13. Then it is time to enable PDO_Mysql, scroll down and enable it:
14. Go back to to the ProcessWire installation URL and click on check again >> You can see no incompatibility issue after enabling PDO_Mysql:
15. Click on Next and now it is time to enter the database credentials:
16. let us create the database, db user and grant privilege's to the db user - it is just matter of few clicks and very easy!
Click on the menu Accounts >> Select your web account of ProcessWire >> Click on App Database then create the a database:
17: Click on create database and enter the database name:
18. Create the database user:
19: Go back to the database page and click on Grant user then grant permission:
20. Go back to the ProcessWire installation URL and enter the database credentials you have created in CloudStick dashboard.
Now, it is time to setup your admin user credentials and setup admin area URL:
21. Then you are done:
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 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?
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?
So we have been working with ProcessWire for sometime now. We absolutely love ProcessWire so much that we have changed our site from a custom build on a custom CMS to WordPress and now ProcessWire and will never go back to anything else. We launched a small version of our site to test the migration from WordPress a couple months ago and now have finalized a new look and feel. We are a small team based out of the Chicagoland area that is eager to grow.
Our go to CMS is ProcessWire for our clients.
Please take a peak at:
We are currently running the latest version of ProcessWire with Template Editor Module.
We are looking to start building some of our own modules in the near future.
Ryan Cramer, thank you for such an incredible CMS. ProcessWire community, thank you for such an amazing group of fellow developers, designers and SEOS. You guys are all great and have helped us grow so much with answers to API questions, suggestions and advice.