Recently Browsing 0 members
No registered users viewing this page.
By Kevin C. McCarthy
For some background, I'm great with WordPress and I'm great with writing websites by hand with Notepad only. The biggest hurdles I have with PW is the phrasing is so far left of WP at times that it's a massive hurdle for me to get over. Like in WP, themes, templates, etc are totally different things. And as someone who builds WP sites for a living, it gets hard to kill those old preconceived meanings.
I want to start building out PW sites for numerous reasons. For one, most of my clients they would benefit from it vs the Bloated Beast. Two, it would allow me to differentiate me in a market saturated by WP devs. I know I have a long ways to go until I reach that point of considering myself a "PW dev", but I am desperate for resources to help me wrap my head around it.
I've built my own website in PW but TBH it only handles some of the data while most of the text has been hard-coded into the PHP template files because I couldn't get my my head around the "best practice" of structuring the data.
Anyway, enough rambling, I'm just hoping those of you in the community can point me to easily-digestible sources out there that can help move me along so I can actually benefit from using the platform. Thank you!
I have a marketplace site built on PW which I'd like to tie to a subscription payment system for those selling. The user accounts currently use specific PW user accounts. I'm looking closely at PayWhirl to manage payments and subscriptions as it looks ideal for subscriptions. Their API seems to work well too from initial testing.
I wondered if anyone else in this super forum had used PayWhirl and had any advice or tips & tricks?
I'm a System Administrator responsible for DevOps in our Company. We're trying PW in a single client project atm and experience some glitches with DevOps-/Workflow.
We have a small team of developers that need to work with the same code base. They all need to be able to develop locally and deploy to a preview/staging environment.
Our Toolstack contains git for versioning, chef/vagrant or docker for local development/testing and Jenkins for building assets and automatic deployment to the staging-site.
There's several challenges / glitches in this process that makes me think that ProcessWire hadn't been developed for a use case like ours and is much more intended to be used by single developers that work right on the production system.
Can you advise me on a suitable workflow?
There's problems with the assets/files dir that must be shared between the staging website and local environments of our developers.
We're right now working with symlinks on the staging system that helps to preserve the direcory when deploying from the master branch. but now we tend to use nfs-shares so devs can collaborate with a shared directory.
The local docker containers can use the same target (the nfs) from inside the containers. But is that the way it needs to be done? Really?
There's so much work that needs to be done to fit ProcessWire in a DevOps Workflow that we tend to decide to switch to another CMS.
Any suggestions or hints that i might have missed. Am I wrong or is PW really not meant to be used this way. I
Has anyone successfully installed Processwire on an Amazon EC2 instance/virtual server?
Which configuration works; Amazon Linux or one of the other flavors?
How do you get file permissions and the database working?
Which lines in .htaccess cause problems on Amazon AWS?
What are the pitfalls to watch out for?
Why can't I get it working...?
The first problem I run into is an error message that the installer doesn't have write access and that I should manually rename the 'site-myprofile' folder to 'site'. Attempt to chmod all the files and folders to 777 don't seem to have any effect on that and some files do get written fine.
But I keep ending up with inaccessable pages and fatal server errors. I am not asking you to solve my problem. I am curious what other people's experiences are with this. Can it be done or am I wasting my time?
I've been fiddling around a lot lately with docker containers for my local development on a linux machine. Tried many different options, also readily available processwire images and tutorials from the forum. But never got it right. Mainly because of permission issues with docker volumes. That is a tricky part on linux machines whereas on OSX it doesn't seem to be an issue.
Then I discovered http://www.wordpressdocker.com/. And the setup with nginx as a proxy that routes requests to separate containers with the actual site install appealed to me. The whole thing sits on top of alpine linux containers which are really lightweight. So I decided to give it a try.
And, first time since experimenting with docker, I got a running PW install. Rewriting was not working until I adjusted the nginx config. Now I have a fairly complex PW site running in a container. Everything is working, image upload/editing etc.
So I'm really exited, especially since the dev site is now blazing fast compared to my old vagrant virtualbox vm setup.
Honestly, I don't really understand everything that is happening behind the scene. But I managed to adjust the original files and build a new image that works with PW and doesn't have all the WP stuff.
The nginx config I took from https://github.com/elasticweb/nginx-configs/blob/master/configs/processwire-2.conf
Not sure if it covers everything for PW3 as well. I would very much appreciate if someone who is more in the know than me could take a look.
All files for building the docker image are here https://github.com/gebeer/alpine-php-processwire
A working image here: https://hub.docker.com/r/gebeer/alpine-php-processwire/
Documentation is kind of lacking. I took over quite a lot from the original project. But following the github README and the original documentation should get people started who have a little experience with docker already.
If someone needs a more in depth step by step tutorial for setting things up, let me know and I'll put something together.