Prog, dream, shiny, en

Oupsnow 0.5.0 released

Sat, 13 Mar 2010 00:00:00 +0100

That’s it. After only one month to released Oupsnow 0.4.1, I released the 0.5.0 version. This version
mark adding features and stability on code base.

New features ?

Add filter by closed or not with closed keywords
You can edit a milestone now
You can define one milestone like current. By define the first one created
Add the recover password configuration by your email
Add remember solution when you logged
Add information about number of ticket in search
A logged user can watch a ticket. If user watch ticket he received email
when ticket is update
A user can change his own email.

Like I made each time, my capistrano file to deploy Oupsnow

set :application, "oupsnow"
set :repository,  "git://github.com/shingara/oupsnow.git"
set :domain, "dev.shingara.fr"

# If you aren't deploying to /u/apps/#{application} on the target
# servers (which is the default), you can specify the actual location
# via the :deploy_to variable:
set :deploy_to, "XXXXXXXXX"

# If you aren't using Subversion to manage your source code, specify
# your SCM below:
# set :scm, :subversion
set :scm, :git
set :git_enable_submodules, 1

set :runner, "xxxx"
set :user, "xxxx"
set :use_sudo, false

set :thin_conf, "/etc/thin/#{domain}.yml"

set :rails_env, "production"

role :app, domain
role :web, domain
role :db,  domain, :primary => true

task :update_config, :roles => [:app] do
  run "ln -s #{shared_path}/config/database.yml #{release_path}/config/database.yml"
  run "ln -s #{shared_path}/config/email.yml #{release_path}/config/email.yml"
  run "ln -s #{shared_path}/config/initializers/errornot.rb #{release_path}/config/initializers/errornot.rb"
  run "cd #{release_path} && echo 'GOOGLE_ANALYTICS=\"XXXXXXXX\"' >> config/environment.rb"
end

namespace :deploy do
  task :start, :roles => [:app] do
    run "thin -C #{thin_conf} start"
  end

  task :stop, :roles => [:app] do
    run "thin -C #{thin_conf} stop"
  end

  task :restart, :roles => [:app] do
    run "thin -C #{thin_conf} restart"
  end
end

task :update_db do
  run "cd #{current_path} && RAILS_ENV=#{rails_env} rake db:update"
end

after "deploy:update_code", :update_config
after "deploy:symlink", :update_db

Traduction française

Typo 5.4.0 released

Mon, 21 Dec 2009 00:00:00 +0100

That’s it. A new version of Typo is released. I don’t really participate to this
version, by lack of time and motivation, but I am allways proud to see a new version.

Each release see a new admin, but each time is allways better than previous. So it’s a good thing.

My french blog is update and use this new version with new default design.

My little gift with this released is my capistrano config file to deploy it. It can be useful

set :application, "typo"
set :repository,  "git://github.com/fdv/typo.git"
set :domain, "blog.shingara.fr"

# If you aren't deploying to /u/apps/#{application} on the target
# # servers (which is the default), you can specify the actual location
# # via the :deploy_to variable:
set :deploy_to, "/var/rails/blog-typo"
#
# # If you aren't using Subversion to manage your source code, specify
# # your SCM below:
set :scm, :git

set :runner, "rails"
set :user, "rails"
set :use_sudo, false

set :thin_conf, "/etc/thin/#{domain}.yml"

role :app, domain
role :web, domain
role :db,  domain, :primary => true

task :update_config, :roles => [:app] do
  run "cp -Rf #{shared_path}/config/* #{release_path}/config/"
  run "ln -s #{shared_path}/files #{release_path}/public/files"
end

task :update_gems, :roles => [:app] do
  run "cd #{release_path} && RAILS_ENV=production rake gems:install"
end


after "deploy:update_code", :update_config
after "deploy:update_code", :update_gems


namespace :deploy do
  task :start, :roles => [:app] do
    run "thin -C #{thin_conf} start"
  end

  task :stop, :roles => [:app] do
    run "thin -C #{thin_conf} stop"
  end

  task :restart, :roles => [:app] do
    run "thin -C #{thin_conf} restart"
  end
end

task :clear_cache, :roles => [:app] do
  run "cd #{current_path} && RAILS_ENV=production rake sweep_cache"
  run "cd #{current_path} && RAILS_ENV=production rake tmp:cache:clear"
end

after "deploy:restart", :clear_cache
after "deploy:start", :clear_cache

Traduction française

Oupsnow 0.4.0 released

Tue, 01 Dec 2009 00:00:00 +0100

That’s it. I finally released Oupsnow 0.4.0. This version is a complete refactoring. After a oupsnow version 0.3.0 in Merb/DataMapper, this new
version is with Rails and MongoDB. The server and the backend have changed.

But with the complete changed, there are some new features.

Add filter by state in search ticket
Add possibility to change function of all member by project
Add preview in ticket and ticket updates
Add ticket’s milestone information in ticket show
Add ordering to all column in ticket search

You can download it on rubyforge

If you want try the oupsnow demo version, it’s online. The administrator login/password is : admin@admin.org/oupsnow Have fun.

The code source is hosted on github http://github.com/shingara/oupsnow

You can report any bug about it on my own oupsnow instance

Traduction française

Oupsnow from Merb to Rails

Thu, 19 Nov 2009 00:00:00 +0100

Lately, I decided to migrate Oupsnow, from Merb to Rails.

Just after ending my migration from SQL to MongoDB, I starting a new one but this one much more deep.

Why this migration ?

Rails 3. Since December 2008, almost one year later, Merb is allways freeze. Someone say that community is reviving and it’s true.
I am glad to see that, but Merb is really late now with one year of late. Even Rails don’t really improve in his stable version,
his edge move a lot.

Trying test all new technologies in Ruby, I will play with Rails 3. But no migrating too exists to migrate from Merb to Rails 3.
After a quick test, I see that difference between Rails 2.3.x and Rails 3 is little. So the migration from Rails 2.3.x to Rails 3 can be
more easily.

Like I want release soon as possible a stable version of Oupsnow. I decided to migrate Oupsnow to Rails 2.3.x before upgrade to
Rails 3. And this time, I maybe can release a stable version of Oupsnow compatible with Rails 3.

Oupsnow become a project Rails/MongoMapper and no more a Merb/DataMapper project like before. Any help are welcome.

Traduction française

RabbitMQ doesn’t works with MacOSX ?

Wed, 18 Nov 2009 00:00:00 +0100

A couple of week, I want go on using RabbitMQ, I have a big issue.
With RabbitMQ, you need configure vhost and user. but I can’t connect to rabbitMQ by command rabbitmqctl.
Plan to upgrade my Mac to SnowLeopard I don’t found how fix this problem. RabbitMQ can be wait.

But after my upgrade, I install again RabbitMQ. to use again. But I was allways same issue. After a long search, I
found the cause. The hostname.

What made if your control node rabbitMQ can’t contact the master node ?

The solution is really simple. hostname -s. Add this one in your file /etc/hosts to ip 127.0.0.1.
And now it’s works. Sometimes the solution is so easy.

Traduction française