Closed WilliamMcCumstie closed 6 years ago
Hold off merging this PR until GitHub
sorts its problem out. It appears a few commits are missing. Hmmm
Oh well, this comment will probably be rejected by the GitHub
servers
This PR makes the download and install of flight-cache
independent of the global server. It does not however fix the snapshot itself. Thus it is a part fix for issue #21
The public directory is also set during the install process. This should fix #26
The bug with FileUtils
in flight-syncer
has also been resolved. Fixes #27
Currently the yum repo version of
postgres
is set to 9.2. This is to old to work with thepg
and as such a newer version needs to be installed instead.To keep with the standard flight design pattern, a version of postgres has been compiled that can be installed into
$FL_ROOT/opt/postgres
. Then when it is installed, thedb
data is stored within$FL_ROOT/var/postgres/data
.This service is managed by. The service has been namedsystemd
and thus a unit file is still written to/usr/lib/systemd/system
postgresql-flight
so that is appears along side the originalpostgresql
service without replacing it.EDIT: The
systemd
unit files are now installed into/etc/systemd/system
as they are installed outside of a package managerTo make offline install work correctly,
flight-cache
has also been updated. It no longer uses theanvil
packages, instead it buildsanvil
directly into the package. This requires downloading the rails gems without installing them. As rails requires native c extensions, it is best to install/compile the gems at install time. However bybundle package
ing the gems at build time,flight-cache
can still be installed offline.Finally, rails uses the
pg
gem to connect to postgres. This gem needs to be compiled against the flight version of postgres. As such thepg
build config is set to use the correctpg_config
.