Close and Go BackBack to Viget

Projects

Tyrant

Tyrant is a "meta" Rails application designed to run other Rails applications. It was born out of our need to have non-developers work alongside us without requiring a full Rails stack running on their local machines.

Ideally, Tyrant runs (via mongrel) on a development server with multiple user directories that contain SVN working directories with Rails applications. Upon startup, these applications are listed in a user's dashboard and Tyrant provides the interface to start and stop each one. The configuration settings dictate the available port range, and as a new application is started it will grab the next one available.

Current Features

  • User-configurable settings (including ports and rails application dir)
  • Basic user management
  • Basic mongrel management (start / stop)

Future Additions

  • LDAP integration
  • Limiting number of apps a user can run
  • Basic log viewing
  • Database bootstrapping

Quick Installation

  • $ svn co http://svn.extendviget.com/tyrant/trunk tyrant
  • $ mysqladmin create tyrant_development
  • $ cd tyrant
  • $ rake vl:db_load
  • $ ./script/server

This will set up the database with some sample accounts but no settings. Navigate to http://localhost:3000 to configure your personal settings. Now, your users can log in and start accessing their Rails applications.

More documentation to come, in the meantime check out some of the current ScreenShots.

We're the Developers

at Viget Labs. We write about web development trends, tips, best practices, industry events, and our projects — all with an emphasis on Ruby on Rails.

Recent Comments

For translating strings you can use Rails I18n backend instead of using inflectors.

The `typus_human_name` is a patch to fix a problem in `human_name` [1].

[1] https://rails.lighthouseapp.com/projects/8994/tickets/2120-humanize-and-human_name-dont-separate-words

Contact Us

Have any questions, comments, ideas, or secrets to share? Let us know.


Sorry, you need to have Javascript enabled to use this form. (Don't blame us, blame the spammers!) If you'd like to contact us, please visit our Contact page.