Add detection for an existing OctopusServer.config file in the home folder when setting up a new instance

[octopus-hideaki]

Prerequisites

• I have searched open and closed issues to make sure it isn't already requested
• My team has started working on this issue
• I have written a descriptive issue title

The enhancement

The Need

Customers can get caught out when an OctopusServer.config file already exists in the home folder used to set up a fresh Octopus Server instance. The OctopusServer.config file may exist for a number of reasons including customer testing, uninstalling/reinstalling different versions of Octopus, or issues with a customer attempting to upgrade while migrating to a new machine.The setup process does not currently appear to indicate that the existing OctopusServer.config file will be used, which can cause confusion when the Octopus Server service does not start as expected.

Solution

• Detect when there's a file in the home folder upon set-up
• If there is, prompt the user to delete the OctopusServer.config file from the home folder on the new machine

Links

Internal R&D Ticket