Scoot is a project mainly written in RUBY and SHELL, based on the AGPL-3.0 license.
Bigger. Better. Awesome. "Fork" of Gitorious
Please see HACKING
Please see the LICENSE file
Also see the files in the doc/ folder, they contain further detailed information about setting up the application for specific linux distributions such as CenOS and Ubuntu/Debian
===========================================================================
Installation to a production environment -- a partial walkthrough.
===========================================================================
=== Make ready
You may want to make separate directories, away from everything, to hold the site code and the git repository respectively. In production, you'll be setting up a special user account too, but don't worry about that yet.
For this intro we're going to use, as examples,
All of these can be adjusted to suit: specifically, dirs within your home directory are fine, and (though MySQL has the best development coverage), the website code should be free of mysql-isms/quirks.
=== Dependencies
First, install each of these Libraries/applications:
Next, get the gitorious code itself:
Install each of these Ruby libraries/bindings/gems:
ruby-iconv
chronic rmagick geoip ultrasphinx ruby-openid
=== Database
First we need a database. Use the mysql command line app, or phpMyAdmin, or whatever to create first a user. Referring to http://www-css.fnal.gov/dsg/external/freeware/mysqlAdmin.html:
CREATE USER 'git'@'localhost' IDENTIFIED BY 'awesomepassword';
GRANT ALL PRIVILEGES ON `git%. * TO 'git'@'localhost'; FLUSH PRIVILEGES; CREATE DATABASEgit_devDEFAULT CHARACTER SET utf8 COLLATE utf8_bin; CREATE DATABASEgit_testDEFAULT CHARACTER SET utf8 COLLATE utf8_bin; CREATE DATABASEgit_prod` DEFAULT CHARACTER SET utf8 COLLATE utf8_bin;
If you haven't set a password for the root user, now's a good time for that, too.
Edit database.yml to reflect your local database connection. This is a standard Ruby on Rails config file, not specific to gitorious -- if you have questions here they're answered on the web, or consult the rails IRC channel. (One hint: NO TABS AT ALL in a .yml file.) Our example:
development: adapter: mysql username: git password: awesome_password host: localhost database: git_dev
test: adapter: mysql username: git password: awesome_password host: localhost database: git_test
production: adapter: mysql username: git password: awesome_password host: localhost database: git_prod
Use rake to create the databases, migrate each, and run the tests:
rake db:create:all for RAILS_ENV in development test production ; do rake db:migrate done rake test
FTW!
=== Gitorious config
Copy the config/gitorious.sample.yml file to config/gitorious.yml
Create a directory to hold project files
Make a long, complicated string. You can run "apg -m 64", or if you lack 'apg'
dd if=/dev/random count=1 | md5sum ,
and put that on the 'cookie_secret' line (replacing the 'ssssht').
Here's an example gitorious.yml (omitting comments) for local testing:
cookie_secret: 26ee61bc4d6aa9870ab48d118a55e6ebcd11011dd6b61aa33536c024853c48d4e7c3d672aa57859 repository_base_path: "/gitorious/repositories" extra_html_head_data: system_message: gitorious_client_port: 3000 gitorious_client_host: localhost gitorious_host: localhost # gitorious.org gitorious_user: gitslave
=== Get Sphinx going for RAILS_ENV in development test production ; do RAILS_ENV=$RAILS_ENV rake ultrasphinx:configure RAILS_ENV=$RAILS_ENV rake ultrasphinx:index done RAILS_ENV=production rake ultrasphinx:daemon:start &
=== Tweak environment
In environment.rb, uncomment config.action_controller.session -- choose a new session key string and generate your own secret key using something like (uptime; date) |sha1sum
If you haven't set up your mailer, production mode will fail on login. Set config.action_mailer.delivery_method = :test for immediate gratification.
=== Run the server
From the gitorious directory,
It should start up on port 3000, listening only to local connections. Ue "ssh -L 3000:127.0.0.1:3000 -N [email protected]" for testing.
You can now visit the site, sign up with your OpenID, put in your ssh key, and poke around! Once you get bored, make a test repository, wonder why nothing is there yet, and then....
=== Hand-start the task_performer
Key adoption, repo generation and other tasks are handled by the 'task_performer' script, which must be run periodically or on demand. Run the script/task_performer and let it create the repository for you.
Push something to that repository (cd to a git repository with commits and do "git push path/to/the/bare/repository/you/just/created master"). The actual (bare) repos live in repository_base_path/#{project.slug}/#{repository.name}.git Ex: the fubar project's mainline fork sits in a directory called
/gitorious/repositories/fubar/mainline/fubar.gitThis will be a 'bare' git repo -- you won't see files in it.
=== Button up
In production, you'll want to have a limited-privileges user to run the git processes, just as you do for your webserver
Make the tree invisible to any other non-root user; make the tree read-only by that user; but grant write access to the /tmp and /public/cache directories.
Consider setting up the standard (lighttpd|nginx|apache) frontend <=> mongrel backend if you see traffic.
=== More Help
=== Gotchas
Gitorious will add a 'forced command' to your ~/.ssh/authorized_keys file for the target host: if you start finding ssh oddities suspect this first. Don't log out until you've ensured you can still log in remotely.