Bug #4514
closed
Files are being saved in the Kepler installation directory
Added by Chad Berkley over 14 years ago.
Updated over 14 years ago.
Description
There are still files and directories being saved, at runtime, to the Kepler installation directory. These files need to be saved to the .kepler directory instead. The files/dirs that I see are:
configuration (dir)
InstanceAuthNamespace
InstanceAuthNamespaceTesting
To close this bug, change the location of these files to <user.home>/.kepler.
There are two options here, keep the configuration directory in the installation directory and save the other files there. Or move the configuration directory to .kepler and keep the InstanceAuthNamespace in the installation directory.
The reason is that the InstanceAuthNamespace uniquely identifies a Kepler installation. If you want to generate the InstanceAuthNamespace during the installation and move the configuration directory to .kepler and then keep the separate Kepler installation configurations in subdirectories labeled by their InstanceAuthNamespace values that could work. Please discuss with me if it is not clear.
I just sent a related email to kepler-dev, "proposed changes to .kepler".
After discussion w/ Chad and Aaron it sounds like we're ok with keeping InstanceAuthNamespace in the installation directory since it's only generated once, but that the configuration can go away, though the idea of storing configuration files beneath an instanceAuthNamespace directory inside .kepler can be incorporated.
configuration/ has been moved.
I think we just need to deal with / come to a consensus on InstanceAuthNamespace and LastObjectID now.
InstanceAuthNamespace now gets saved into the persistent Kepler core module directory. LastObjectID file is no longer used.
Original Bugzilla ID was 4514
Also available in: Atom
PDF