In my .emacs I was loading the subversion plugin.
(require 'psvn)
Unfortunately on systems that don’t have the subversion plugin Emacs would barf on this line and stop loading the rest of the .emacs file.
Fortunately someone else had asked a similar question, alternative to (require …), on gnu.emacs.help.
Based on that thread I updated my .emacs with this code.
(condition-case nil (require 'psvn) (error (message "Subversion plugin unavailable, skipping load ...")))
Whenever I start my bash shell I get this annoying message.
Your group is currently “mkgroup”. This indicates that
the /etc/group (and possibly /etc/passwd) files should be rebuilt.
See the man pages for mkpasswd and mkgroup then, for example, run
mkpasswd -l [-d] > /etc/passwd
mkgroup -l [-d] > /etc/group
Note that the -d switch is necessary for domain users.
I tried doing what the documentation but I still kept getting that message. I then tried one of the suggestions in the comments of this post, Cygwin users and groups « sinewalker.
$ mkpasswd -l -p /home/ -c > /etc/passwd
$ mkgroup -l -c> /etc/group
I then got this message.
Copying skeleton files.
These files are for the user to personalise
their cygwin experience.These will never be overwritten.
`./.bashrc’ -> `/home/fkim//.bashrc’
`./.bash_profile’ -> `/home/fkim//.bash_profile’
`./.inputrc’ -> `/home/fkim//.inputrc’
Your group name is currently “mkgroup_l_d”. This indicates that not
all domain users and groups are listed in the /etc/passwd and
/etc/group files.
See the man pages for mkpasswd and mkgroup then, for example, run
mkpasswd -l -d > /etc/passwd
mkgroup -l -d > /etc/groupThis message is only displayed once (unless you recreate /etc/group)
and can be safely ignored.
I am not sure what it means but it was only displayed once. Now that I am not seeing it anymore I’m happy. 🙂
Today I took the plunge and installed Rails 2.0.2. Notes on the Rails 2.0 release can be found here.
Here are the steps I took.
gem update --systemgem install rails -v 2.0.2gem install mysqlrails prayer -d mysqlcd prayerruby script/plugin install http://svn.techno-weenie.net/projects/plugins/restful_authentication/ruby script/generate scaffold Prayer title:string body:text
--include-activation flag is to create the mailers for activation and signup notification.ruby script/generate authenticated user sessions --include-activationrake db:migrateapp/models/user_mailer.rb, replacing the place holders with constants which you can configure with different values for different environments using config/environments/development.rb, config/environments/production.rb.ruby script/generate scaffold Role rolename:stringruby script/generate model PermissionMuch of this post is based on this excellent post, Restful Authentication with all the bells and whistles. At this point I did not continue with much of the tutorial, especially with parts like password forgotten, separate account controller, etc.
When I run rake db:migrate I get this error at the end.
Error in my_thread_global_end(): 1 threads didn't exit
I pinned it down to this code in one of my migration files.
# create admin user user = User.new user.login = 'admin' user.password = 'password' user.save(false)
If I don’t run user.save(false) I don’t get the error. I am not sure why, the user does get saved properly to the database.
I saw this post on the MySQL forums that seemed to indicate it was an issue with libmySQL.dll. So I upgraded my MySQL instance from 5.0.27 to 5.0.51a. Of course this did not go smoothly, I got this error when trying to reconfigure the MySQL server instance “MySQL service could not be started error 0”. Fortunately another post on the MySQL forums, Could not start service : Error 2003, solved this problem for me. I just had to remove the following files from the mysql/data directory.
Unfortunately when I then did a rake db:migrate I saw this error.
Mysql::Error: Table 'prayer.schema_info' doesn't exist: SELECT version FROM schema_info
After deleting and recreating the database I was finally able to run rake db:migrate. Unfortunately I still got the same error that inspired this post.
Googling some more I saw a MySQL bug report, MySQL Bugs: #25621: Error in my_thread_global_end(): 1 threads didn’t exit. Apparently this is a client side issue and I think I can safely ignore it though it is quite annoying.
Strictly speaking, this is not MySQL bug. This is a client bug – a client application (PHP, probably) linked with libmysqlclient calls my_thread_init() but does not call my_thread_end() as appropriate (doesn’t call at all or calls too late). MySQL client library detects this and issues a warning.
On the other hand, we can just remove the check and let buggy applications to fail some other way. Not calling my_thread_end() is a guaranteed memory leak. Calling it too late could easily crash the application.
This site, FreeConference, allows you to do free conference calling. I just did a conference call with a client and it worked well. I haven’t tried setting one up but free is free. 🙂
I tried to update the restful_authentication plugin by doing this.
$ ruby script/plugin update restful_authentication
Unfortunately it didn’t do anything.
I know I don’t have the latest version because in another project I pulled down the latest restful_authentication code and it was different.
To get around this I forced an install with the latest code.
$ ruby script/plugin install -x \ http://svn.techno-weenie.net/projects/plugins/restful_authentication/
Fortunately I received an answer about this on the rails mailing list. Apparently update only works if the plugin is in svn:externals. To do this you would install it with the -x flag (see list of flags by doing ruby script/plugin install -h’).
However if you try this with the restful_authentication plugin you’ll see this.
$ ruby script/plugin install -f \ http://svn.techno-weenie.net/projects/plugins/restful_authentication/ Cannot install using externals because this project is not under subversion.
Previously I talked about configuring a production Ruby on Rails applications using a Mongrel cluster with an Apache front end / load balancer. Now though a new Apache module was released called mod_rails which obviates the need for a Mongrel cluster. Seems promising, both for simplicity of installation and performance.
As mentioned in my post, Configuring Apache to work with a Mongrel Cluster, you need an Apache installation with mod_rewrite and mod_proxy_balancer. Unfortunately on the Red Hat installation I was using the default installation is Apache 2.0 which does not have mod_proxy_balancer. When I tried to upgrade it using up2date I got some errors that seemed to indicate this install was not properly registered. I then tried using the Apache 2.2 install done by the tech guy but this install did not have the modules I needed.
Therefore it was time for me to do the install by myself. Fortunately it was not hard with the help of this article, Building Apache 2.2 plus the manual.
Here is what I did.
$ wget http://apache.mirror99.com/httpd/httpd-2.2.8.tar.gz
$ tar xvfz httpd-2.2.8.tar.gz
$ cd httpd-2.2.8
$ ./configure --enable-rewrite=shared --enable-proxy=shared \
--enable-proxy_balancer=shared --enable-proxy_http=shared
$ make
$ sudo make install
$ sudo /usr/local/apache2/bin/apachectl start
Previously I wrote about Configuring Capistrano and Mongrel. Now we are going to configure Apache to work with the Mongrel cluster.
For this article I used the chapter Setting Up A Development Environment in Agile Web Development with Rails, version 2.0, plus this article.
Capistrano working together with Mongrel allows you to deploy and restart Mongrel clusters quite nicely.
Configure Apache proxy balancer
Apache has a mod_proxy_balancer module which must be enabled. Once this is done you can add the following to the end of conf/httpd.conf or if you are on Red Hat Linux you can put the proxy balancing section in /etc/httpd/conf.d/myapp.proxy_cluster.conf and the virtual host section in /etc/httpd/conf.d/myapp.conf.
<Proxy balancer://mongrel_cluster> BalancerMember http://127.0.0.1:8000 BalancerMember http://127.0.0.1:8001 BalancerMember http://127.0.0.1:8002 </Proxy> <VirtualHost *:80> Include conf/myapp.common (or Include conf.d/myapp.common) ErrorLog logs/myapp_errors_log CustomLog logs/myapp_log combined </VirtualHost>
Configure Apache Virtual Host
Next you configure the virtual host that represents the Ruby on Rails application in the custom file conf/myapp.common or if you are on Red Hat Linux in /etc/httpd/conf.d/myapp.common.
ServerName myapp.com
DocumentRoot /usr/local/rails/myapp/current/public
<Directory "/usr/local/rails/myapp/current/public">
Options FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all
</Directory>
RewriteEngine On
# Uncomment for rewrite debugging
#RewriteLog logs/myapp_rewrite_log
#RewriteLogLevel 9
# Check for maintenance file and redirect all requests
RewriteCond %{DOCUMENT_ROOT}/system/maintenance.html -f
RewriteCond %{SCRIPT_FILENAME} !maintenance.html
RewriteRule ^.*$ /system/maintenance.html [L]
# Rewrite index to check for static
RewriteRule ^/$ /index.html [QSA]
# Rewrite to check for Rails cached page
RewriteRule ^([^.]+)$ $1.html [QSA]
# Redirect all non-static requests to cluster
RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
RewriteRule ^/(.*)$ balancer://mongrel_cluster%{REQUEST_URI} [P,QSA,L]
Restart Apache
$ sudo /usr/local/apache2/bin/httpd -k restart
or
$ sudo /etc/init.d/httpd restart
I was wondering what the difference was between require and require_dependency.
According to this post in comp.lang.ruby the difference is not significant but interesting. Looks like I’ll be using require_dependency from now on.
require loads a file (shared object or ruby source) once from the load path.
require_dependency isn’t a ruby core feature, it’s part of rails. It remembers the given file and loads it on each new server request (like load “path/file.rb” does), if development mode is enabled:
http://wiki.rubyonrails.com/rails/pages/RequireDependency
—
Florian Frank