GitXplorerGitXplorer
h

enterprisebooking

public
2 stars
2 forks
0 issues

Commits

List of commits on branch master.
Unverified
dc21eee38ff6e802af364502a8f7da0264bdb11e

Forgot to add files in previous commit

hhegjon committed 17 years ago
Unverified
21b16b2b6f8c6717a76454f35bf8804c721e010a

Split Person into Profile and CompanyProfile

hhegjon committed 17 years ago
Unverified
abcf884f5290ac53bb45fcca4af034f3bc01be36

Check if code is nil

hhegjon committed 17 years ago
Unverified
d2df17f90e6aa3bf383192ef34badad8b5b73ea4

Refactoring

hhegjon committed 17 years ago
Unverified
31e5d0c95dd1e270959461842bb076260848e434

Add Periodes to Booking

hhegjon committed 17 years ago
Unverified
720f0348495706dcf4cfbc08d3d744c1e04e264a

Comment out failing test :(

hhegjon committed 17 years ago

README

The README file for this repository.

== Welcome to EnterpriseBooking server

Enterprise Booking is client-server-based booking system for large-scale site catering. Its goal is to simplify fast and effective booking, check-in and the overall progress.

== Getting Started

  1. Install Rails.
  2. At the command prompt, start a new instance using the script/server (run with --help for options) command

== Web Servers

By default, EnterpriseBooking will try to use Mongrel and lighttpd if they are installed, otherwise EnterpriseBooking will use WEBrick, the webserver that ships with Ruby. When you run script/server, EnterpriseBooking will check if Mongrel exists, then lighttpd and finally fall back to WEBrick. This ensures that you can always get up and running quickly.

== Console

You can interact with the domain model by starting the console through script/console. Here you'll have all parts of the application configured, just like it is when the application is running. You can inspect domain models, change values, and save to the database. Starting the script without arguments will launch it in the development environment. Passing an argument will specify a different environment, like script/console production.

To reload your controllers and models after launching the console run reload!

== Description of Contents

app Holds all the code that's specific to this particular application.

app/controllers Holds controllers that should be named like weblogs_controller.rb for automated URL mapping. All controllers should descend from ApplicationController which itself descends from ActionController::Base.

app/models Holds models that should be named like post.rb. Most models will descend from ActiveRecord::Base.

config Configuration files for the Rails environment, the routing map, the database, and other dependencies.

db Contains the database schema in schema.rb. db/migrate contains all the sequence of Migrations for your schema.

doc This directory is where your application documentation will be stored when generated using rake doc:app

lib Application specific libraries. Basically, any kind of custom code that doesn't belong under controllers, models, or helpers. This directory is in the load path.

public The directory available for the web server. Contains subdirectories for images, stylesheets, and javascripts. Also contains the dispatchers and the default HTML files. This should be set as the DOCUMENT_ROOT of your web server.

script Helper scripts for automation and generation.

test Unit and functional tests along with fixtures. When using the script/generate scripts, template test files will be generated for you and placed in this directory.

vendor External libraries that the application depends on. Also includes the plugins subdirectory. This directory is in the load path.