jose

No doubt of that, the only way to learn it is to use it, your on your way.

Thanks for your quick reply. I hear you about being busy I don't remember summer being so busy. Anyways I will test out the utility and give you feedback. Please don't hesitate to ask for help from your community members, so we can pitch in. I'm pretty well versed in git and mercurial and dvcs. If you would like I could help you re-integrate the projects under one repository(a test private repo to make sure its all good). Anyways help is here when you have time.

Hello everyone, I was wondering how divergent the two repositories for processwire are. The reason being is that we use version control on all projects including processwire. To explain a little of the workflow. 1) We have our own fork of processwire which I pull the latest/safe changes from upstream/master(your repo). 2) When we create a project I clone our processwire repo for the new project and then I create another repo for this client project. 3) If we make custom changes to processwire we make them to our own repo, and we can also push/pull request from our processwire repo to send changes back to upstream. When updates are made to processwire in upstream we pull to our repo then to our client projects. That's basically how we keep everything tracked. I want to move to version 2.1 of processwire, will adding the new repo to git config file and pulling changes from that repo allow me to update the main stable repo code. Reason for this is that I want everything tracked and easy to manage, that is what version control systems are for, and also maintain a history between versions. I also know there are database changes due to new user mechanism, is there a document explaining the upgrade to the database(IIRC you said you had been working on one)? Another question is why you chose another repository instead of a branch? Anyways thank you for your help and lets me know what you think. Thank you for your time. -Jose Raffucci

Fantastic! I think perhaps I will move these sites now before I finish development. Thank you for your time.

I was wondering if there would be a documented upgrade path when the development version is declared stable. The reason for the question is I am developing a few sites now for customers that I will be maintaining and supporting, we chose ProcessWire and I just want to know how hard will it be to upgrade/migrate to new version. Thanks for your time in advance.

Ryan, I think that you will like nginx a whole lot. It is light weight, easy to use, asynchronous, over all a great piece of software. That's not to knock apache at all since we still use apache and it is rock solid. If you want to play with it quickly I recommend a virtual machine, either hosted like on cloudserver by rackspace(just started using this service and so far I am happy with it) or fire up virtual box or vmware and install debian linux(squeeze). With a basic install add the dotdeb repositories and install these packages apt-get install nginx php5-mysql php5-fpm php5-gd postfix mysql-server Install postfix as an internet site/with direct delivery and keep all defaults. Once everything is installed you can edit and create the configuration files /etc/nginx/sites-available and sites-enabled directories. A simple start of nginx server /etc/init.d/nginx start and your off and running. There is a lot of great documentation out there this is just meant to peak your appetite for nginx. As far as the install is concerned, the are 2 areas: 1) .htaccess file is not supported under nginx the fact that its not there should not fire off an error (perhaps a warning) if we are not under apache. 2) rewrite module detection, again not needed for nginx, perhaps a warning instead of an error. I am sure we can detect nginx with the simple $_SERVER['SERVER_SOFTWARE'] global. Other then that ProcessWire seems to install and work perfectly under nginx. I will be updating the rewrite rules for nginx to exclude the core folder from direct access when I get closer to deployment of 3 projects we are building with ProcessWire. I would tend to agree that a more formal documentation would be better then relying on a forum, you never know what can happen to a forum. I would be glad to help write formal configuration documentation as well as help write the detection code in the installer. I am excited to see this project moving forward so well and hope to be a consistent contributer and community member. Thanks again for all your efforts.

