I hope I'm posting this in the right category, I wasn't sure if it should be software or servers, since its Apache software but I know it will be a bit of work on the Server as well.

So, long story short, I have a Web based PHP application that id like to distribute, and id like the preferred installation be the PHP application running on its own instance of Apache and PHP.

I want this for a few reasons...

1. Support - If they use this "Package" I can support them 100%
2. To make it easier for those who dont know how to work with Linux servers or how to install Apache/PHP, or how to manage them
3. So that it will be in its own environment, not in same service with other "websites" or applications

I know a great deal of Linux (Mostly RHEL/CentOS), and I'm pretty well experienced with Apache and PHP (Both from the server side and development standpoints)

The question I have is basically... Whats the best way to go about doing this? Has anyone here tried it before? I couldn't find any decent tutorials online, so I thought id try here.

Thanks!

I don't know if it's the best way but you can chroot it (OpenBSD chroots Nginx by default) or run it in Xen.

Sounds like a job for Docker! See my most recent blog post here about the particulars.

Have Fun!

I might support docker containers as well, but for those who dont use docker.. I want them to be able to do a simple "yum install $application", and have it install a sandboxed Apache or Nginx...

Please, guys, no alternatives, lol. This isnt something I plan on ONLY doing, its something I plan on supporting/supplying as well as things like Docker, Vagrant, Chef/Puppet Recipes, etc.

So I know I can just tear into the RPM file and see whats needed, I was just wondering if anyone has a better way of doing it.

It fits all your requirements.
and can be "up and running" in 5 minutes.

and if you "might support" docker/vagrant/chef/puppet, your users won't know any of those either, so why not give it a try?
"yum install $application" is a repo command not an rpm install command. So your reasons for not trying it out
don't make any sense to me.
Your way seems like more work.

You could build your application in a custom container and publish it yourself.

BTW: works on CentOS/Redhat/Fedora/*SUSE and Ubuntu flavored hosts.

You asked for ideas and then say "No alternatives".
This isn't Burger King.
The proper reply is "Thank you".

Good Luck.

Hi

I don't think that these reasons...
...are very strong.
You'll end up with a bunch of clueless people that have no clue about webservers => you'll end up having to take care about all their needs (performance, security, stability).
For example you'll have to act every time that a user will want to run any additional webservice (and that need some kind of different Apache/PHP setting because of the other webservices), every time that Apache/PHP provides some security patches, etc... .
Additionally, I'm not sure what you'll have to do with the various dependencies of Apache/PHP if you run it full standalone.
My best recommendation would be to run it in some kind of linux "container" as the others have stated as well, but that won't match your requirements.