new in linode

Hi, my name is Javier.

I'm very exited to be here.

I'm here because I want to take the next step in my career, I want to build an small application for 2000 users with Ruby, but I have a quiestion for you guys:

What is the best distro for web applications?

I know sometimes this is a subjetive question, I have worked with Ubuntu for a while, and I like it, but I want to work with the best option for web applications,with stability and good support, I don't have any problems to work with any distro so, what do you recomend me?

Thanks.

Javier.

25 Replies

I'm new here also. I installed Ubuntu 10.04 LTS and couldn't be happier.

Also, this page http://www.linode.com/about/ indicates ubuntu is used most on linode.

Thanks for your answer jlevandowski, I saw the guide too, but maybe the popularity of Ubuntu is because it's easy, but i'm not sure about its stability and reliability.

Javier.

If you know ubuntu stick with ubuntu (or debian, ubuntu is derived from debian).

Both the lts versions of ubuntu currently use ruby 1.8.

Ubuntu LTS versions tend to be pretty stable. Most of the stability problems bugging Ubuntu have to do with graphical applications and device drivers – things you won't have to worry about in a Linode environment anyway. Also, it's been a couple of months since the latest LTS version came out, so most of the early issues should have been ironed out.

Having said that, I personally prefer Debian. Guaranteed stability out of the box, and if you know Ubuntu you can use Debian too.

@obs:

If you know ubuntu stick with ubuntu (or debian, ubuntu is derived from debian).

Both the lts versions of ubuntu currently use ruby 1.8.

10.04 LTS uses Ruby 1.9.1.

@hybinet:

Having said that, I personally prefer Debian. Guaranteed stability out of the box, and if you know Ubuntu you can use Debian too.
+1

@BrianJM:

@obs:

If you know ubuntu stick with ubuntu (or debian, ubuntu is derived from debian).

Both the lts versions of ubuntu currently use ruby 1.8.

10.04 LTS uses Ruby 1.9.1.

It shows 1.8 in the package repository online

http://packages.ubuntu.com/lucid/ruby

You're both right: ruby is a metapackage depending on ruby1.8, but both ruby1.8 and ruby1.9 exist.

I was looking at this page (http://packages.ubuntu.com/lucid/ruby/), which shows 1.9.1 is available in the universe repository.

Ah missed that it was in the universe, it's not in the 8.04 universe.

I usually work with CentOS, but that's just because I'm used to a redhat environment, and if you want greater expandability in the future, it's the way to go.

Though, I would strongly suggest Debian to Ubuntu. I don't know why so many people use ubuntu as a server platform, seems a bit silly to me when you have rock hard Debian just waiting for you.

I run a Ruby (on Rails) application on a Linode 512 with 32-bit Debian. I've had zero problems so far!

Instead of using the Ruby interpreter from Debian's repositories, I've installed Ruby Enterprise Edition (still 100% free) which is more efficient with memory usage. The Ubuntu 8.04 packages work in Debian too.

As a server, I use nginx with Phusion Passenger. PostgreSQL serves as the database backend.

@Vudu:

I usually work with CentOS, but that's just because I'm used to a redhat environment, and if you want greater expandability in the future, it's the way to go.

Though, I would strongly suggest Debian to Ubuntu. I don't know why so many people use ubuntu as a server platform, seems a bit silly to me when you have rock hard Debian just waiting for you.

Probably because ubuntu has more press and has a shinier website. I use it because I need some of the newer version of software.

Thanks for your answers.

Reading your answers I can see that I have a lot of things to learn, I think I'll use Ubuntu for the moment, the principal reason is because it works with newer versions of software and because it's easy.

I know that there are others options, but Ubuntu is good for now.

Javier.

I'd say that Ubuntu is a filter of common sense that mitigates the zealotry and crazy-long release schedule of Debian, but then people here would probably get upset with me ;)

Also, it's not as bad as Gentoo's release schedule (or lack of one).

I use Ubuntu because I use Ubuntu. At the time I picked my distro of choice, it was the distribution I chose. LTS for the servers, six-month releases for the workstations.

Turns out that every distribution sucks, so you might as well pick the type of suck you best know how to deal with. I've navigated the Ubuntu bug path a few times and know it well enough that I can productively work around most bugs. (If you're a serious Ubuntu admin, I highly recommend looking into Launchpad's PPA system.)

@hoopycat:

Turns out that every distribution sucks, so you might as well pick the type of suck you best know how to deal with.
Best answer yet - that really belongs in an FAQ.

@Stever:

Best answer yet - that really belongs in an FAQ.

See alt.sysadmin.recovery FAQ, question 3.1.

@Message-ID: :

3.1) Are there any OSes that don't suck?

No. See http://www.ehlke.net/os-suck.html

@Guspaz:

crazy-long release schedule of Debian

That's why they've got backports 8)

Me, I'm running the Testing (Squeeze) version of Debian. It actually feels more stable than Ubuntu 10.04, despite the fact that it still has the "testing" sticker on it.

@hybinet:

@Guspaz:

crazy-long release schedule of Debian

That's why they've got backports 8)
Though even backports are reasonably tightly tied to the release cycle (both for Debian and Ubuntu) which has implications to be aware of.

A few months back I was doing some a-b comparisons with Debian 5 and Ubuntu 8.04 and I tried to grok the Debian backports and for some reason found them more confusing than Ubuntu's. For me backports were important for a few key packages (like PostgreSQL) that I want to stay current with.

Maybe it was how backports pulling from further up the tree (testing and/or even unstable) interacted with the Debian release cycle, and could thus get in the way of a later upgrade the longer you used them after a release had occurred. I seemed to have a harder time quantifying the potential impacts of having backports in use during the transition of a new stable release.

