Ask Slashdot: Is There a Web Development Linux Distro?

Qbertino writes I've been a linux user for more than 15 years now and in the last ten I've done basically all my non-trivial web development on Linux. SuSE in the early days, after that either Debian or, more recently, Ubuntu, if I want something to click on. What really bugs me is, that every time I make a new setup, either as a virtual machine, on concrete hardware or a remote host, I go through 1-2 hours of getting the basics of a web-centric system up and running. That includes setting PHP config options to usable things, setting up vhosts on Apache (always an adventure), configging mod_rewrite, installing extra CLI stuff like Emacs (yeah, I'm from that camp) walking through the basic 10-15 steps of setting up MySQL or some other DB, etc. ... You get the picture.

What has me wondering is this: Since Linux is deeply entrenched in the field of server-side web, with LAMP being it's powerhouse, I was wondering if there aren't any distros that cover exactly this sort of thing. You know, automatic allocation of memory in the runtime settings, ready-made Apache http/https/sftp/ftp setup, PHP all ready to go, etc. What are your experiences and is there something that covers this? Would you think there's a need for this sort of thing and would you base it of Debian or something else? If you do web-dev, how do you do it? Prepareted scripts for setup? Anything else? ... Ideas, unkown LAMP distros and opinions please."

Comments

Probably not...

[Improv]

Not everyone configures this stuff the same way, and new versions of software would mean you'd need to change this tuning all the time. Plus, you'd likely need to know all the tuning anyhow in case you need to debug or adjust it. Your best solution probably is not going to hope for a distro so much as baking yourself an image (or install script, or chef/puppet/ansible recipeset, or similar) and using it to build these systems for you. A custom distro wouldn't make sense.

Re:Probably not...

[Idimmu Xul]

Exactly this, thread over.

You should be developing for the platform you're deploying to, whether that's a series of company maintained servers or some random CPanel hosting you've bought for $1 a month.

The best way is to bake yourself an image you can run from scratch each time that gets installed and configured to a known outcome, hello Puppet/Chef/Ansible/Vagrant/etc/etc

That gives you the benefit on developing on what ever platform with whatever toolset you like the most and an extremely reliable test platform that accurately mirrors your deployment platform.

Otherwise you open yourself and your code to all kinds of unnecessary bugs later on.

Re:Probably not...

[slickwillie]

Actually, Improv's answer wasn't "it can't be done" but more like "it could be done but it doesn't make sense".

He (or she) probably wouldn't want to work for you if your reading comprehension is that low.

Automation is your friend

[Drewdad]

http://xkcd.com/1205/

Have you tried Turnkey Linux?

[markswims2]

It's as close to out-of-the-box as I've found.

http://www.turnkeylinux.org/la...

Re: Roll your own?

[Lunix Nutcase]

Slashdot has never had an edit button.

Re: Roll your own?

[BlackPignouf]

Slashdot has a well-hidden edit button.
EDITED : 2015-02-08 18:40:02 +0100

Re:Yes

[jc42]

Any fucking distro you want. Pretty much every distro does this.

Well, yeah, they mostly come with most of the pieces you want. But this doesn't help. I've found that trying to find where all the pieces are hidden/renamed in any given distro and then trying to figure out how they've tweaked the config stuff is far too time consuming. While someone else is beating their head against their keyboard over all the frustrations, I can beat them out by downloading the latest stable version of apache and each other package I want, and installing them from scratch. The packages in the repositories tend to not change their UI much, only when they have a good reason to do so. Also, they know that their users will be installing from scratch, so they concentrate in making this easy (which includes being mostly consistent with earlier releases, and providing forums that tend to have useful answers to questions).

So my advice is to just scrap the servers and associated packages that come with the distro. Uninstall them if you can discover how to do that in a reasonable time, or just disable them. Copy the config files from another machine that's close to what you want. You'll get it up in much less time than you'd waste trying to figure out how the distro has tweaked everything.