install your gems

bundle install

get the development database in place

rake db:automigrate db:seed

start GWT development console (starts also rails server on port 8888 along the way)

gwt run

just start the rails server (unless you compiled the javascript no GUI code exists)

rails s

all development users have an empty password. the username can look like this

• root
• manager[test]

or in general

{GROUP}[{DOMAIN1},{DOMAIN2}]

the {GROUP} is the only group the user belongs to.

gwt compile --env=production

production will different version for different User-Agents but with env=developement that will be an all-browser version (bigger in size and less optmizied). all possible optimizations are turned on for prodcution as well.

now you can again run

rails s

with the GUI popping up on http://localhost:3000

there external resources from ixtlan-users (or any other rest service with the same API). quasi static means that the do not change often - i.e. a few new entries per month.

from ixtlan-users

• User
• Domain

from http://github.com/mkristian/ixtlan-translations

• Locale
• Ixtlan::Gettext::TranslationKey
• Ixtlan::Gettext::Translation

to update them there is a rake tasks

rake update:users
rake update:translations

or both in one go (not possible with development)

rake update

update these resources wth a cron job helps keeping the local data in sync and reducing the realtime dependency when running the application.

for development the db/seed.rb provides all needed data to start. but you always can update them from http://github.com/mkristian/ixtlan-users by:

cd ../ixtlan-users
rails s

in another terminal

cd ../ixtlan-rideboards
rake update:users

or the data from from http://github.com/mkristian/ixtlan-translations by:

cd ../ixtlan-translations
rails s

in another terminal

cd ../ixtlan-rideboards
rake update:translations

cd ../ixtlan-users
rails s

in another terminal start you application with

cd ../ixtlan-rideboards
SSO=true gwt run

for the password just use password forgotten and look out for the email text in the ixtlan-users console. there you will find a new password :)

copy the config/password.yml.example to config/password.yml and feed the real values in it. the password.yml should not be part of a public git repo.

this config file is used to setup the rest resource in config/initializers/remote_servers.rb

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Added some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

enjoy :)