Changes

244 bytes added ,  14:50, 26 April 2011
Line 26: Line 26:  
!scope="row" | Home
 
!scope="row" | Home
 
|{{Code|/srv/gitorious}}
 
|{{Code|/srv/gitorious}}
 +
|-
 +
!scope="row" | Daemon
 +
|{{Code|/etc/init.d/gitorious}}
 
|-
 
|-
 
!scope="row" | Logs
 
!scope="row" | Logs
 
|{{Code|/srv/gitorious/app/log}}
 
|{{Code|/srv/gitorious/app/log}}
 
|-
 
|-
!scope="row" | Main service
+
!scope="row" | Config
|{{Code|gitorious-all}}
+
|
 +
{{Code|/srv/gitorious/app/config/database.yml}}<br>
 +
{{Code|/srv/gitorious/app/config/gitorious.yml}}<br>
 +
{{Code|/etc/cron.daily/gitorious}}<br>
 +
{{Code|/etc/logrotate.d/gitorious}}<br>
 +
{{Code|/etc/httpd/conf.d/git.sugarlabs.org.conf}}
 +
|-
 +
!scope="row" | SSL certs
 +
|
 +
{{Code|/etc/ssl/private/git.sugarlabs.org.key}}<br>
 +
{{Code|/etc/ssl/certs/git.sugarlabs.org.pem}}
 +
|-
 +
!scope="row" | Sources
 +
| http://gitorious.org/~alsroot/sugarlabs-org
 
|-
 
|-
 
|}
 
|}
   −
Looks like Gitorious Web UI leaks, it might grow from 200M to 1.2G during a week. Had to restart {{Code|gitorious-webui}} from daily cron.
+
=== Database tips ===
 
  −
=== Database tweaks ===
      
To make runtime changes in Gitorious database, follow regular Rails workflow - run {{Code|scripts/console}}:
 
To make runtime changes in Gitorious database, follow regular Rails workflow - run {{Code|scripts/console}}:
Line 59: Line 73:  
  # destroy object and all its dependencies
 
  # destroy object and all its dependencies
 
  user.destroy
 
  user.destroy
 
+
=== Tips ===
  −
 
   
  # reset user password
 
  # reset user password
 
  user = User.find_by_email("user")
 
  user = User.find_by_email("user")
Line 92: Line 104:  
  repo.name = "sat-solver"
 
  repo.name = "sat-solver"
 
  repo.save!
 
  repo.save!
  −
=== Sources ===
  −
  −
* http://gitorious.org/~alsroot/sugarlabs-org
      
== Upgrade notes ==
 
== Upgrade notes ==
    
Upgrade will be triggered on every puppet session (if there is such need), vcs repository will be rebased to the HEAD commit with all related changes like database migration.
 
Upgrade will be triggered on every puppet session (if there is such need), vcs repository will be rebased to the HEAD commit with all related changes like database migration.