Enable `DRIVE_LOCATION` setting for deploying multiple instances of SASjs Server

[Allan Bowe]

Currently it is not possible for multiple instances of SASjs Server to share the same SASJS_ROOT - due to conflicts with logs, session folders etc.

Therefore we should look to separate the shareable parts from the instance-specific parts.

The proposal is as follows:

1. Implement new setting - DRIVE_LOCATION
2. This defaults to $(SASJS_ROOT)/drive if not specified
3. This should contain all of the following:
   • The ./files directory (becomes $(SASJS_ROOT)/drive/files)
   • The ./sasjscore directory (becomes $(SASJS_ROOT)/drive/sasjscore)
   • The appStreamConfig.json file (becomes $(SASJS_ROOT)/drive/appStreamConfig.json
4. If the DRIVE_LOCATION is not $(SASJS_ROOT)/drive then the above items should NOT be generated during the launch of SASjs Server.

The above actions will mean that the logs / sessions / uploads folders will be isolated from other instances.

The DRIVE_LOCATION is also where we should ultimately stick the sasv9.cfg file, per: #278

[Philip Mason]

This looks very useful

[SASjs Bot]

🎉 This issue has been resolved in version 0.25.0 🎉

The release is available on:

• GitHub release
• v0.25.0

Your semantic-release bot 📦🚀

[Philip Mason]

Thanks for doing this so fast.