Ha, this ease of hosting question. 1- Ease of hosting
Thing is that mod_php and PHP itself are easy to compile for almost any distro. With Pharo that's not so easy (64-bit platforms requiring 32-bit libs and some dark tricks to get right [e.g. using experimental debian repos for libc, which no sane hosting company would allow]. We need to come to par with this platform ubiquity if we want to be wider spread. 2- Process vs on-request PHP-based solutions mostly have the request->apache->mod_php->scripts->db and back roundtrip. When there is no client, there is no CPU, no nothing used. This allows to pile on users in a shared hosting as there is usually not that much traffic. With the current Pharo+Seaside combo for example, we do have an always running pharo process taking away CPU cycles. That's not too good for shared hosting and platforms like EC2 where we pay based on that. As my thinking goes, I find interesting to have a FastCGI interface for pure Pharo (until we possibly have a mod_pharo) so that pharo becomes a first class scripting option for simple web applications. With the new command line and environment access, that's not that hard to do. Is there anyone using pharo in such a configuration? Phil On Mon, Feb 17, 2014 at 9:38 AM, Yuriy Tymchuk <[email protected]> wrote: > Hi guys, > > this weekend I was unlucky enough to work with WordPress and all it's > shitty php. Now obvious question is what is the status of Pharo-based CMSes > and how they can be hosted. Right now I'm looking for a free solution. Yes, > I know that developers also want to eat, but, usually people use (for > example) WordPress, because they can put it on a free php hosting, and I > cannot promote Pharo-based solutions if you have to py for them in a first > place. Also from CMS point of view, I'm aware of Pier, but is it the best > thing that I should look into? > > Uko >
