You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I know, no debian package is configured to claim the ownership of the /etc/georchestra/default.properties file, which means that a default setup based on these packages might be broken (or we have a good luck with default parameter values).
Maybe the Security-proxy should take care of the file ?
The text was updated successfully, but these errors were encountered:
totally agree, saw that and i didnt really know what to do with this issue... but generally, i'd say a good practice is to checkout a datadir from git to keep track of files (and eventually compare with the .dpkg-dist files upon pkg upgrades). So i'm not sure if its a real issue (it is one for ppl who dont checkout a datadir)
My concern is in case we want to split the infrastructure onto several different servers, why would one want to force installing the SP if the machine is supposed to be dedicated to GN or GS ?
we could also build a package "georchestra-common" from this repository, and having by default as a dependency from our packages ? I shall see how to create a debian package (outside of maven I mean)
As far as I know, no debian package is configured to claim the ownership of the
/etc/georchestra/default.properties
file, which means that a default setup based on these packages might be broken (or we have a good luck with default parameter values).Maybe the Security-proxy should take care of the file ?
The text was updated successfully, but these errors were encountered: