Fix TO Golang docs config file name

Project: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/repo
Commit: 
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/commit/8e8383eb
Tree: 
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/tree/8e8383eb
Diff: 
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/diff/8e8383eb

Branch: refs/heads/master
Commit: 8e8383eb64987a77aae3c0cc7235711b9b79a8d6
Parents: 10a410a
Author: Robert Butts <robert.o.bu...@gmail.com>
Authored: Tue Aug 1 18:04:44 2017 -0600
Committer: Dewayne Richardson <dewr...@apache.org>
Committed: Thu Aug 10 09:46:03 2017 -0600

----------------------------------------------------------------------
 docs/source/admin/traffic_ops/configuration.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol/blob/8e8383eb/docs/source/admin/traffic_ops/configuration.rst
----------------------------------------------------------------------
diff --git a/docs/source/admin/traffic_ops/configuration.rst 
b/docs/source/admin/traffic_ops/configuration.rst
index 66158d9..45b952b 100644
--- a/docs/source/admin/traffic_ops/configuration.rst
+++ b/docs/source/admin/traffic_ops/configuration.rst
@@ -300,4 +300,4 @@ Configuring the Go Application
 =======================
 Traffic Ops is in the process of migrating from Perl to Go, and currently runs 
as two applications. The Go application serves all endpoints which have been 
rewritten in the Go language, and transparently proxies all other requests to 
the old Perl application. Both applications are installed by the RPM, and both 
run as a single service. When the project has fully migrated to Go, the Perl 
application will be removed, and the RPM and service will consist solely of the 
Go application.
 
-By default, the postinstall script configures the Go application to behave and 
transparently serve as the old Perl Traffic Ops did in previous versions. This 
includes reading the old ``cdn.conf`` and ``database.conf`` config files, and 
logging to the old ``access.log`` location. However, if you wish to customize 
the Go Traffic Ops application, you can do so by running it with the 
``-oldcfg=false`` argument. By default, it will then look for a config file in 
``/opt/traffic_ops/conf/traffic_ops_golang.json``. The new config file location 
may also be customized via the ``-cfg`` flag. A sample config file is installed 
by the RPM at ``/opt/traffic_ops/conf/traffic_ops_golang.json``. If you wish to 
run the new Go Traffic Ops application as a service with a new config file, the 
``-oldcfg=false`` and  ``-cfg`` flags may be added to the ``start`` function in 
the service file, located by default at ``etc/init.d/traffic_ops``.
+By default, the postinstall script configures the Go application to behave and 
transparently serve as the old Perl Traffic Ops did in previous versions. This 
includes reading the old ``cdn.conf`` and ``database.conf`` config files, and 
logging to the old ``access.log`` location. However, if you wish to customize 
the Go Traffic Ops application, you can do so by running it with the 
``-oldcfg=false`` argument. By default, it will then look for a config file in 
``/opt/traffic_ops/conf/traffic_ops_golang.config``. The new config file 
location may also be customized via the ``-cfg`` flag. A sample config file is 
installed by the RPM at ``/opt/traffic_ops/conf/traffic_ops_golang.config``. If 
you wish to run the new Go Traffic Ops application as a service with a new 
config file, the ``-oldcfg=false`` and  ``-cfg`` flags may be added to the 
``start`` function in the service file, located by default at 
``etc/init.d/traffic_ops``.

Reply via email to