Difference between revisions of "TracSVN"

From OSGeo
Jump to navigation Jump to search
(→‎Apache: gogs->gitea)
(add some info about PostgreSQL)
Line 9: Line 9:
 
The Apache configuration <code>/etc/apache2</code> is under revision control via Git.
 
The Apache configuration <code>/etc/apache2</code> is under revision control via Git.
 
One clone of this repository can be accessed by [[SAC]] members via https://git.osgeo.org/gitea/sac/tracsvn-apache-config (ref [[SAC:Gitea]])
 
One clone of this repository can be accessed by [[SAC]] members via https://git.osgeo.org/gitea/sac/tracsvn-apache-config (ref [[SAC:Gitea]])
 +
 +
= PostgreSQL =
 +
 +
PostgreSQL is configured to always require passwords. Services with non-centralized configuration (like trac) are using .pgpass file to avoid duplication, which means every user using trac-admin will need to have the
 +
same .pgpass (this may change in the future). Currently users "www-data" and
 +
"git" have the .pgpass file in their home. This lets Gitea git hooks use trac-admin command successfully, and Trac (run via Apache thus www-data user)
 +
also work.
  
 
[[Category:Infrastructure]]
 
[[Category:Infrastructure]]

Revision as of 14:46, 17 July 2018

The Tracsvn VM is a virtual machine (see SAC_Service_Status) administered by SAC, hosted on osgeo3 at OSU OSL and used for source code management.

Apache

The Apache configuration /etc/apache2 is under revision control via Git. One clone of this repository can be accessed by SAC members via https://git.osgeo.org/gitea/sac/tracsvn-apache-config (ref SAC:Gitea)

PostgreSQL

PostgreSQL is configured to always require passwords. Services with non-centralized configuration (like trac) are using .pgpass file to avoid duplication, which means every user using trac-admin will need to have the same .pgpass (this may change in the future). Currently users "www-data" and "git" have the .pgpass file in their home. This lets Gitea git hooks use trac-admin command successfully, and Trac (run via Apache thus www-data user) also work.