mvhub-dev team mailing list archive
-
mvhub-dev team
-
Mailing list archive
-
Message #00089
[Merge] lp:~omacneil/mvhub/improve_laptop_setup into lp:mvhub
Dan MacNeil has proposed merging lp:~omacneil/mvhub/improve_laptop_setup into lp:mvhub.
Requested reviews:
mvhub-dev (mvhub-dev)
slight doc tweaks for non-brave setup
--
https://code.launchpad.net/~omacneil/mvhub/improve_laptop_setup/+merge/23595
Your team mvhub-dev is subscribed to branch lp:mvhub.
=== modified file 'app-mvhub/doc/checklists/install_mvhub.txt'
--- app-mvhub/doc/checklists/install_mvhub.txt 2010-02-03 19:36:09 +0000
+++ app-mvhub/doc/checklists/install_mvhub.txt 2010-04-17 00:20:29 +0000
@@ -7,117 +7,84 @@
# not assume CSL enviroment.
___ Assumptions
-
- ___ $USER is username of developer
- ___ MVHub to be setup on localhost only
- ___ Password for MVHub admin interface should be 'test'
- ___ Database passwords should be 'test'
+
+ ___ $USER is username of developer
+ ___ MVHub to be setup on localhost only
+ ___ Password for MVHub admin interface should be 'test'
+ ___ Database passwords should be 'test'
___ Installation Prerequisites
___ Be root on Debian or Ubuntu machine you are installing to
___ Debian 5.0 (Lenny) and newer or Ubuntu 8.04 (Hardy) and newer
- # Debian Etch can't connect to launchpad
- # You won't be able to use bzr to get
- # our code with a stock Debian Etch.
+ # Debian Etch can't connect to launchpad
+ # You won't be able to use bzr to get
+ # our code with a stock Debian Etch.
- # If you use Etch, you will need a backport of bzr.
- # We have had reports that this is doable
- # but haven't tested this ourselves.
+ # If you use Etch, you will need a backport of bzr.
+ # We have had reports that this is doable
+ # but haven't tested this ourselves.
___ Development Requirement
- ___ The /etc/mv_aliases MUST BE part of your environment
- # See /var/www/mvhub/$USER/link-to-live-code/README after
- # installation for more details
+ ___ The /etc/mv_aliases MUST BE part of your environment
+ # See /var/www/mvhub/$USER/link-to-live-code/README after
+ # installation for more details
___ Initial Steps
# NOTE: $USER is your username. It will already be set by bash as
# an enviroment variable, except in very strange cases.
-
- ___ Create variables commonly used during installation
- export BASE_DIR=/var/www/mvhub/$USER/
-
- ___ Create the /var/www/mvhub/$USER directory structure.
- sudo mkdir -p /var/www/mvhub/$USER
-
- ___ Create the following subdirectories within /var/www/mvhub/$USER:
- cd $BASE_DIR
-
- sudo mkdir conf
- sudo mkdir log
- sudo mkdir log/mvh
- sudo mkdir log/nsp
- sudo mkdir source-code
- sudo mkdir cover_db
- sudo mkdir tmp
- sudo mkdir reports
-
- ___ Set ownership / permissions of folder structure
-
- sudo chown $USER:$USER $BASE_DIR -R
-
- chmod g=rwx,o=rx -R /var/www/mvhub/$USER/cover_db/
- ___ Install Bazaar:
- sudo aptitude install bzr
-
+
___ Get our source code from Launchpad version control.
- cd $BASE_DIR/source-code
-
- # Grab the active development branch of mvhub and name it mvhub-01
- bzr branch lp:mvhub mvhub-01
-
-___ Create symbolic link so Apache can find the source code.
-
- cd $BASE_DIR
-
- ln -s /var/www/mvhub/$USER/source-code/mvhub-01 link-to-live-code
+
+ # Grab the active development branch of mvhub and name it mvhub-01
+ bzr branch lp:mvhub mvhub-01
___Install needed debian packages
- # Change into MVHub root directory
- cd link-to-live-code
-
- # Run test to check what is missing
- app-mvhub/t/debian_packages_installed.t
+ # Change into MVHub root directory
+ cd mvhub-01
+
+ # Run test to check what is missing
+ app-mvhub/t/debian_packages_installed.t
# Install what test says is missing
- sudo aptitude install <PACKAGES>
-
- # Accept all defaults for any interactive dialogs that appear
- # during package installation.
+ sudo aptitude install <PACKAGES>
+
+ # Accept all defaults for any interactive dialogs that appear
+ # during package installation.
___ Install needed cpan modules
- sudo cpan YAML
- sudo cpan CPAN::SQLite
- sudo cpan CPAN
-
- # OPTIONAL: Save yourself lots of time
- # by having CPAN auto-accept common
- # prompts that you would say 'y' to.
-
- $EDITOR /etc/perl/CPAN/Config.pm
- # change:
- 'prerequisites_policy' => q[ask],
- 'build_requires_install_policy' => q[ask/yes],
- 'connect_to_internet_ok' => q[1],
+ sudo cpan YAML
+ sudo cpan CPAN::SQLite
+ sudo cpan CPAN
+
+ # OPTIONAL: Save yourself lots of time
+ # by having CPAN auto-accept common
+ # prompts that you would say 'y' to.
+
+ $EDITOR /etc/perl/CPAN/Config.pm
+ # change:
+ 'prerequisites_policy' => q[ask],
+ 'build_requires_install_policy' => q[ask/yes],
+ 'connect_to_internet_ok' => q[1],
- # to:
- 'prerequisites_policy' => q[follow],
- 'build_requires_install_policy' => q[yes],
- 'connect_to_internet_ok' => q[0],
-
- # Install CPAN modules defined in MVHub bundle
-
- cd $BASE_DIR/link-to-live-code/lib-mvhub/lib/
- perl -MCPAN -e 'install Bundle::MVHub'
-
- # check to see all cpan modules installed
+ # to:
+ 'prerequisites_policy' => q[follow],
+ 'build_requires_install_policy' => q[yes],
+ 'connect_to_internet_ok' => q[0],
+
+ # Install CPAN modules defined in MVHub bundle
+
+ cd $BASE_DIR/link-to-live-code/lib-mvhub/lib/
+ perl -MCPAN -e 'install Bundle::MVHub'
+
+ # check to see all cpan modules installed
- cd $BASE_DIR/link-to-live-code/
-
+ cd $BASE_DIR/link-to-live-code/
+
grep :: lib-mvhub/Build.PL \
| cut -d '=' -f1 \
| egrep -v '\#|use|\$' \
@@ -125,25 +92,32 @@
| xargs -i perl -e "use {};" 2>&1\
| grep "Can.t locate" \
| cut -d '.' -f1
-
- # No output means success. If you recieve 'Can't locate'
- # errors, install the offending modules with:
- # sudo cpan Module::Name
-
+
+ # No output means success. If you recieve 'Can't locate'
+ # errors, install the offending modules with:
+ # sudo cpan Module::Name
+
+___ Create symbolic link so Apache can find the source code.
+
+ cd $BASE_DIR
+
+ ln -s /var/www/mvhub/$USER/source-code/mvhub-01 link-to-live-code
+
+
___ Configure apache
- sudo a2enmod macro
- sudo a2enmod include
- sudo apache2ctl restart
+ sudo a2enmod macro
+ sudo a2enmod include
+ sudo apache2ctl restart
- # add our apache configuration file
- sudo cp app-mvhub/setup/etc/apache2/sites-available/mvhub.conf \
+ # add our apache configuration file
+ sudo cp app-mvhub/setup/etc/apache2/sites-available/mvhub.conf \
/etc/apache2/sites-available/mvhub3.conf
-
- # enable our config
- # don't reload apache2 yet
- sudo a2ensite mvhub3.conf
-
+
+ # enable our config
+ # don't reload apache2 yet
+ sudo a2ensite mvhub3.conf
+
___ configure apache with test host names
# change into apache directory
@@ -167,30 +141,30 @@
sudo su -c "echo 127.0.0.1 nsp.$USER.localhost >> /etc/hosts"
___ setup apache basic auth
-
- sudo htpasswd -cb $BASE_DIR/conf/auth_apache_users test test
- sudo chown $USER:$USER $BASE_DIR/conf/auth_apache_users
+
+ sudo htpasswd -cb $BASE_DIR/conf/auth_apache_users test test
+ sudo chown $USER:$USER $BASE_DIR/conf/auth_apache_users
___ restart apache
- sudo /etc/init.d/apache2 reload
+ sudo /etc/init.d/apache2 reload
___ Add cron job to remove mvhub session files
- sudo cp app-mvhub/setup/etc/cron.daily/clean_slash_tmp_for_mvhub /etc/cron.daily/
-
+ sudo cp app-mvhub/setup/etc/cron.daily/clean_slash_tmp_for_mvhub /etc/cron.daily/
+
___ Add convenience
-
- # Adds 'cdw' and 'cdws' aliases, for quick cd into link-to-live-code
- # and source-code directories, respectively.
- sudo cp $BASE_DIR/link-to-live-code/app-mvhub/project-tools/mv_aliases /etc/
- sudo su -c "echo source /etc/mv_aliases >> /etc/bash.bashrc"
+
+ # Adds 'cdw' and 'cdws' aliases, for quick cd into link-to-live-code
+ # and source-code directories, respectively.
+ sudo cp $BASE_DIR/link-to-live-code/app-mvhub/project-tools/mv_aliases /etc/
+ sudo su -c "echo source /etc/mv_aliases >> /etc/bash.bashrc"
- # Command to make it easy for apache to switch branches
- sudo cp $BASE_DIR/link-to-live-code/app-mvhub/project-tools/bin/mv_set_active /usr/local/bin/
-
- # Create sym link in user's home dir to MVHub code
- sudo ln -s $BASE_DIR /home/$USER/mvhub-project
-
+ # Command to make it easy for apache to switch branches
+ sudo cp $BASE_DIR/link-to-live-code/app-mvhub/project-tools/bin/mv_set_active /usr/local/bin/
+
+ # Create sym link in user's home dir to MVHub code
+ sudo ln -s $BASE_DIR /home/$USER/mvhub-project
+
___ create database(s) and database user
# add database user
@@ -220,34 +194,34 @@
grep port /etc/postgresqql/$n.n/main/postgresql.conf
# if it is not either:
- # adjust either the mvhub conf file
+ # adjust either the mvhub conf file
# or:
# remove older versions of the postgresql db
# and change port in postgresql.conf for version
# you want
# also be sure to uncomment:
- postgresql.conf: listen_addresses = 'localhost'
+ postgresql.conf: listen_addresses = 'localhost'
___ load data
cd $BASE_DIR/link-to-live-code/app-mvhub/project-tools/
- psql -h localhost -U $USER -d $USER.mvh -f test_mvh_db.sql > /dev/null
+ psql -h localhost -U $USER -d $USER.mvh -f test_mvh_db.sql > /dev/null
psql -h localhost -U $USER -d $USER.nsp -f test_nsp_db.sql > /dev/null
- # You will get many errors stating that different tables, functions,
- # and views don't exist. This is normal, and can be disregarded.
+ # You will get many errors stating that different tables, functions,
+ # and views don't exist. This is normal, and can be disregarded.
___ copy conf templates
- cd $BASE_DIR
-
- sudo cp link-to-live-code/app-mvhub/project-tools/templates/template.conf $BASE_DIR/conf/nsp.conf
- sudo cp link-to-live-code/app-mvhub/project-tools/templates/template.conf $BASE_DIR/conf/mvh.conf
+ cd $BASE_DIR
+
+ sudo cp link-to-live-code/app-mvhub/project-tools/templates/template.conf $BASE_DIR/conf/nsp.conf
+ sudo cp link-to-live-code/app-mvhub/project-tools/templates/template.conf $BASE_DIR/conf/mvh.conf
- sudo chown $USER.$USER $BASE_DIR/conf/ -R
- sudo chmod u=rw,g=rw,o= $BASE_DIR/conf -R
- sudo chmod u=rwx,g=rwxs,o= $BASE_DIR/conf
+ sudo chown $USER.$USER $BASE_DIR/conf/ -R
+ sudo chmod u=rw,g=rw,o= $BASE_DIR/conf -R
+ sudo chmod u=rwx,g=rwxs,o= $BASE_DIR/conf
___ edit mvh.conf
@@ -283,13 +257,13 @@
___ run tests & fix problems they show
- # Set the MVHub environment variables
- source /etc/mv_aliases
- cdw
+ # Set the MVHub environment variables
+ source /etc/mv_aliases
+ cdw
- mv_prove app-mvhub/t/ -r
- mv_prove lib-mvhub/t/ -r
-
+ mv_prove app-mvhub/t/ -r
+ mv_prove lib-mvhub/t/ -r
+
___ Access the MVHub application
firefox: http://mvh.$USER.localhost/
=== modified file 'app-mvhub/doc/checklists/setup_developer_on_brave.txt'
--- app-mvhub/doc/checklists/setup_developer_on_brave.txt 2010-03-08 08:07:29 +0000
+++ app-mvhub/doc/checklists/setup_developer_on_brave.txt 2010-04-17 00:20:29 +0000
@@ -98,27 +98,6 @@
# Set the permissions
sudo chown $NEW_DEV_USER:$NEW_DEV_USER /home/$NEW_DEV_USER/.ssh -R
-
-
- ___ Create user's muttrc file
-
- cdw
- cd app-mvhub/project-tools/developer_home_dir/
- sudo cp muttrc /home/$NEW_DEV_USER/.muttrc
-
- # Edit the muttrc file
- sudo $EDITOR /home/$NEW_DEV_USER/.muttrc
-
- # Change 'set pgp_sign_as="0x1234ABCD"' to be assigned to the
- # new user's pgp key. This is probably not setup at this point,
- # and will have to be revisited after the user creates their pgp
- # key. set the 'set from="$YOUR_EMAIL_ADDRESS" to be assigned to
- # the user's email address.
-
- # Set the permissions
-
- sudo chown $NEW_DEV_USER:$NEW_DEV_USER \
- /home/$NEW_DEV_USER/.muttrc
___ copy conf templates
Follow ups
