Quick Start
These instructions should get you up and running with Devalot in a few minutes.
We also offer Devalot installation, configuration, and tuning services. See the frequently asked questions section for more information.
Getting The Source
Download a tarball from http://files.noscience.net/pub/devalot/files.
E.g.,wget http://files.noscience.net/pub/devalot/files/devalot-rel-0.1.tar.bz2 tar xvjf devalot-rel-0.1.tar.bz2
You can also get the latest cutting edge (and probably unstable) source from the Git repository.
git clone http://repo.noscience.net/devalot.git
The repository can also be viewed online: http://repo.noscience.net/?p=devalot.git;a=summary
Preparing The Database
Before you begin, make sure you have your database server up and running. Since Devalot uses the Ruby on Rails framework, you can use any database that the ActiveRecord library supports, such as PostgreSQL, MySQL, or even SQLite.
Note: If you’re planning on using SQLite, you might want to read this first.
Using your database administration tools, create a database named ‘devalot’. If you plan on doing development on devalot, you should also create ‘devalot_test’ and ‘devalot_dev’ databases. Once you have the database created, copy the config/database.yml.sample file
in the Devalot source to config/database.yml:
cp config/database.yml.sample config/database.yml
Use your favorite text editor to change the database connection settings to match the settings for the ‘devalot’ database you just created.
Now you can create all the necessary tables, and insert the default data:
env RAILS_ENV=production rake db:migrate env RAILS_ENV=production ruby script/setup
Starting the Web Server
You can start the built-in web server using the following command:
env RAILS_ENV=production ruby script/server
Final Steps
- Point your web browser at http://localhost:3000/account/login
- Login with ‘admin@localhost.local’ as the username and ‘admin_pass’ as the password
- Change the admin password!
- Review the settings in http://localhost:3000/admin
- You can change your site name in the admin area, under “Policies”
- Did you change the admin password?
Updated Fri, Jun 06 by Isaac Foraker
Tags:
Comments:
Geir, good catch.
I'm unable to check out with the URL specified above. Subversion just hangs and doesn't report any errors, I have to kill it with another terminal window. I'm using subversion 1.1.4. Is there a problem with the repository?
Todd, the repository is fine. Can you provide more details about your setup. What operating system are you running on? Can you let svn run until it dies and reports an error message.
Also, I'm not sure if it's a problem, but the repository is managed with Subversion 1.3.x, so I guess that could be a problem.
Hi Peter, I'm using CentOS 4.4. I've followed the rails installation described [http://wiki.rubyonrails.com/rails/pages/Rails+on+CentOS+4.3+with+Apache+and+FastCGI+Simply]
My CentOS 4.4 is a vmware image. Once I'm done creating it, I would like to contribute it to you so that people can easily download and play with devalot. It shows a lot of promise. FYI, it finally started downloading. It just took 10 minutes to start getting files.
I have a VMWare image that is close to production worthy (it may need a few tweaks on the ruby on rails and fast cgi side). Its a CentOS 4.4 distro with Apache, FastCGI, and MySQL. Where would you like it to post it so that you can take a look at it?
Todd, open a ticket and attache whatever files you have.
Hints for windows install:
Set up a system environment variable ... Variable: RAILS_ENV Value: production
In a cmd window switch to your application root directory ... rake db:migrate ruby script/setup
I’m using revision 821 and I’ve noticed that the admin account is not enabled by default in my sqlite3 db after doing the QuickStart Guide, thus not allowing me to log in as described above. Anyone else run into this?
Hey guys
Downloaded your software 'cause it sounds like just what we need but it doesn't work in SQL Server... :(
Unfortunately, the word 'public' must be a reserved word or something...
Do you have any patches for MSSQL? (thought I'd ask before we start digging)
Anyway,hopefully we can try it out soon.
Regards Paul
Have something to say? Login to post a comment.
Geir Gluckstad, Feb 13, 2007
Level 2 (Tourist with 1 point)
See that environment 'production' is assumed in most cases. Got problems running 'rake db:migrate' and 'ruby script/setup' without first doing an 'export RAILS_ENV=production'.
My 2 cents.