Leandro Dorileo

You may want to migrante a rails database from a given dbms to another.

Perhaps you started configuring a third-party product built with rails, after sometime you discovered you’ve configured everything and now want to set it up for production environment but, you played initially with sqlite and your production environment runs with mysql. Well you got the idea.

The idea is to use yaml_db, dump from production, configure you test profile env. and load it into. yaml_db is simple plugin, it’s git repo is here: git://github.com/adamwiggins/yaml_db.git

Dumping:

rake db:dump RAILS_ENV=production

Loading:

rake db:load RAILS_ENV=test

Here you find a tutorial teaching step-by-step.

Today I finally managed to finish an old task on my job. Our application runs on about 13-14 different clients and we have to manage some particularities, some custom settings and business components.

It`s a web application mostly written in java(j2ee old things). We used to configure and build it with a collection of ant scripts. With some migrations in mind I realized I should start by migrating the whole thing to a different build platform, and maven seemed to be the best option.

Well, after some tests and 2 new extra plugins written I finally completed the so desired task, now It`s time to manage the next migrations to make our life better.

PS: besides the development and team leading I do manage a big range of servers.

There`s a getpass module that takes care about currently logged user.

import getpass
print getpass.getuser()

getuser() will return of the user.here you can read more about.

Sometimes we need to know(or are curious about) the files installed on you system by a specific package. On Debian systens we do:

dpkg -L <package name>

But for Fedora we can`t find the same feature by default, it`s needed an additional package to help on it, lets see:

yum install yum-utils

yum-utils brings some utilities to help manage installed packages, to accomplish our initial goals we ought use repoquery:

repoquery --list <package name>

I found these photos on flickr, people hacking coreboot. Coreboot Summit - Denver, 2008.

My table arrangement was inspired by some photos from this set. A cut basket with motherboard over it and the power supplier under. Of course my setup is a bit more organized than the the people`s in Denver(well it was a Summit).

ps: this is also a “note to myself” since I may want to show these photos to someone else;

If you want to change your remote repository to point to some arbitrary commit you cold do the following:

1

git push -f origin sha1:branchname

But be careful, you may break someone else`s repository in the case it has being fetched or cloned by someone.

Many people has bloged and written about launchpad release, I would like to be part of the crowd.

Canonical released launchpad source code.

now back to work

Well, if you`re using display:table you certainly will face some day a situation where you need to verify/test some attribute in the current register to show or not something(maybe a different situation but you need to verify something).

The fact is, display:table will set an attribute in the PageContext, this attribute name will be based on uid or id(the main difference between uid and id is backward compatibility).

With that(say) you`ve set the id attribute of display:table to row. Verifying an attribute in the current row is as easy as using the #attr.row.

For example:

   <display:table id="row" ...
      <s:if test="#attr.row.you_attribute == 12">
      [....]

That`s it, best luck.