I don't think that either of these links provide reasons not to use Ubuntu, it is more telling you how to install it a few different ways and what to expect with each way you install it.

For most servers, once you have them up and running, there are very few reasons to upgrade as you don't want to break a production environment that doesn't need fixing, so a production environment in Ubuntu shouldn't really be a problem.

I think that you should be a little more careful with comments, as saying baseless things like this could scare a noob away from using something that is fine to use and making their experience more difficult than it has to be.

I was simply expressing my opinion that there are valid reasons as stated in Debian's Position that it can present one with difficulties down the road. As I said I elected to avoid the problems by not using ruby on rails. I for one would not be happy if someone didn't point that out and I was left with an un-upgradable system or at the very least one that might be somewhat more difficult to upgrade.

Sorry you think I'm badmouthing Ubuntu, in fact my intent was more to warn people away from Ruby on Rails because I believe its Ruby Gems to be a poor idea. I like Ubuntu and encourage anyone to use it. I don't want people to blindly implement a distro that might give them grief down the road. That's a sure fire way to get people to really badmouth a distro.

Jim

My point was that if you make wild statements, some people will take it as gosbel when they really shouldn't. The only thing you really need to do to have a perfectly upgradeable system is install gems from source, ruby and your server via packages and you are set to go, both are easily upgradable, system via apt and ruby gems via the built in installer, but to be honest once they are set up right upgrading production systems should be minimal where it can be avoided to keep stability high.

Just one question, if this scared you off rails what did you decide to use instead?

I didn't. I wanted to run an app that used it but decided the hassle was too great, so I didn't use that app. I'm not a big fan of Ruby on Rails as can tell.

Thanks,

Jim.

That's cool, you don't have to like Rails, I was just curious.

Hi Navi,

What you'd outline here is very useful. I followed every step you mentioned and got my website working. Thanks!