Metropoli is a flexible and unobstrusive city database engine that can relate to your Rails 3 models.
It is built using Rails Engines and is inspired on Devise, the authentication solution by Plataforma Tecnologia.
The main features of Metropoli are.
- Non obstrusive city database
- Provides easy and flexible way to relate your models to a city, state or country.
- Built-in jquery autocomplete solution with json response.
- Prepared for behaviour extension.
Metropoli is built specifically for Rails 3, therefore it doesn’t work with previous rails versions. Right now it’s not released as a gem yet but you can use it copying the following code in your Gemfile.
gem 'metropoli', :git => 'git://github.com/innku/metropoli.git'
rails generate metropoli:install
Metropoli has 2 different installation options
- —skip-demo : Skips the generation of the example seed files
Metropoli includes a rake task to seed the database based on CSV Files. The files are under the directory “/db/csv” and they are named:
By default the installation will create an example database but you will likely edit this files to fit your needs according to your country.
The csv files are self-explaining, if you want to add a column to any of the database tables, you can add it in the appropriate migration file, add a column in the csv file with the name of the new field as the first line, and the migration will just work.
This rake task will run the migration.
If you should encounter any errors while seeding the database, you can clean the tables up with the following command:
Use it in your models
To start using metropoli you need to generate the migration that will relate your model to the engine. You can do this with the following command.
rails generate metropoli model [city | state | country] [options]
- model is the name of your model
- [city | state | country] is the type of relation you would like to have, you can select either city, state or country
The option —as is useful when you’d like to explicitly name your relation with the engine.
After you run the migration, you need to declare the association in your model.
This declaration will generate the attribute city_name in your model, both reader and writer. If you want to assign a city to your model you can simply assign it as a string. For example, if you had a user model, you might do the following.
@user.city_name = 'Houston'
After that the user will be automatically related to the City. You can be more specific with the assignation like this:
@user.city_name = 'Houston, Tx'
That will also work. This process is also valid for both states and countries.
If you want to explicitly name the relation it will be a similar process. For example if you have a trip with an origin and a destination you might declare it in the model like:
metropoli_for :city, :as => 'origin'
metropoli_for :city, :as => 'destination'
The generated attributes would be origin_name and destination_name. All of the previously mentioned functionality would work in the same way.
Use it in your interface
If you want to use the autocomplete functionality you need to add both jquery and jqueryui to your layout. After that you need to add the script generated in the installation: metropoli.jquery.ui to your layout.
To use it just add one of the following classes to your inputs:
f.text_field :city_name, :class => 'city_autocomplete'
f.text_field :state_name, :class => 'state_autocomplete'
f.text_field :country_name, :class => 'country_autocomplete'
The process of adding explicitly named relations is the same for the name of the attribute but the css class needs one of the above according to the relation type.
There are several ways to customize the gem with the configuration options found in the initializer:
Extend its behaviour
To install the gem
gem install bundler --version '~> 1.0.0'
If you want to add any gems, please note that we are using jewelry. So you need to add it to the Rakefile. And then run rake gemspec
To run the tests
If you want to run the whole suite,
If you want to run a single test file
ruby -Itest test/file.rb
Please note that you do not need to add run any migrations because we are using a in memory database.
To see it working
There is a test app under test/test_app. Inside this app, you need to follow the instructions described at the top of this document.
What we’re doing to it
You can check out what we are doing to the project on:
Copyright © 2010 Innku. http://innku.com