Hello Everyone, Sorry that I have not been on the forums much of late. As my development team moves to use ProcessWire as our main cms tool for clients. We have needed to make sure that ProcessWire works on nginx platform. We use both apache and nginx, we found as many already have that nginx is faster and easier to configure. It scales well and when you really need speed it is a great solution. Anyways with all that being said ProcessWire was surprisingly easy to configure for nginx and did not require adding or modifying any code. Using the same "try_files" directives used for Wordpress and Dupral I was able to run it under nginx, here is a sample config: upstream php { server unix:/tmp/php-cgi.socket; server 127.0.0.1:9000; } server { listen 80; server_name hostname; root /websites/path/to/processwire; index index.php; try_files $uri $uri/ /index.php?it=$uri&$args; location ~ \.php$ { fastcgi_split_path_info ^(.+\.php)(/.+)$; include fastcgi.conf; fastcgi_intercept_errors on; fastcgi_pass php; } } There are a few things that still need to be done like protecting the wire and certain directories like assets but so far everything looks to be working correctly. If ProcessWire has a test suite, I could run it against this server to see if everything is functioning properly. I think that advertising the fact that ProcessWire works under nginx would greatly help to attract more eyes to the project(not that it isn't doing great already) and to give options to hosting and scalability. If you would like help working on this for official support of the platform, perhaps with adding detection algorithms to the install or anything else that is needed, I would be glad to help. Anyways I hope someone finds this post useful.

Fixed: The directories sessions, logs, files, cache where not being created. I created them and applied writable permissions to the folders and I can now log into the admin. A little history on my configuration. I provide hosting for my clients with a collocated server. So I have many sites with different permissions. I am also keeping this site under revisions control so I can quickly merge upstream(master repo for processwire) changes as processwire gets updated. I think that a group flag may have been set for the folder and creating folders was limited to that user. Once I created the folders and gave write permissions everything seems to be working. Hope this helps anyone in a similar setup

Strange I tested the install localy and everything worked fine. I guess it must be a configuration problem on my server. Still not sure what it could be though as the setups are almost identical. *** Update *** I still can't seem to login, like I said I can access the admin(used to be /processwire/ now /admin/) page just fine. But login takes me back to home page. Will try and see what I messed up. *** Update 2 *** When I type the incorrect login it fails with a message so post is working. When I login correctly I am taken to the home page, very strange. I made sure my .htaccess file is correct by replacing it with default. I am not sure where to go from here. Any help would be greatly appreciated. *** Update 3 *** Seems that the sessions folder under assets is not being created, even though permissions are fully open on that folder 777 I will try to see if changing ownership of assets folder will make any difference. Seems like not creating sessions would be the issue. Will keep you updated.

I created a custom install for a new website. I changed the pageurl for the admin from "processwire" to "admin" as this is easier for clients to remember. This was part of the install.sql that was added to the profile. Everything worked great(install, main home page) except when I try to login to the admin. The admin page shows up just fine but when I try to login it takes me back to the home page. I looked at the html source that is being generated and the post address is "./". I am not sure what I did to mess this up but I would be glad to send you the site profile I created. Please let me know if there something in the database that I should look at etc.. Thank you in advance for your help.

Wow thanks for such a thorough reply. This is very helpful.

I have been looking over the site-default profile learning how to build a custom profile. I must confess that it is very straight forward. I just wanted to make sure that I understood the database creation portion. During installation site-default is renamed to site, the database is configured and then the site/install/install.sql is run. After looking it over it seems that it also creates all the tables used by ProcessWire. This has led me to believe that the best way to build your custom profile is to install the default-profile, overwrite the default templates with your own. Remove the extra pages from the admin, apply the correct templates to the home page and any other pages you want to leave. Change fields and templates settings, etc... Delete the images that you don't need from assets. Once you have your basic site working you dump the database into a install.sql file and replace the install.sql that came with the default site profile. You now have a portable site profile to install anywhere you need(after removing installed.php from assets). Is this how ProcessWire plans on doing installs in the future or will ProcessWire change to install the tables cleanly in the future(from the core wire folder) and take the user to the admin to start adding pages? I am just interested in building something future proof. BTW thanks for making ProcessWire Open Source and sharing with the community.

Just pulled and tested the changes. Everything is working as it should. Ryan, thanks for getting to this so quickly. Will take a look at the IE modal problem and see if I can't come up with a solution. Thanks again.

Yup I think I was originally correct in my first diagnosis. Maybe I did something different when I tested it again. I will pull the changes and let you know. Thanks for staying on top of this!

Wait, I think it may have been an issue with the cache. I cleared out both browsers and it seems to be working fine. I am sorry for the inconvenience. Please disregard my previous message.