Upgrading to 3.4.6
cantor.2 at osu.edu
Thu Nov 7 15:14:08 EST 2019
On 11/7/19, 3:08 PM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:
> One better, use a symlink to point to the current version. When you upgrade, just repoint the symlink.
Other than making sure there's a backup (which the installer creates, but you really should have it all tracked by source control anyway...), eventually there really isn't any need to do anything unusual.
> I just want to make sure the install.sh script does not use the path passed in for "Installation Directory" for anything
> other than to copy the new files to.
Not at present, but that's not how the process is documented, so that's not a guaranteed assumption. It doesn't want to know a made up directory name you just created, it wants to know where it was installed and will be run from. You should assume that you need to give it that value. We will not know to point out that something we didn't explicitly support suddenly doesn't work anymore. This has happened on numerous occasions with the webapp tree and other aspects of the installation process.
More information about the users