Currently Fork accesses a servers directory by expecting the name of the directory to be the name of the server. This means, that renaming a server breaks Fork.
Solution:
Introduce a fork.json which is created in each servers directory that contains the servers ID. At startup Fork scans all folders in the server directory and looks for the servers it knows.
Edge cases:
- If a server is not found at startup notify the user
- If a new server is found promt the user with an import
- Check the folder before each access for the
fork.json in case of a rename at runtime
Currently Fork accesses a servers directory by expecting the name of the directory to be the name of the server. This means, that renaming a server breaks Fork.
Solution:
Introduce a
fork.jsonwhich is created in each servers directory that contains the servers ID. At startup Fork scans all folders in the server directory and looks for the servers it knows.Edge cases:
fork.jsonin case of a rename at runtime