[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
SF.net SVN: ledger-smb:[3223] trunk
- Subject: SF.net SVN: ledger-smb:[3223] trunk
- From: ..hidden..
- Date: Sat, 11 Jun 2011 16:13:17 +0000
Revision: 3223
http://ledger-smb.svn.sourceforge.net/ledger-smb/?rev=3223&view=rev
Author: ehuelsmann
Date: 2011-06-11 16:13:17 +0000 (Sat, 11 Jun 2011)
Log Message:
-----------
Replace INSTALL with something hopefully more targeted at our user base.
Modified Paths:
--------------
trunk/tools/prepare-company-database.sh
Added Paths:
-----------
trunk/INSTALL
Removed Paths:
-------------
trunk/INSTALL
trunk/INSTALL.manual
Deleted: trunk/INSTALL
===================================================================
--- trunk/INSTALL 2011-06-11 14:55:09 UTC (rev 3222)
+++ trunk/INSTALL 2011-06-11 16:13:17 UTC (rev 3223)
@@ -1,135 +0,0 @@
-LedgerSMB 1.3 (svn trunk) INSTALL
-=================================
-
-This file documents automated installation methods for LedgerSMB 1.3.0.
-
-Manual installation instructions have been moved to INSTALL.manual, and it does
-not cover checking out from svn or obtaining a tarball (we assume if you have
-this file, you are already past that point).
-
-
-Requirements
-------------
-
-LedgerSMB 1.3 requires the following software before you begin.
- * PostgreSQL 8.1 or higher
- * Perl 5.8 or higher
- * A web server (Apache 2.2, for example) which supports both executing CGI
- scripts and passing authentication data to them.
-
-the instructions here assume Linux or UNIX.
-
-
-Change working directory to /path/to/ledgersmb13
--------------------------------------------------
-
-For this INSTALL procedure /path/to/ledgersmb13 is the location where you have
-manually installed the LedgerSMB 1.3 source or checkout. LedgerSMB 1.3 in
-pre-alpha form is not currently packaged for any distribution.
-
-$ cd /path/to/ledgersmb13/
-/path/to/ledgersmb13 $
-
-All commands from this point forward are executed from a working directory of
-/path/to/ledgersmb13 unless otherwise noted.
-
-
-Application Installation
------------------------
-
-An automated install script (minus the database installation) is found in
-install.sh. This script installs the necessary perl modules and configures
-Apache using the ledgersmb-http.conf file as a template.
-
-After running this script, you will need to restart apache:
-
-$ sudo /etc/init.d/apache2 restart
- * Stopping apache2 ... [ ok ]
- * Starting apache2 ... [ ok ]
-
-(On other systems you may need to log in as root to do this.)
-
-
-Apache must be able to read and write /path/to/ledgersmb13/templates/
--------------------------------------------------
-
-Make sure the /path/to/ledgersmb13/templates directory is read-writable by
-user:group apache:apache, or as appropriate for your distribution's Apache
-conventions.
-
-Apache must also be able to read (but not write) /path/to/ledgersmb13/ and its
-subdirectories.
-
-
-=========================
-PostgreSQL Configuration
-=========================
-
-LedgerSMB 1.3 is tightly integrated with PostgreSQL. In the current beta
-state, it is necessary to run several PostgreSQL commands and SQL statements
-exactly as shown below. Automated installion is still somewhat shakey.
-
-
-Securing PostgreSQL with LedgerSMB
-========================================
-
-LedgerSMB 1.3.0 and higher use the database to enforce all permissions and
-ensure that users are who they say they are. For this reason, it is critical
-that PostgreSQL be properly secured.
-
-In the standard setup, LedgerSMB authenticates a user by logging into PostgreSQL
-with the username/password provided. For this reason it is important that the
-authentication in PostgreSQL be properly configured. This is handled in the
-pg_hba.conf file in the PostgreSQL data directory. Each line ends in an
-authentication method. Methods which can cause major problems include:
- * trust (allows any user to authenticate merely by knowing the username)
- * ident sameuser (which, in most cases, will just prevent anyone from logging
- on)
-
-Most commonly you want to set the authentication for every user, database, etc.
-to md5, which uses a digest-type authentication which is reasonably secure.
-
-In this file you can also require SSL to be used to connect to the database.
-This is most helpful when the web server and database server are on different
-computers.
-
-
-Automated PostgreSQL Database Setup
-===================================
-Point your browser to http://[yourhost]/path/to/ledgersmb/initiate.pl
-
-You will see an HTTP authentication prompt. Enter credentials for the database
-superuser (for example "postgres" user). Then follow the prompts and fill in
-the information.
-
-There is also a script provided called 'install-mycompany.sh' which can be used
-to set up the database from the command line.
-
-Login to LedgerSMB 1.3 Instance
-===============================
-
-It should now be possible to log into your LedgerSMB 1.3 instance at:
-
-http://localhost/ledgersmb
-
-With cookies enabled for localhost.
-
-Name: myuser
-Password: MYUSER_PASSWORD
-Company: mycompany
-
-
-How-To Section
-==============
-
-Q: How do I remove the 90+ roles for mycompany created by the INSTALL process?
-
-A: First, since most objects in the mycompany database depend on these roles,
-you must drop the mycompany database first, obviously with loss of data.
-
-$ dropdb -U postgres mycompany
-
-After that, you must issue the droprole command for each rolname in the query
-embedded in the following command:
-
-$ for role in `psql -U postgres -t -c "SELECT rolname FROM pg_roles WHERE rolname LIKE 'lsmb_mycompany%';"`; do dropuser -U postgres $role; done
Added: trunk/INSTALL
===================================================================
--- trunk/INSTALL (rev 0)
+++ trunk/INSTALL 2011-06-11 16:13:17 UTC (rev 3223)
@@ -0,0 +1,299 @@
+
+
+Contents
+--------
+
+ * System requirements
+ * Installing Perl module dependencies
+ * for Debian
+ * for Fedora
+ * for <your system>
+ * Adding configuration to Apache 2.x
+ * Initializing a company database
+
+
+System requirements
+===================
+
+LedgerSMB depends on the following software:
+
+ * a web server (Apache v2.x or MS IIS)
+ * PostgreSQL 8.1+
+ * Perl 5.8+
+
+
+
+Installing Apache 2
+===================
+
+On Debian and its derivatives - like Ubuntu - Apache installation
+is as simple as running:
+
+ $ apt-get install apache2
+
+On Fedora systems the following command does the same:
+
+ $ yum install httpd
+
+On other systems, the steps to follow may differ. Please submit
+instructions for your system for inclusion here.
+
+
+Installing PostgreSQL
+=====================
+
+On Debian and its derivatives installing PostgreSQL works with:
+
+ $ apt-get install postgresql-server postgresql-client postgresql-contrib
+
+On Fedora systems this command does the same:
+
+ $ yum install postgresql postgresql-server
+
+On other systems, the steps to follow may differ. Please submit
+instructions for your system for inclusion here.
+
+
+Installing Perl module dependencies
+===================================
+
+LedgerSMB depends on these required modules:
+
+ Data::Dumper
+ Log::Log4perl
+ Locale::Maketext
+ DateTime
+ Locale::Maketext::Lexicon
+ DBI
+ MIME::Base64
+ Digest::MD5
+ HTML::Entities
+ DBD::Pg
+ Math::BigFloat
+ IO::File
+ Encode
+ Locale::Country
+ Locale::Language
+ Time::Local
+ Cwd
+ Config::Std
+ MIME::Lite
+ Template
+ Error
+ CGI::Simple
+
+and these optional ones:
+
+ Net::TCLink [Support for TrustCommerce credit card processing]
+ Parse::RecDescent [Support for the *experimental* scripting engine]
+ Template::Plugin::Latex [Support for Postscript and PDF output]
+ XML::Twig [Support for OpenOffice output]
+ Excel::Template::Plus [Support for Excel output]
+
+
+All these modules can be downloaded from CPAN, the modules distribution
+archive for Perl. However our experience has been that if your distribution
+provides a module via its package manager (apt, rpm, etc.), you will have
+fewer difficulties if you use that instead.
+
+The sections below list specific instructions for the different OSes and
+distributions. If you plan to depend as much as possible - as recommended -
+on your distribution, you should follow the instructions in those sections
+before proceeding here.
+
+When you have completed the distribution specific steps described below,
+you should proceed to run:
+
+ $ perl Makefile.PL
+ $ make install
+
+which will ask you which modules it should download, if you didn't install
+- using your package manager - all of the required and optional modules
+listed above. If you don't want support for a specific module, simply
+answer 'no' in response to the download question.
+
+Remark: If you've never downloaded packages from CPAN, Perl is likely
+to ask you a number of questions regarding the configuration of the
+CPAN module (the Perl module downloader) as well.
+
+
+
+
+>>> Perl module dependencies for Debian
+
+[For a list of actions to take on Lenny, see below]
+
+---- Actions for Debian Squeeze
+
+To install all the required packages which Squeeze supports, execute the
+following command:
+
+ $ aptitude install libdatetime-perl libdbi-perl libdbd-pg-perl \
+ libcgi-simple-perl libtemplate-perl libconfig-std-perl libmime-lite-perl \
+ liberror-perl liblocale-maketext-lexicon-perl libtest-exception-perl \
+ libtest-trap-perl liblog-log4perl-perl
+
+This installs the modules available from the Squeeze repository.
+
+As far as the optional packages are concerned on Squeeze, the Excel and
+PDF/Postscript output options are not directly available. If you want
+these output options, you'll need to download them from CPAN.
+
+Please note that the PDF/Postscript module depends on the TeX/LaTeX
+package which *is* in the Squeeze package repository:
+
+ $ aptitude install texlive-latex-recommended
+
+The credit card processing support for TrustCommerce is available
+from the Squeeze repository through:
+
+ $ aptitude install libnet-tclink-perl
+
+The Open Office output option is available from the Squeeze repository
+as well through the command:
+
+ $ aptitude install libxml-twig-perl
+
+
+---- Actions for Debian Lenny
+
+To install all the required packages which Lenny supports, execute the
+following command:
+
+ $ aptitude install libdatetime-perl libdbi-perl libdbd-pg-perl \
+ libcgi-simple-perl libtemplate-perl libconfig-std-perl libmime-lite-perl \
+ liberror-perl liblocale-maketext-lexicon-perl libtest-exception-perl \
+ liblog-log4perl-perl
+
+The required module Test::Trap isn't available as a Lenny package. In order
+to install that component, execute the following commands:
+
+ $ aptitude install libmodule-install-perl
+ $ cpan 'Test::Trap'
+
+
+As far as the optional packages are concerned on Lenny, the Excel and
+PDF/Postscript output options are not directly available. If you want
+these output options, you'll need to download them from CPAN.
+
+Please note that the PDF/Postscript module depends on the TeX/LaTeX
+package which *is* in the Lenny package repository:
+
+ $ aptitude install texlive-latex-recommended
+
+The credit card processing support for TrustCommerce is available
+from the Lenny repository through:
+
+ $ aptitude install libnet-tclink-perl
+
+The Open Office output option is available from the Lenny repository
+as well through the command:
+
+ $ aptitude install libxml-twig-perl
+
+
+Initializing a company database
+===============================
+
+LedgerSMB 1.3 stores data for each company in a separate "database". A
+database is a PostgreSQL concept for grouping tables, indexes, etc.
+
+Each company database must be named. This name is essentially the system
+identifier within PostgreSQL for the company's dataset. The name for the
+company database can only contain letters, digits and underscores.
+Additionally, it must start with a letter. Company database names are
+case insensitive, meaning you can't create two separate company databases
+called 'Ledgersmb' and 'ledgersmb'.
+
+The 'prepare-company-database.sh' script in the tools/ directory will set
+up databases to be used for LedgerSMB. The script should be run as 'root'
+because it wants to 'su' to the postgres user. Alternatively, if you
+know the password of the postgres user, you can run the script as any other
+user. You'll be prompted for the password.
+
+
+The following invocation of the script sets up your first test company,
+when invoked as the root user and from the root directory of the LedgerSMB
+sources:
+
+ $ ./prepare-company-database.sh --company testinc
+
+The script assumes your PostgreSQL server runs on 'localhost' with
+PostgreSQL's default port (5432).
+
+Upon completion, it'll have created a company database with the name
+'testinc', a user called 'ledgersmb' (password: 'LEDGERSMBINITIALPASSWORD'),
+a single user called 'admin' (password: 'admin') and the roles required to
+manage authorizations.
+
+Additionally, it'll have loaded a minimal list of languages required
+to succesfully navigate the various screens.
+
+All these can be adjusted using arguments provided to the setup script. See
+the output generated by the --help option for a full list of options.
+
+
+Adding configuration to Apache 2.x
+==================================
+
+LedgerSMB requires a webserver which passes authentication information
+through to the LedgerSMB application. Currently, Apache (with mod_rewrite
+support) and IIS are known to support this requirement. The section below
+details the Apache setup process.
+
+If your Apache has been built with module support, your configuration files
+should include the following line somewhere:
+
+LoadModule rewrite_module <path-to-apache-modules-directory>/mod_rewrite.so
+
+[On Debian and its derivatives, mod_rewrite can be enabled using the command
+
+ $ a2enmod rewrite
+
+executed as the root user.]
+
+A default configuration file to be used with Apache2 comes with LedgerSMB in
+its root project directory: ledgersmb-httpd.conf.template. If you ran the
+'prepare-company-database.sh' script from the last section, the template
+has been filled out for you and stored as ledgersmb-httpd.conf.
+
+You need to add a commmand to your Apache configuration to load the
+configuration in that file by including the following line:
+
+Include /path/to/ledgersmb/ledgersmb-httpd.conf
+
+[On Debian and derivatives, you can store the resulting
+configuration file directly in the /etc/apache2/conf.d directory. From
+that location, it'll be automatically included upon the next server (re)start.]
+
+
+In order for the changes to take effect, you should run
+
+ $ apachectl restart
+
+On some systems apachectl might be called apache2ctl.
+
+On systems without apachectl support, you will need to run either:
+
+ $ service apache2 restart
+
+or
+
+ $ /etc/init.d/apache2 restart
+
+
+Manual configuration
+====================
+
+If you want to perform the installation of the company database completely
+manually, you should consult the 'tools/prepare-company-database.sh' script
+as the authorative documentation of the steps to perform.
+
+
+Company database removal
+========================
+
+In the tools/ directory, there's a script which will remove a company
+database and all the standard authorization data that's created by
+the 'prepare-company-database.sh' script. Said script is called
+'delete-company-database.sh'.
Deleted: trunk/INSTALL.manual
===================================================================
--- trunk/INSTALL.manual 2011-06-11 14:55:09 UTC (rev 3222)
+++ trunk/INSTALL.manual 2011-06-11 16:13:17 UTC (rev 3223)
@@ -1,306 +0,0 @@
-LedgerSMB 1.3 (svn trunk) INSTALL.manual
-=================================
-
-This file documents manual installation methods for LedgerSMB 1.3.0.
-
-Manual installation instructions have been moved to INSTALL.manual, and it does
-not cover checking out from svn or obtaining a tarball (we assume if you have
-this file, you are already past that point).
-
-The methods here are provided in case you get stuck or wish to install into a
-non-standard environment. Because we currently lack a Windows installer, users
-of that platform are likely to need to follow the instructions here and adapt
-as necessary (for example, if you are using IIS instead of Apache).
-
-Before we begin, you will want to cd to the directory of the LedgerSMB directory
-where the svn tree has been checked out or the tarball has been untarred into:
-
-$ cd /path/to/ledgersmb13
-
-
-Apache Configuration
-====================
-
-LedgerSMB uses Apache-2.x, with mod_rewrite.
-
-
-Create up an Apache conf file for the /path/to/ledgersmb13 location
-----------------------------------------------------------
-
-Configure ledgersmb-httpd.conf for apache, subsituting /path/to/ledgersmb13 with
-the absolute path of your LedgerSMB installation.
-
-The following sed command applies the repetitive substitution automatically.
-
-$ sed -e "s|WORKING_DIR|$(pwd)|" ledgersmb-httpd.conf > ledgersmb-httpd-13.conf
-
-You can also apply the substitution manually in your preferred text editor.
-
-
-Install the Apache conf file
-----------------------------
-
-Move the apache conf file ledgersmb-httpd-13.conf to a location where it will be
-picked up on apache restart. One way is to use an include statement in
-/etc/apache2/httpd.conf (e.g. Include /etc/apache2/app/*.conf).
-
-$ sudo mv ledgersmb-httpd-13.conf /etc/apache2/app/ledgersmb13.conf
-
-Restart apache:
-
-$ sudo /etc/init.d/apache2 restart
- * Stopping apache2 ... [ ok ]
- * Starting apache2 ... [ ok ]
-
-The LedgerSMB-specific apache configuration can later be integrated into your
-virtual host configuration as needed.
-
-
-Verify that RewriteRule is working
-----------------------------------
-
-LedgerSMB 1.3 depends on mod_rewrite's ReWriteRule. Make sure that your Apache
-has module or built-in support for mod_rewrite. You can test this if you are
-unsure. Use an .htaccess file to check that mod_rewrite is working and that our
-directory alias has been loaded by apache (this has to be done from the
-LedgerSMB directory):
-
-$ echo -e 'RewriteEngine on\nRewriteRule ^(.*)$ http://www.google.com [R]' > .htaccess
-
-$ wget -qO /dev/stdout http://localhost/ledgersmb | grep -c '<title>Google</title>'
-1
-
-If you saw the grep output "1" above, RewriteRule is working. Remove your
-temporary .htaccess file:
-
-$ rm .htaccess
-
-
-Apache must be able to read and write to the templates/ directory
--------------------------------------------------------------------
-
-Make sure the templates directory is read-writable by
-user:group apache:apache, or as appropriate for your distribution's Apache
-conventions.
-
-Apache must also be able to read (but not write) the LedgerSMB root directory
-and its subdirectories.
-
-
-Check And Satisfy Perl Dependencies
-===================================
-
-LedgerSMB depends on Perl-5.8, and several CPAN packages, which may or may not
-be available as system packages for your linux distribution:
-
-$ perl -v | grep v5.
-This is perl, v5.8.8 built for i686-linux
-
-Using the Makefile.PL requires Module::Install. If you do not have
-Module::Install loaded on your system, you can install it using:
-
-# cpan Module::Install
-
-Run Makefile.PL to check for LedgerSMB's Perl dependencies. The output should be
-similar to the following:
-
-$ perl Makefile.PL
-include /path/to/ledgersmb13/inc/Module/Install.pm
-include inc/Module/Install/Metadata.pm
-include inc/Module/Install/Base.pm
-include inc/Module/Install/AutoInstall.pm
-include inc/Module/Install/Include.pm
-include inc/Module/AutoInstall.pm
-*** Module::AutoInstall version 1.03
-*** Checking for Perl dependencies...
-[Core Features]
-- Test::More ...loaded. (0.86)
-- Test::Trap ...loaded. (0.0.23)
-- Test::Exception ...loaded. (0.27)
-- Data::Dumper ...loaded. (2.121)
-- Locale::Maketext ...loaded. (1.13)
-- DateTime ...loaded. (0.47)
-- Locale::Maketext::Lexicon ...loaded. (0.77 >= 0.56)
-- DBI ...loaded. (1.607 >= 1.00)
-- MIME::Base64 ...loaded. (3.07)
-- Digest::MD5 ...loaded. (2.38)
-- HTML::Entities ...loaded. (3.60)
-- DBD::Pg ...loaded. (2.11.8)
-- Math::BigFloat ...loaded. (1.51)
-- IO::File ...loaded. (1.13)
-- Encode ...loaded. (2.12)
-- Locale::Country ...loaded. (2.07)
-- Locale::Language ...loaded. (2.07)
-- Time::Local ...loaded. (1.1901)
-- Cwd ...loaded. (3.29)
-- Config::Std ...loaded. (0.0.4)
-- MIME::Lite ...loaded. (3.024)
-- Template ...loaded. (2.20 >= 2.14)
-- Error ...loaded. (0.17015)
-- CGI::Simple ...loaded. (1.108)
-[POS module credit card processing support]
-- Net::TCLink ...loaded. (3.4)
-[Experimental scripting engine]
-- Parse::RecDescent ...loaded. (1.94)
-[Developer tool dependencies]
-- Getopt::Long ...loaded. (2.38)
-- FileHandle ...loaded. (2.01)
-[PDF and Postscript output]
-- Template::Plugin::Latex ...loaded. (2.70)
-[OpenOffice.org output]
-- XML::Twig ...loaded. (3.32)
-- OpenOffice::OODoc ...loaded. (2.035)
-[Excel output]
-- Excel::Template::Plus ...loaded. (0.03)
-*** Module::AutoInstall configuration finished.
-include inc/Module/Install/Makefile.pm
-include inc/Module/Install/WriteAll.pm
-Writing META.yml
-include inc/Module/Install/Win32.pm
-include inc/Module/Install/Can.pm
-include inc/Module/Install/Fetch.pm
-include inc/Module/Install/Build.pm
-Writing Makefile for LedgerSMB
-
-Use your distribution's CPAN or packaging tools to satisfy the dependencies
-shown above.
-
-
-Installing PostgreSQL Contrib Function Libraries (Not Optional)
-===============================================================
-
-LedgerSMB 1.3 depends on several function libraries distributed with PostgreSQL,
-but typically not installed by default in most distributions.
-
-Identify the system package containing the files tsearch2.sql, tablefunc.sql,
-and pg_trgm.sql. Install that package, and locate the files on the filesystem.
-
-If you install these on template1 then you only need to install these function
-libraries once per postgresql cluster. They will be included in any new
-database created from template1.
-
-For the remainder of this INSTALL procedure, you will need to become user
-postgres, or have the ability to log in to psql as your current user, or issue
-the commands with: sudo -u postgres [cmd].
-
-
-Install Tsearch2 Full Text indexing engine for PostgreSQL
----------------------------------------------------------
-
-$ psql -U postgres -d template1 -f /usr/share/postgresql-8.3/contrib/tsearch2.sql
-
-
-Install tablefunc.sql for PostgreSQL
-------------------------------------
-
-$ psql -U postgres -d template1 -f /usr/share/postgresql-8.3/contrib/tablefunc.sql
-
-
-Install pg_trgm.sql for PostgreSQL
-----------------------------------
-
-$ psql -U postgres -d template1 -f /usr/share/postgresql-8.3/contrib/pg_trgm.sql
-
-
-Configure a LedgerSMB Company Database
-======================================
-
-Create a LedgerSMB company database. The user and configuration information
-are stored alongside the accounting data as of this writing:
-
-$ createdb -U postgres -O ledgersmb mycompany
-
-
-Install the plpgsql procedural language to the company database:
-
-$ createlang plpgsql mycompany
-
-
-Apply the SQL statements in sql/Pg-database.sql to
-the company database:
-
-$ psql -U postgres -d mycompany -f sql/Pg-database.sql
-
-
-Apply the in-development SQL statements in the files sql/modules/ to
-the company database, in exactly the order specified in sql/modules/LOADORDER:
-
-$ psql -U postgres -d mycompany -f sql/modules/Drafts.sql
-$ psql -U postgres -d mycompany -f sql/modules/chart.sql
-
-etc.
-
-Load a template Chart of Accounts
----------------------------------
-
-The user is encouraged to create a custom chart of accounts, but for the
-purposes of this INSTALL, load a template chart of accounts from the most
-appropriate SQL statement file under sql/coa:
-
-$ psql -U postgres -d mycompany -f sql/coa/us/chart/General.sql
-
-
-Generate A Custom Roles SQL Statement File
-------------------------------------------
-
-Preprocess the sql/modules/Roles.sql file with sed, generating a custom SQL
-file:
-
-$ sed -e 's/<?lsmb dbname ?>/mycompany/g' sql/modules/Roles.sql > mycompany_roles.sql
-
-
-Apply the SQL statements in the sed-generated file mycompany_roles.sql to the
-company database:
-
-$ psql -U postgres -d mycompany -f mycompany_roles.sql
-
-
-Create A Company User
-=====================
-
-There are a set of stored procedures for this. The best way to do this (which
-creates the user, inserts into all applicable tables, etc.) is to run the
-following query from the psql prompt or PgAdmin:
-
-SELECT admin__save_user(NULL, -- no user id yet, create new user
- person__save(NULL, -- create new person
- 3, -- employee/user
- 'First_name', -- First Name
- 'Last_name', -- Last Name
- (select id from country
- where short_name = 'US') -- example
- ),
- 'username', -- Username desired
- '[yourpasswd]' -- password
- );
-
-If you want to create a few users, you can (for example):
-
-PREPARE my_user_q (text, text, text, text, text)
-AS SELECT admin__save_user(NULL,
- person_save(NULL, 3,
- $1, $2,
- (SELECT id FROM country
- where short_name = $3)
- ),
- $4, $5);
-
-EXECUTE my_user_q('Tony', 'Davis', 'US', 'tony_d', 'Wferw324$');
-EXECUTE my_user_q('David', 'Stewart', 'UK', 'dstewart', 'SDFEWRer43245(');
-
-etc.....
-
-Granting Roles to User
-======================
-
-You can now grant roles to a user using:
-
-SELECT admin__add_user_to_role('username', 'role');
-
-If you want to add a user to every role, you can:
-
-SELECT admin__add_user_to_role('username', rolname)
-FROM pg_roles
-WHERE rolname like 'lsmb_[dbname]';
-
-
Modified: trunk/tools/prepare-company-database.sh
===================================================================
--- trunk/tools/prepare-company-database.sh 2011-06-11 14:55:09 UTC (rev 3222)
+++ trunk/tools/prepare-company-database.sh 2011-06-11 16:13:17 UTC (rev 3223)
@@ -12,7 +12,7 @@
port=5432
srcdir=$PWD
dstdir=$PWD
-coa=
+coa=$srcdir/sql/coa/us/chart/General.sql
gifi=
pgsql_contrib_dir=ignore
ADMIN_FIRSTNAME='Default'
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.