Difference between revisions of "User:Rfs/Installing wobble motions"

From FreekiWiki
Jump to navigation Jump to search
m
Line 51: Line 51:
 
Populate the database:
 
Populate the database:
 
  rfs@boq:~/wobble/motions/trunk$ rake db:migrate
 
  rfs@boq:~/wobble/motions/trunk$ rake db:migrate
(in /home/rfs/wobble/motions/trunk)
+
(If you have a dump of the database, you can use that to populate it with real or usable data.
rake aborted!
 
could not connect to server: Connection refused
 
        Is the server running on host "localhost" and accepting
 
        TCP/IP connections on port 5433?
 
 
 
(See full trace by running task with --trace)
 
 
 
''(Hmmm.. that's a problem.)''
 
  
  
Line 76: Line 68:
  
  
Click on a link, which will take you to a log in page. Log in:
+
Click on a link, which will take you to a log in page and log in.
  PGError in LoginController#login
+
 
   
+
Note: One problem I had was my database.yml file was set to look at a custom port for postgresql. Check /etc/services to see where postgresql is listening:
  could not connect to server: Connection refused
+
  rfs@boq:~/wobble/motions/trunk$ grep postgresql /etc/services
Is the server running on host "localhost" and accepting
+
  postgresql      5432/tcp        postgres        # PostgreSQL Database
TCP/IP connections on port 5433?
+
  postgresql      5432/udp        postgres
  
''(OK. That needs fixing too. Probably same problem as above.)''
+
If postgresql is listening on the standard port (5432), you don't need the port: lines in database.yml. If it is listening on a non-standard port, then you need to specify which port that is in database.yml.

Revision as of 17:24, 8 October 2007

Install necessary packages:

sudo aptitude install rails rubygems postgresql-8


Trying to start the server, I got a message that said to do this as well:

sudo gem install -v=1.1.6 rails


Get the application(s) from the svn server:

svn co svn+ssh://dev.freegeek.org/svn/wobble/trunk wobble/trunk

(??? actually I need to get motions which is a sub-project of wobble.)


Check the configuration file for the username and password. (Edit these to suit yourself.)

rfs@boq:~/wobble/motions/trunk$ cat config/database.yml


Create a user for the database:

rfs@boq:~/wobble/motions/trunk$ sudo su - postgres
postgres@boq:~$ createuser USERNAME_GOES_HERE
Shall the new role be a superuser? (y/n) y
CREATE ROLE
postgres@boq:~$ 


Set the user's password:

rfs@boq:~/wobble/motions/trunk$ psql template1
Welcome to psql 8.2.5, the PostgreSQL interactive terminal.

Type:  \copyright for distribution terms
      \h for help with SQL commands
      \? for help with psql commands
      \g or terminate with semicolon to execute query
      \q to quit

template1=# ALTER USER USERNAME_GOES_HERE password 'PUT_THE_PASSWORD_HERE';
ALTER ROLE
template1=# 


Create the databases (empty for now):

rfs@boq:~/wobble/motions/trunk$ createdb motions_test
CREATE DATABASE
rfs@boq:~/wobble/motions/trunk$ createdb motions_development
CREATE DATABASE
rfs@boq:~/wobble/motions/trunk$ createdb motions_prioduction
CREATE DATABASE


Populate the database:

rfs@boq:~/wobble/motions/trunk$ rake db:migrate

(If you have a dump of the database, you can use that to populate it with real or usable data.


Start the server:

rfs@boq:~/wobble/motions/trunk$ ./script/server 
=> Booting WEBrick...
=> Rails application started on http://0.0.0.0:3000
=> Ctrl-C to shutdown server; call with --help for options
[2007-10-08 10:19:56] INFO  WEBrick 1.3.1
[2007-10-08 10:19:56] INFO  ruby 1.8.5 (2006-08-25) [i486-linux]
[2007-10-08 10:19:56] INFO  WEBrick::HTTPServer#start: pid=7392 port=3000


Using a browser, go to:

http://localhost:3000


Click on a link, which will take you to a log in page and log in.

Note: One problem I had was my database.yml file was set to look at a custom port for postgresql. Check /etc/services to see where postgresql is listening:

rfs@boq:~/wobble/motions/trunk$ grep postgresql /etc/services 
postgresql      5432/tcp        postgres        # PostgreSQL Database
postgresql      5432/udp        postgres

If postgresql is listening on the standard port (5432), you don't need the port: lines in database.yml. If it is listening on a non-standard port, then you need to specify which port that is in database.yml.