From: Andreas Bauer
---
src/README.devel | 36 +++++++++++++++++++++++++-----------
1 files changed, 25 insertions(+), 11 deletions(-)
diff --git a/src/README.devel b/src/README.devel
index 25cdf3e..346c652 100644
--- a/src/README.devel
+++ b/src/README.devel
@@ -44,7 +44,9 @@ http://api.rubyonrails.com/classes/Breakpoint.html#M000833
Deployment
------------
-Deploy locations:
+Deploy locations (SUSE specific):
+
+The deploy path is referred to as $DEPLOY_LOCATION in the later sections.
- backend
@@ -70,9 +72,6 @@ Deploy locations:
Prerequisites:
-Your public RSA key has to be in the authorized_keys file of user opensuse on
-all servers (currently only api.opensuse.org).
-
The buildservice uses Switchtower (http://manuals.rubyonrails.com/read/book/17)
for deployment. Before using the deploy scripts, the switchtower gem has to be
installed:
@@ -80,8 +79,16 @@ installed:
%> gem install switchtower
+Customizing your configuration
+
+Switchtower deployment is available for webclient, frontend (API) and common libs.
+In each of the root directories of these parts (below trunk/buildservice/src), there
+is a file config/deploy.rb.template. Change the values in these files to match your
+setup (SUSE developers: use the deploy.rb scripts from internal svn).
+
-Preparing a server for the first deploy:
+
+Preparing a setup for the first deploy:
In the three directories trunk/buildservice/src/(frontend|webclient|current), call:
@@ -91,12 +98,19 @@ In the three directories trunk/buildservice/src/(frontend|webclient|current), ca
Deploying:
-If the frontend database schema has not changed since the last
-deploy, just execute the 'deploy' script in trunk/buildservice/src.
+Call rake deploy in the RAILS_ROOT directory of the part you want to deploy. If your
+forge username is different from the username on your workstation, set the
+environment BS_SVN_USER to your forge username.
+
+Example:
+Deploy the webclient using forge user 'lieschenmueller':
+
+%> cd trunk/buildservice/src/webclient
+%> rake deploy BS_SVN_USER=lieschenmueller
-If the database schema has changed, use ./deploy as usual. After that, ssh to
-buildserviceapi.suse.de and change the database. The schema is in the directory
-/srv/www/opensuse/frontend/current/db.
+If the database schema has changed, ssh to the server running the API database
+after the deploy and update it manually. The update script is located in
+$DEPLOY_LOCATION/current/db/ on the server.
Warning:
The current schema is autogenerated for use with the development database
@@ -106,6 +120,6 @@ system.
After the database is updated, restart the FastCGI processes:
-%> cd /srv/www/opensuse/frontend/current
+%> cd $DEPLOY_LOCATION
%> script/process/reaper -d /srv/www/opensuse/frontend/current/public/dispatch.fcgi
--
1.7.7
--
To unsubscribe, e-mail: obs-commits+unsubscribe@opensuse.org
To contact the owner, e-mail: obs-commits+owner@opensuse.org
