I''m putting together a "One-Click Ruby Server" that will install all software needed to set up a ruby-based server (all configured and ready-to-go). I am initially doing this for the Windows platform (I would welcome anyone who wanted to create versions for other platforms). My general model is something along the lines of EasyPHP and XAMPP. My motivation is to help spread the adoption of Ruby and Rails by lowering the effort needed to setup and maintain a ruby-based server environment. While one of my primary motivations is the support of Rails, I want this to be useful for non-Rails use of a ruby-based server, as well. So, what would you recommend that I include? Here''s my current short list: - ruby 1.8.2 - apache 1.3 (not apache 2) - mysql - mod_ruby - mod_fastcgi - rails - openssl Please give me your recommendations/caveats/advice. Thanks, Curt -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.296 / Virus Database: 265.6.5 - Release Date: 12/26/2004
Hi, On Tue, 28 Dec 2004 09:57:33 -0600, Curt Hibbs <curt-fk6st7iWb8MAvxtiuMwx3w@public.gmane.org> wrote:> I''m putting together a "One-Click Ruby Server" that will install all > software needed to set up a ruby-based server (all configured and > ready-to-go). I am initially doing this for the Windows platform (I would > welcome anyone who wanted to create versions for other platforms). My > general model is something along the lines of EasyPHP and XAMPP. > > My motivation is to help spread the adoption of Ruby and Rails by lowering > the effort needed to setup and maintain a ruby-based server environment. > While one of my primary motivations is the support of Rails, I want this to > be useful for non-Rails use of a ruby-based server, as well. > > So, what would you recommend that I include? Here''s my current short list: > > - ruby 1.8.2 > - apache 1.3 (not apache 2)Why not Apache2? The PHP guys use to recommend Apache 1.3 but Apache 2 is supposed to be better on Windows. The recommended approach is to use FastCGI on Windows because mod_ruby has some caveats on Windows anyway.> - mysqlODBC, Firebird, and maybe other database drivers?> - mod_ruby > - mod_fastcgi > - rails > - opensslImageMagick, PDF libraries (at least two are native Ruby), what else? :-)> > Please give me your recommendations/caveats/advice. > > Thanks, > CurtCheers, Joao
Curt Hibbs wrote:> I''m putting together a "One-Click Ruby Server" [...] > So, what would you recommend that I include? Here''s my current short list: > > - ruby 1.8.2I''d suggest using the Ruby from the One-Click Installer as it does include lots of libraries that might be helpful to have around when doing something fancy. Maybe RMagick also ought to be included.> - mysqlDepending on how difficult it is to do it would also be nice to have SQLite and PostgreSQL support. And thank you a lot for doing this, it is something that will be very useful to the community as a whole.
Joao Pedrosa wrote:> > On Tue, 28 Dec 2004 09:57:33 -0600, Curt Hibbs <curt-fk6st7iWb8MAvxtiuMwx3w@public.gmane.org> wrote: > > > > So, what would you recommend that I include? Here''s my current > short list: > > > > - ruby 1.8.2 > > - apache 1.3 (not apache 2) > > Why not Apache2? The PHP guys use to recommend Apache 1.3 but Apache 2 > is supposed to be better on Windows. The recommended approach is to > use FastCGI on Windows because mod_ruby has some caveats on Windows > anyway.Its my understanding that that there are still issues with apache2 and the other software components that I would be including. Correct me if I am mistaken, but if true, I would want to stick with a known, stable combination.> > - mysql > > ODBC, Firebird, and maybe other database drivers?Just to make sure I was clear, I''m taking about including mysql itself -- not just the drivers.> > - mod_ruby > > - mod_fastcgi > > - rails > > - openssl > > ImageMagick, PDF libraries (at least two are native Ruby), what else? :-)Thanks for your suggestions, Curt
Florian Groß wrote:> > Curt Hibbs wrote: > > > I''m putting together a "One-Click Ruby Server" [...] > > So, what would you recommend that I include? Here''s my current > short list: > > > > - ruby 1.8.2 > > I''d suggest using the Ruby from the One-Click Installer as it does > include lots of libraries that might be helpful to have around when > doing something fancy. Maybe RMagick also ought to be included.I am going to steal the build scripts for the one-click installer (and take this opportunity to refactor them, and feed them back into that project), so many of the libs in the one-click installer will be included. I will leave out those that are not applicable to a server environment (like FXRuby).> > - mysql > > Depending on how difficult it is to do it would also be nice to have > SQLite and PostgreSQL support.I think lot''s of DB drivers should be included. I also plan to include some actual DBs themselves. MySQL for sure, possibly SQLite. I suppose there could be others if the demand was high enough. But since I want to provide an integrated admin interface, I''ll probably have to limit this initially.> And thank you a lot for doing this, it is something that will be very > useful to the community as a whole.I''m just being selfish... I want to make Ruby popular enough that someone will hire me (fulltime) to do Ruby work! :-) Curt
Marcel Molina Jr.
2004-Dec-28 17:08 UTC
Re: One-Click Ruby Server -- What should it include?
On Tue, Dec 28, 2004 at 09:57:33AM -0600, Curt Hibbs wrote:> I''m putting together a "One-Click Ruby Server" that will install all > software needed to set up a ruby-based server (all configured and > ready-to-go). I am initially doing this for the Windows platform (I would > welcome anyone who wanted to create versions for other platforms). My > general model is something along the lines of EasyPHP and XAMPP. > > My motivation is to help spread the adoption of Ruby and Rails by lowering > the effort needed to setup and maintain a ruby-based server environment. > While one of my primary motivations is the support of Rails, I want this to > be useful for non-Rails use of a ruby-based server, as well. > > So, what would you recommend that I include? Here''s my current short list: > > - ruby 1.8.2 > - apache 1.3 (not apache 2) > - mysql > - mod_ruby > - mod_fastcgi > - rails > - openssl > > Please give me your recommendations/caveats/advice.Something similar to this was talked about in #rubyonrails about a week ago. The idea was to include Tar2rubyscript along with rails and add a rake task that would make a single executable of your entire rails app using the Tar2rubyscript. Additionally, the webrick servlet would be able to take far more configuration through command line options so that a database adapter could be specified, a database name, username and password, etc so that this self contained ruby archive of your rails application would just delegate to the webrick server when executed passing along the parameters on the command line. It would assume various conventions in the db directory, such as sqlite.sql, mysql.sql and postgresql.sql. It could, if instructed, build the db and db structure then start up the webrick server and you are good to go. As a proof of concept I made an archive of Hieraki with a simple init.rb script for Tar2rubyscript that built the db and then started Webrick. On my system (debian) it just *worked* so I''m hopeful, though I have no idea how it works on other OSes. Another idea that was presented was to allow for this kind of functionality from a browser as well (a "shim" I believe this is called?) so that someone wouldn''t have to open up a command prompt. I volunteered to work on the enhancements to the webrick server but have not gotten to that yet. I hope to very soon, maybe starting today...In any event, the goals here sound quite similar and we had also talked about integrating ruby2exe into things. marcel -- Marcel Molina Jr. <marcel-WRrfy3IlpWYdnm+yROfE0A@public.gmane.org>
----- Original Message ----- From: "Marcel Molina Jr." <marcel-WRrfy3IlpWYdnm+yROfE0A@public.gmane.org> To: "Rails-ML" <rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org> Subject: Re: [Rails] One-Click Ruby Server -- What should it include? Date: Tue, 28 Dec 2004 12:08:27 -0500> > On Tue, Dec 28, 2004 at 09:57:33AM -0600, Curt Hibbs wrote: > > I''m putting together a "One-Click Ruby Server" that will install all > > software needed to set up a ruby-based server (all configured and > > ready-to-go). I am initially doing this for the Windows platform (I would > > welcome anyone who wanted to create versions for other platforms). My > > general model is something along the lines of EasyPHP and XAMPP. > > > > My motivation is to help spread the adoption of Ruby and Rails by lowering > > the effort needed to setup and maintain a ruby-based server environment. > > While one of my primary motivations is the support of Rails, I want this to > > be useful for non-Rails use of a ruby-based server, as well. > > > > So, what would you recommend that I include? Here''s my current short list: > > > > - ruby 1.8.2 > > - apache 1.3 (not apache 2) > > - mysql > > - mod_ruby > > - mod_fastcgi > > - rails > > - openssl > > > > Please give me your recommendations/caveats/advice. > > Something similar to this was talked about in #rubyonrails about a > week ago. The idea was to include Tar2rubyscript along with rails > and add a rake task that would make a single executable of your entire > rails app using the Tar2rubyscript. Additionally, the webrick servlet > would be able to take far more configuration through command line > options so that a database adapter could be specified, a database name, > username and password, etc so that this self contained ruby archive of > your rails application would just delegate to the webrick server when > executed passing along the parameters on the command line. It would assume > various conventions in the db directory, such as sqlite.sql, mysql.sql and > postgresql.sql. It could, if instructed, build the db and db structure > then start up the webrick server and you are good to go. As a proof of > concept I made an archive of Hieraki with a simple init.rb script for > Tar2rubyscript that built the db and then started Webrick. On my system > (debian) it just *worked* so I''m hopeful, though I have no idea how it works > on other OSes. > > Another idea that was presented was to allow for this kind of > functionality from a browser as well (a "shim" I believe this is > called?) so that someone wouldn''t have to open up a command prompt. > > I volunteered to work on the enhancements to the webrick server but have > not gotten to that yet. I hope to very soon, maybe starting today...In > any event, the goals here sound quite similar and we had also talked > about integrating ruby2exe into things.This sounds like a very nice and simple packaging and delivery mechanism for rails apps. And, as you pointed out, there is considerable overlap here even though it is different. Eventually, I''d like to see the ability to create rubygems of rails apps (or rails add-ons) that can be easily deployed to a one-click ruby server installation (as well as beaing easily managed and updated). Curt
Curt Hibbs:> I''m putting together a "One-Click Ruby Server" that will install all > software needed to set up a ruby-based server (all configured and > ready-to-go). I am initially doing this for the Windows platform (I would > welcome anyone who wanted to create versions for other platforms). My > general model is something along the lines of EasyPHP and XAMPP. > > My motivation is to help spread the adoption of Ruby and Rails by lowering > the effort needed to setup and maintain a ruby-based server environment. > While one of my primary motivations is the support of Rails, I want this to > be useful for non-Rails use of a ruby-based server, as well. > > So, what would you recommend that I include? Here''s my current short list: > > - ruby 1.8.2 > - apache 1.3 (not apache 2) > - mysql > - mod_ruby > - mod_fastcgi > - rails > - openssl > > Please give me your recommendations/caveats/advice.That is really great. Please don''t laugh, but I think it would also be wise to inlude at least PHP (if not Python and Perl, too) with Ruby being default somehow. A lot of ppl (like myself) still have a lot of php work to maintain and I wouldn''t install a second apache/mysql/... combination just to have ruby/rails support. The other webframeworks would be great, too. IOWA, Nitro, Cerise, etc. -- Sascha Ebach
Sascha Ebach wrote:> > Curt Hibbs: > > I''m putting together a "One-Click Ruby Server" that will install all > > software needed to set up a ruby-based server (all configured and > > ready-to-go). I am initially doing this for the Windows platform (I would > > welcome anyone who wanted to create versions for other platforms). My > > general model is something along the lines of EasyPHP and XAMPP. > > > > My motivation is to help spread the adoption of Ruby and Rails by lowering > > the effort needed to setup and maintain a ruby-based server environment. > > While one of my primary motivations is the support of Rails, I want this to > > be useful for non-Rails use of a ruby-based server, as well. > > > > So, what would you recommend that I include? Here''s my current short list: > > > > - ruby 1.8.2 > > - apache 1.3 (not apache 2) > > - mysql > > - mod_ruby > > - mod_fastcgi > > - rails > > - openssl > > > > Please give me your recommendations/caveats/advice. > > That is really great. Please don''t laugh, but I think it would also be wise to > inlude at least PHP (if not Python and Perl, too) with Ruby being default > somehow. A lot of ppl (like myself) still have a lot of php work to maintain > and I wouldn''t install a second apache/mysql/... combination just to have > ruby/rails support.I''m not laughing... I can see the value here (although, I think I''d rather have something like this packaged as a separately installed add-on.> The other webframeworks would be great, too. IOWA, Nitro, Cerise, etc.Would it make sense for any of these to be installed by default, or would it be good enough that they could be subsequently installed via RubyGems? Curt
I agree PHP should be part of it. If for nothing else then phpmyadmin and maybe a comparable tool for sqlite. PHP can easily be setup to work over fastcgi. So no mod_php required. Likewise I would not really include mod_ruby since it only allows you to run one rails application at a time on the server and people might get a wrong impression from this. FastCgi is recommended for production use anyways. Thank you for this project! This is will be great! On Tue, 28 Dec 2004 10:53:13 -0800, Curt Hibbs <curt-fk6st7iWb8MAvxtiuMwx3w@public.gmane.org> wrote:> Sascha Ebach wrote: > > > > Curt Hibbs: > > > I''m putting together a "One-Click Ruby Server" that will install all > > > software needed to set up a ruby-based server (all configured and > > > ready-to-go). I am initially doing this for the Windows platform (I would > > > welcome anyone who wanted to create versions for other platforms). My > > > general model is something along the lines of EasyPHP and XAMPP. > > > > > > My motivation is to help spread the adoption of Ruby and Rails by lowering > > > the effort needed to setup and maintain a ruby-based server environment. > > > While one of my primary motivations is the support of Rails, I want this to > > > be useful for non-Rails use of a ruby-based server, as well. > > > > > > So, what would you recommend that I include? Here''s my current short list: > > > > > > - ruby 1.8.2 > > > - apache 1.3 (not apache 2) > > > - mysql > > > - mod_ruby > > > - mod_fastcgi > > > - rails > > > - openssl > > > > > > Please give me your recommendations/caveats/advice. > > > > That is really great. Please don''t laugh, but I think it would also be wise to > > inlude at least PHP (if not Python and Perl, too) with Ruby being default > > somehow. A lot of ppl (like myself) still have a lot of php work to maintain > > and I wouldn''t install a second apache/mysql/... combination just to have > > ruby/rails support. > > I''m not laughing... I can see the value here (although, I think I''d rather have something like this packaged as a separately installed add-on. > > > The other webframeworks would be great, too. IOWA, Nitro, Cerise, etc. > > Would it make sense for any of these to be installed by default, or would it be good enough that they could be subsequently installed via RubyGems? > > Curt > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- Tobi http://blog.leetsoft.com
Tobias Luetke wrote:> > I agree PHP should be part of it. If for nothing else then > phpmyadmin and maybe > a comparable tool for sqlite.Hmmm... good point!> PHP can easily be setup to work over fastcgi. So no mod_php required. > Likewise I would not really include mod_ruby since it only allows you to > run one rails application at a time on the server and people > might get a wrong > impression from this. FastCgi is recommended for production use anyways.More good points... thanks! Curt> Thank you for this project! This is will be great! > > > On Tue, 28 Dec 2004 10:53:13 -0800, Curt Hibbs <curt-fk6st7iWb8MAvxtiuMwx3w@public.gmane.org> wrote: > > Sascha Ebach wrote: > > > > > > Curt Hibbs: > > > > I''m putting together a "One-Click Ruby Server" that will install all > > > > software needed to set up a ruby-based server (all configured and > > > > ready-to-go). I am initially doing this for the Windows > platform (I would > > > > welcome anyone who wanted to create versions for other > platforms). My > > > > general model is something along the lines of EasyPHP and XAMPP. > > > > > > > > My motivation is to help spread the adoption of Ruby and > Rails by lowering > > > > the effort needed to setup and maintain a ruby-based server > environment. > > > > While one of my primary motivations is the support of > Rails, I want this to > > > > be useful for non-Rails use of a ruby-based server, as well. > > > > > > > > So, what would you recommend that I include? Here''s my > current short list: > > > > > > > > - ruby 1.8.2 > > > > - apache 1.3 (not apache 2) > > > > - mysql > > > > - mod_ruby > > > > - mod_fastcgi > > > > - rails > > > > - openssl > > > > > > > > Please give me your recommendations/caveats/advice. > > > > > > That is really great. Please don''t laugh, but I think it > would also be wise to > > > inlude at least PHP (if not Python and Perl, too) with Ruby > being default > > > somehow. A lot of ppl (like myself) still have a lot of php > work to maintain > > > and I wouldn''t install a second apache/mysql/... combination > just to have > > > ruby/rails support. > > > > I''m not laughing... I can see the value here (although, I think > I''d rather have something like this packaged as a separately > installed add-on. > > > > > The other webframeworks would be great, too. IOWA, Nitro, Cerise, etc. > > > > Would it make sense for any of these to be installed by > default, or would it be good enough that they could be > subsequently installed via RubyGems? > > > > Curt > > _______________________________________________ > > Rails mailing list > > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > > > -- > Tobi > http://blog.leetsoft.com > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.296 / Virus Database: 265.6.5 - Release Date: 12/26/2004 >
Curt Hibbs:> Sascha Ebach wrote: > >> Curt Hibbs: >> >>> I''m putting together a "One-Click Ruby Server" that will install >>> all software needed to set up a ruby-based server (all configured >>> and ready-to-go). I am initially doing this for the Windows >>> platform (I would welcome anyone who wanted to create versions >>> for other platforms). My general model is something along the >>> lines of EasyPHP and XAMPP. >>> >>> My motivation is to help spread the adoption of Ruby and Rails by >>> lowering the effort needed to setup and maintain a ruby-based >>> server environment. While one of my primary motivations is the >>> support of Rails, I want this to be useful for non-Rails use of a >>> ruby-based server, as well. >>> >>> So, what would you recommend that I include? Here''s my current >>> short list: >>> >>> - ruby 1.8.2 - apache 1.3 (not apache 2) - mysql - mod_ruby - >>> mod_fastcgi - rails - openssl >>> >>> Please give me your recommendations/caveats/advice. >> >> That is really great. Please don''t laugh, but I think it would also >> be wise to inlude at least PHP (if not Python and Perl, too) with >> Ruby being default somehow. A lot of ppl (like myself) still have a >> lot of php work to maintain and I wouldn''t install a second >> apache/mysql/... combination just to have ruby/rails support. > > > I''m not laughing... I can see the value here (although, I think I''d > rather have something like this packaged as a separately installed > add-on.Maybe a minimum distribution, ruby concentric and the maximum thing with all bells and whistles. Looking at xampp this could get rather large (prolly > 100 MB). I would only be interested in the latter.>> The other webframeworks would be great, too. IOWA, Nitro, Cerise, >> etc. > > > Would it make sense for any of these to be installed by default, or > would it be good enough that they could be subsequently installed via > RubyGems?I don''t think so. My reference would be to include the current version of all the frameworks, so that ppl who start out on the package have a choice. The other way around Apache and rails would be like Windows and Internet Explorer. 90% of the ppl won''t go looking around for alternative web frameworks if rails is already installed. This would be kinda unfair for the other frameworks, because some of them look promising, too. As a matter of fact, and I hope the respective authors read this, the only thing that really set rails apart from the other frameworks (like IOWA and Nitro) is that its documentation is awesome and more mature. I hope that the authors of the other frameworks will pick up on that in the future. It will certainly bring them more market share ;) Add to this that the size of a couple of other frameworks (ruby libs) will hardly put a lot of weight on the package as a whole. The binaries of Apache and the DB Servers will eat all the megabytes. Speaking of DB Servers. PostgreSQL 8.0 (still in beta I think) comes as a native Windows version nowadays (or will come soon). It would be *really* nice to have this automatically installed. I myself have been a victim of using MySql only because it was installed at my first ISP (or could easily be installed) under Windows in the first place. Never shopping around for better alternatives. I have since come to regret this when wanting to use fulltext search and transactions with the same table type. PostgreSQL doesn''t have this and other problems and it has an amazing set of other interesting features. It can even be extended with Ruby. Just imagine you would have a native Windows version of PostgreSQL 8.0 + PLRuby (http://moulon.inra.fr/ruby/plruby.html) An example from the page: For example to concatenate 2 rows create the function plruby_test=# CREATE FUNCTION tu(varchar) RETURNS setof record plruby_test-# AS '' plruby_test''# size = PL.column_name(args[0]).size plruby_test''# res = nil plruby_test''# PL::Plan.new("select * from #{args[0]}", plruby_test''# "block" => 50).each do |row| plruby_test''# if res.nil? plruby_test''# res = row.values plruby_test''# else plruby_test''# res.concat row.values plruby_test''# yield res plruby_test''# res = nil plruby_test''# end plruby_test''# end plruby_test''# if res plruby_test''# res.concat Array.new(size) plruby_test''# yield res plruby_test''# end plruby_test''# '' language ''plruby''; CREATE FUNCTION plruby_test=# plruby_test=# select * from tt; a | b ---+---- 1 | 2 3 | 4 5 | 6 7 | 8 9 | 10 (5 rows) plruby_test=# select * from tu(''tt'') as tbl(a int, b int, c int, d int); a | b | c | d ---+----+---+--- 1 | 2 | 3 | 4 5 | 6 | 7 | 8 9 | 10 | | (3 rows) plruby_test=# You love your Ruby? It seems like PostgreSQL is your friend. -- Sascha Ebach
Hi,> > I agree PHP should be part of it. If for nothing else then > > phpmyadmin and maybe > > a comparable tool for sqlite. > > Hmmm... good point!and phpPgAdmin for PostgreSQL users, I think. Cheers. --- Yasuyuki Inoue inoue-W6UanM1vskUTBYAz+LHnZg@public.gmane.org