Re:Avoid PHP trap
by randallsquared on Saturday July 05, 2008 @09:18PM
(#237469)
Weird php.ini settings can almost always still go in the directory with the php files, so just copying the directory automagically makes everything work right. Some settings don't work this way, of course, but I'm not sure which those would be, offhand.
If you're using Python, for example, you're probably also using some framework... for years I used Webware for Python, and more recently web.py. Both require careful attention to get working in a convenient fashion, in my opinion.
Re:Avoid PHP trap
by jamesbritt on Sunday July 06, 2008 @01:10AM
(#237609)
" That's all there is to deploying Perl, Ruby, and Python these days."
And scaling with those languages is a solved problem.
Aren't most PHP apps dependent on weird php.ini settings?
And anyway, the "real" langauges are equally easy to deploy. Get yourself a $20 slicehost account (to start with), add two lines to apache's config to enable FastCGI, then just copy your app up to that server. That's all there is to deploying Perl, Ruby, and Python these days.
With Perl and Catalyst, I can "make catalyst_par" and get a file that contains the entire application; including the version of Perl I am developing with. That way I know for sure it will work when I copy it to production. (Yes, this means I have to use the same architecture for both development and deployment. I do.)