laplix

@kongondo, @horst, @BitPoet, Thank you for welcoming me.

OK, I tried soma installer and it work quite nicely, except
 everything is the name of the apache user www-data, meaning I have to change the owner of the site/ directory and if I want to tinker with ProcessWire, I'll have to do that for the whole installation I got ProcessWire 2.7.2 instead of 3.0.15 I do want the 3.0.x branch, and I want to stay up to date with the branch. This why I used git. I'm ready to live with some bugs. This is mostly a learning project though some of it may go out later when the 3.0 branch goes beta or stable.

@horst, this is why, at first, I would copy site-default to site and chmod 777 access config.php and modules before starting installation. But on @BitPoet suggestion, I didn't do any of that before starting another installation. I did correct everything after these errors showed up.

Checking in install.php, I see in initProfile.php that it does try to rename the profile I chose. But since I clone the repository, the files belong to me, not to the apache user. So the installer is unable to create the site.

It will work with grabpw.php because it is the installer that creates the files. So they belong to the apache user.

Anyway, I finally manage to install my project with 3.0.15. Now, the fun part starts

Yet, I would like to know why this error occurred. Maybe later, when I am familiar with the code, I'll hunt it down.

ProcessWire looks like an awesome framework, doing things in a completely different way compare to other frameworks and challenging the brain a bit. For example, I started designing my project, making the database schema and stopped right there realizing that PW is mostly about pages, templates and fields. No need for a full database design.

Anyway, I want to thank you all for taking the time to answer me. This looks like a very, very friendly community.