For example, the warning on backports.org about continuing to use etch-backports after lenny's release carrying a risk of preventing an eventual upgrade to lenny. And presumably that risk is introduced the day of a new stable release, so there's a hard window of time to make some decisions once a new stable is coming out, even if there's no immediate intention to upgrade to the new stable.

Backports availability generally matches the release cycle, and the "release when ready" policy of Debian isn't necessarily a positive in terms of backports and ongoing support. For example, etch-backports stopped accepting submissions/updates this past January, just a year after lenny's first release. If you installed etch on your server in 2009, you had a very short lifecycle. Backports for Ubuntu 8.04 is still active (and presumably will be through the end of the LTS support, which is still a few years out for server), and the LTS to LTS upgrade path should remain intact.

Not to say one is necessarily better than the other, but Ubuntu LTS does give you a bit more runway and predictable overlap, all while backports continues to be supported. I find Debian Stable vs. Ubuntu LTS stability debatable in the server space (personally I don't see much difference), but from an administration perspective, maybe I'm just getting old, but I find predictable timing for release and support cycles has a lot going for it. Even if I assume I'll always wait a year into a new 5-year LTS release before considering it, that's still predictable.

Of course, in the context of Linode some of the upgrade stuff may be less critical, as it's certainly plausible to just always start afresh with a new distribution image and move over your applications, than necessarily try to do an in-place upgrade, if the latter is likely to cause any issues.

– David

The danger of ubuntu's backports (and I presume Debians) are that unless you pin the repo, it'll update everything you have installed to whatever is in backports. Of course, with pinning, you can ensure that you get only the package you want and any dependencies.

The alternative is to use PPAs, which are essentially miniature repositories maintained by Ubuntu users, usually for specific packages or small groups of packages, some potential dependencies, built against various versions of Ubuntu. This can also be useful for packages that aren't in the main Ubuntu repositories at all.

When I was using Ubuntu as my desktop OS, I used the smplayer PPA to get a recent version of smplayer, since the version in the Ubuntu repositories was extremely old.

@Guspaz:

The danger of ubuntu's backports (and I presume Debians) are that unless you pin the repo, it'll update everything you have installed to whatever is in backports. Of course, with pinning, you can ensure that you get only the package you want and any dependencies.
Absolutely, and that was something I wish was clearer when I first started with backports, but it took me one system of seeing any backport come in to figure it out. Now, whenever I enable the backports repository on a system, I immediately create a preferences file that assigns 200 to anything in that repository (anything below 500 will do). So nothing happens by default. And yes, the same works with Debian.

When I want a backport, I just specify the backports repository to the install command at which point the level gets a bump that then exceeds the main repositories.

An alternative is to use preferences to prevent backports from ever being installable, but then if you try to cherry pick packages, you end up having to specify any backported dependencies individually. Also, by having a level set, just below the regular repository, once you do install a backport, it'll be maintained if the backport package is updated.

> The alternative is to use PPAs, which are essentially miniature repositories maintained by Ubuntu users, usually for specific packages or small groups of packages, some potential dependencies, built against various versions of Ubuntu. This can also be useful for packages that aren't in the main Ubuntu repositories at all.
Yep, I've used several packages from them. Though one risk I find with the private PPAs is that you have no control over how long they exist. One that I was using (a current version of nginx for 8.04) just disappeared one day when the developer apparently moved on to later releases and retired his support for 8.04. Of course, that didn't negate the installation I had, but if or when I want to upgrade, it'll be back to a locally built version.

– David

@Guspaz:

When I was using Ubuntu as my desktop OS, I used the smplayer PPA to get a recent version of smplayer, since the version in the Ubuntu repositories was extremely old.

Why do you not run it on your desktop now?

I use ubuntu server over debian for more up-to-date package versions.

I'm not running some sort of nasa mission critical system, it's just my box to play with. :)

And ufw rocks https://wiki.ubuntu.com/UncomplicatedFirewall

:)

@jebblue:

@Guspaz:

When I was using Ubuntu as my desktop OS, I used the smplayer PPA to get a recent version of smplayer, since the version in the Ubuntu repositories was extremely old.

Why do you not run it on your desktop now?

It suited my purposes fine for a year or two, but I wasn't doing much gaming. When I got a new computer and built a pretty powerful rig, I wanted to get back to doing more gaming. I also did some fansubbing for a while.

In terms of gaming, gaming on Linux is a joke, no matter what anybody tells you. Barely any games have native ports, those that do take extra effort to get running (getting UT2K4 running involved messing around with replacing sound libraries), WINE makes some games decently playable but can require hours of tweaking to get each game running, and they never run as well as on Windows…

Fansubbing is really tough on Linux, partially because libass is (or was, at the time), very inaccurate in terms of rendering subtitles, and a lot of the tools used just don't exist on Linux.

These days, I'm not fansubbing actively anymore, and I could just dual-boot Ubuntu and Windows for when I want to play games, but it's annoying to be rebooting all the time (I always had a Windows partition even when I ran Ubuntu), and Windows was so much better than Vista that it was just easier to stick to the one OS that did most of what I wanted rather than switching back and forth between two OSes, neither of which fit my needs entirely.

After all, I still maintain a variety of Linux servers and VPSes off-site, and my file server in my apartment runs OpenSolaris (for ZFS). And my laptop does still have a seldom used Ubuntu partition… So on the off chance that I need to do something on Linux or Unix, I certainly have more than enough places to do so.

All of the VPS and servers run Ubuntu, except for the fileserver. I'd run Ubuntu there too if ZFS didn't require FUSE… I could have gone with Nexenta to get the Ubuntu userland, but my worry there was that the kernel and drivers wouldn't be as recent as OpenSolaris.

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct