Slashdot Mirror
LinRails — Ruby On Rails For Linux
foobarf00 writes "LinRails is a binary package that includes Ruby-1.8.6, Rubygems-0.9.4, Rails 1.2.3, Mongrel 1.0.1, MySQL-5.0.41, ncurses-5.6, OpenSSL-0.9.8e, and zlib-1.2.3. Its goal is to make it easy to get a Ruby on Rails development environment running in no time. This initial 0.1 release doesn't have a Web server in the package; opinions are solicited as to which to include."
...up2date?
:-P
monk.e.boy
Open source, flash charts
Makes this so easy it's hardly worth the packaging bother. Although I guess people still saddled with the atrocious Yum will like it.
> It includes Mongrel 1.01 [...]
>This initial 0.1 release doesn't have a Web server
Mongrel is a very good web server, especially for a development environment. (And the ruby package includes webbrick on top of that). Current 'best practice' deployments of RoR applications usually use a pack of Mongrels behind a load balancer (such as mod_proxy or Pound), and/or Apache or Nginx to serve static pages. If you want to completely mirror your production environment in your development/testing environment than including those would the logical choice.
This sig is just as redundant as the rest of this posting
because MySQL is free.
See, you're not the only one that can spew garbage.
This is great news for me. I recently built an Ubuntu system on which to do media production (music, video, like that). It's not my primary system yet, but I've been so disgusted with Windows Vista and Mac OS that I decided it was time to make (another) try at doing my work on a Linux system.
After three months, the results have far exceeded my expectation. I'm very impressed with the maturity of music production apps for Linux and the performance has been as strong as I expected. I'm still a Linux noob, but the experience has been positively inspirational. In fact, it's been a lot like my first experiences with media production on my first Mac, where just about every day brought another new way to look at the work.
I'm not a programmer, but I'm learning Ruby and this new release gives me one more reason to sit down at the Linux box instead of my others.
You are welcome on my lawn.
Color me stupid here, but isn't Apache the de facto standard that most everyone uses?
Some may argue that better alternatives exist (of which I'm not really aware) but since Apache is so popular and common place, wouldn't it seem the logical piece of this meta-package?
People who want specific packages for specific reasons are going to set up their own environment. For a pre-setup environment, shouldn't you shoot for the common setup?
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
I imagine a meta-package like this is catering to the average user who just wants a common setup easy to just drop in and go. MySQL is more commonly used, and thusly it seems the logical choice for such a meta-package.
Though I'm looking to move off a web-host and build a server out of my house. Everyone keeps saying PostgreSQL is better. Why? For my average use, what benefits will it offer me?
If I throw some common PHP/SQL stuff on there, will it run faster (Gallery2, LotGD, phpbb3, etc)?
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
This thing is completely pointless and unnecessary under modern Linux package management systems. One could just create a metapackage with the proper dependencies.
Even without such a metapackage, one can install this software with a single apt-get command line. Windows-based development methodology is bad enough, let's not infect linux/unix development with it.
we discovered a new way to think.
"Little does he know, but there is no 'I' in 'Idiot'!"
If I throw some common PHP/SQL stuff on there, will it run faster (Gallery2, LotGD, phpbb3, etc)? I know that a lot of people here will kill me and say "but you can do this in mysql too!! (somehow)", but:
- Integrity: if i delete from people where id=1; all child tables of people (telephone numbers, addresses and whatnot) are kept. On top of that you are allowed to delete the parent if it has childs. I hate this default behavior.
- ACID
- Stored Procs: You may not use them, but one day you may will. Maybe you will have to insert rows in a table after an update on another, or implement some other things that are best implemented on the database. If you use pg from the beginnig you can.
- Triggers: the same
This are my main choices I choose pg ove mysql, but this is really a personal choice. The flamewar between mysql an pg will never end, I think it's like emacs vs vi.
I just don't trust anything that bleeds for five days and doesn't die.
MySQL just seems more common and I can't see that changing. Pretty much every web development book and site uses MySQL for database teachings so as people come into web development I'd argue it's just going to increase the MySQL user base even more.
For most people's web development needs MySQL just does what you need. Chances are if you need something MySQL doesn't have then you're already competent enough to not need a package like this and set it all up yourself anyway, this just makes it easier for those who are relatively new to web development to jump straight in.
I'm just about to start learning RoR myself and I just run my practice servers as VMs so for people like me, it's pretty easy to just setup a Linux VM, install a package like this and knuckle straight down with learning RoR. When I've got a decent understanding of it and am sure it's something I really do want to continue with I'll start to pay more attention to setting it up in a production environment and I'll start looking further into different databasing options and so forth.
Why bother with either. Just include sqlite and be done with it. Rails can take care of all the data integrity for you anyway. Combine that with microapache and you are done.
evil is as evil does
I've read a little about Ruby on Rails. Will somebody list one site that's on Rails and is worth a flip? I've seen the hype, but I'd love to see a site that talks the talk. Thanks!
Mongrel is a web server, hence this package includes a web server (unless it doesn't actually contain Mongrel, despite what the writeup says). Also, Ruby 1.8.6 comes with WEBrick, which is a the web server Rails uses by default...
Anyway isn't a simplified Rails installer for Linux kind of redundant? Most newer Linux distros I've seen already have a native package that installs Ruby on Rails and all its dependencies. Most people will probably find the Instant Rails package a lot more useful, since it does the same for Windows.
After months of hard work I finally bring Debian/Ubuntu/Xandros/[derivativus infinitum] users a computer program that will not only download the latest RoR development packages for you, it will also notify you of new versions when they become available later.
Moreso, all the packages I provide are registered in a special database so that should you choose to remove the below packages, you can do so with ease using a GUI button or the command line!
Please download the following code into your computer terminal and compile it by hitting ENTER (one-key compile for convenience).
sudo apt-get update ; sudo apt-get install rails ruby rubygems libruby1.8-extras mysql libncurses-ruby openssl libzlib-ruby
The above program is licensed under the "Why Make It Harder Than It Needs 2B License". Please use this link to make a donation to my project.
We have Oracle 8, Sybase 12 and postgresql 8 (I think).
The whole factory is run off of postgresql.
The financial system is run off of Oracle.
The timesheet system is run off of Sybase.
Guess the systems which gave the most and least problems.
The winner is PostgreSQL. Untouched for months, perhaps even years. Next we have Oracle which is a pain in the arse to manage but never failed. and last place came sybase which had to be touched, managed and/or restarted regularly[1].
In terms of transactions, the factory systems took an absolute pounding, the financial system was used extensively daily and the timesheet system got maybe thousand updates per day.
PostgreSQL's largest benefit is reliability.
[1] Clearly these attributes are what made Sybase the product of choice for Microsoft to build their enterprise database management system upon.
Deleted
I can, on the other hand, highly recommend Wicket, its what we used to build Thoof, and so-far its scaling very well indeed.
As a frustrated Windows user who would like to switch to Linux but can't get it to work, let me explain this to you:
.exe always works regardless of what Windows version I'm using, while a Linux package generally doesn't work on the Linux distro I'm trying.
.exe that will fix my internet connection, it's rather obvious to me that I can download the .exe from another PC, put it on a USB key and run it on my own PC. however, if I get an apt-get line to help me fix my internet connection, I have absolutely no clue what to do with it.
1) in my experience a Windows
2) if I'm given a link to a
Zope, Plone, Django, Turbogears -- cool.
Cake, Symfony -- stay the hell away from these crummy frameworks.
And sure Rails may be overhyped, but that doesn't mean that it's bad.
this space intentionally left blank
Both Symfony and Cake seemed nice at first, but I couldn't even follow their 101 tutorials because the instructions were not correct for the current stable versions. Sure I could have figured it out, but when I have a fairly short time to evaluate these things I'm not going to start diving into the source just to get started! I didn't have to do that with Rails, and I didn't have to do that with the Zend framework (which was at v0.14 at the time).
Qcodo is interesting. Seagull looked fairly interesting as well, but this was a small internal project and the Zend framework fit the bill nicely.
So it was based on a quick 20-minute dicking around. If you're very interested in the projects then they may work well for you, and for all I know the docs actually match the code by now which I guess was the biggest turn off.
Or is it PHP that you don't like? I'm really interested. Propels XML is the only potential downside I can see. And that doesn't seen to much of a problem. I won't pretend to be a PHP fan but that didn't factor into my choice of framework since it had to be done in PHP. I didn't take more than a 20-minute glance at Propels (as part of Symfony iirc) so I don't have much of an opinion on it.
Cake and Symfony try very hard to be Rails. If you have a choice of language I strongly urge anyone looking at those 2 to just use the real deal instead. If you want to use PHP then I would still urge you to look at Prado, Seagull, Zend framework or Qcodo before these 2. At least those have some unique features and direction, rather than just picking up the scraps Rails throws away.
this space intentionally left blank