GitHub user jeffmart opened a pull request:

    https://github.com/apache/incubator-trafficcontrol/pull/456

    [TC-228] postinstall and INSTALL.md updates

    INSTALL.md
    - Changed manual installation approach for non-containered postgres
    
    postinstall
    - Set reconfigure to 1, always init database
    - Set debug to 1, always output so the end user sees what is
         happening
    - set the goose needed driver to "postgres" instead of "Pg"
    - changed question default: "Database server root (admin) user"
         name from "root" to "postgres"
    - set PGUSER and PGPASSWORD in env to login to the postgres
         superuser account
    - update traffic_ops database table with the "admin" user name
         and password provided by user (after initdb)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jeffmart/incubator-trafficcontrol 
postinstall_fix_TC-228

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafficcontrol/pull/456.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #456
    
----
commit f019dbb136cb5cf751df9996b06a6e0f6f6f5020
Author: Jeff Martin <[email protected]>
Date:   2017-04-11T19:06:55Z

    [TC-228] postinstall and INSTALL.md updates
    
    INSTALL.md
    - Changed manual installation approach for non-containered postgres
    
    postinstall
    - Set reconfigure to 1, always init database
    - Set debug to 1, always output so the end user sees what is
         happening
    - set the goose needed driver to "postgres" instead of "Pg"
    - changed question default: "Database server root (admin) user"
         name from "root" to "postgres"
    - set PGUSER and PGPASSWORD in env to login to the postgres
         superuser account
    - update traffic_ops database table with the "admin" user name
         and password provided by user (after initdb)

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to