Comments for VPS.NET Cloud Server Blog | VPS.NET

Comment on PHP Built In Web Server [Developer Tips] by Sajan Parikh

Sajan Parikh — Tue, 14 May 2013 08:07:00 +0000

I guess if you’re talking about a public API with users that sign up for a service. Most APIs we use and deal with are just for data sharing between internal systems. Things we set up for ourselves, in which case scale really is not a factor.

Also, regarding the rewrites, you can achieve http://foo/api/call using the PHP server just fine. In fact, Laravel does this out of the box and works just fine.

Comment on PHP Built In Web Server [Developer Tips] by Anthony Somerset

Anthony Somerset — Tue, 14 May 2013 07:51:30 +0000

Sure you made my point for me – its fine for very small scale but not for API’s as the poster suggested which by there nature probably need to be very scalable. I also want to contest that API’s don’t need rewrites being only half true, they don’t if you plan to use an explicit .php in the file url – eg http://foo/bar.php/api/call However 95% of the API’s I have seen and used don’t do that, they just do http://foo/api/call and guess what…. handle the rewrite at the webserver level – also web servers allow for caching of some API results which to my knowledge the php web server can’t do on its own

Comment on PHP Built In Web Server [Developer Tips] by Sajan Parikh

Sajan Parikh — Tue, 14 May 2013 07:29:30 +0000

Yes, the manual does explicitly state not to use it in production. However, that’s not exactly a law. I’ve got a couple of publically accessible scripts on a small server that I send ‘webhook’ requests to from various services to send POST requests to with notifications.

I promise you, in very small scale uses like that which everyone can benefit from, it’s much easier to cut Apache, NGINX, or whatever web server out of the loop.

Other than stuff like that, sure. You shouldn’t use it in production nor is anyone advocating it.

Comment on PHP Built In Web Server [Developer Tips] by Anthony Somerset

Anthony Somerset — Tue, 14 May 2013 07:01:52 +0000

Recommending the built in php http server is a bad idea, as per the PHP manual: php.net/manual/en/features.commandline.webserver.php the developers explicitly state that its not recommended for production use.

It scales nowhere near as well as PHP-FPM or mod_PHP

Comment on Are You Using A PHP Framework Yet? You Should! by Abby

Abby — Wed, 24 Apr 2013 02:49:49 +0000

Really a nice blog. I want to start my carrier in Php, but I am really confused fro where to start as I do not have any knowledge of php. Is it necessary to learn php with My SQL? I really need some books and other stuff to learn php apart from training. For classes I am starting my course at http://www.wiziq.com/course/5871-php-mysql-with-basic-javascript-integrated-course but I am still confused with which books to follow. I will really appreciate if you can guide me with some good books

Cheers

Abby

Comment on Are You Using A PHP Framework Yet? You Should! by Chris

Chris — Tue, 23 Apr 2013 04:29:18 +0000

Yep, frameworks make development a lot easier. In fact, we often use a framework for even basic multi-page websites where wordpress would be too much work to customise. This makes creating different views and adding more functionality later easier.

Comment on Apache MPMs – Prefork, Worker, and Event by David

David — Mon, 22 Apr 2013 13:27:49 +0000

mod_php works just fine with Worker, we’ve been using it in production environments for many many years.

PHP-FPM is nicer in many ways, but is a much more complicated setup and you lose access to a few things such as apache_note() or the ability to use HTTP Authentication via PHP.

Comment on [Important] Secure Your WordPress Password Immediately – Global WordPress Brute Force Attack by Maak jouw WordPress site en blog in 5 stappen veilig tegen brute kracht aanvallen | Webmaster Resources

Mon, 15 Apr 2013 14:52:05 +0000

[...] codex: Brute Force Attacks Post Matt Mullenweg Passwords and brute force VPS.net (hosting) [Important] Secure Your WordPress Password Immediately – Global WordPress Brute Force Attack Venture Beat WordPress admin accounts target of botnet attacks [...]

Comment on [Important] Secure Your WordPress Password Immediately – Global WordPress Brute Force Attack by Maak jouw WordPress veilig in 5 stappen tegen brutte kracht aanvallen

Maak jouw WordPress veilig in 5 stappen tegen brutte kracht aanvallen — Mon, 15 Apr 2013 04:32:15 +0000

Comment on Apache Worker, I Command Thee! by Madalin Ignisca

Madalin Ignisca — Thu, 11 Apr 2013 11:44:32 +0000

Hello,

I haven’t documented before on MPM’s for apache. I’ve switched to worker after reading this one and saw some little improvements, based on my team feedback when they are working on sites we are building and test on our server.

I’m a happy customer on vps.net