Lodestone checks for the existence of an environmental variable LODESTONE_PATH upon startup. If said env var exists it will use that path. If not, it will default to your home directory.

On *nix: ~/.lodestone

On Windows: %userprofile%/.lodestone

Lodestone checks for the existence of an environmental variable LODESTONE_PATH upon startup. If said env var is found it will create that directory and use that as the storage location. If the env var is not found it will default to .lodestone directory under the user's home directory.

If you are on *nix: export LODESTONE_PATH=[replace this with your desired path]

If you are on Windows:

search for "env" in your search bar, open "Edit environmental variables for your account"

Click on "new"

Put LODESTONE_PATH as the name, and the absolute path to your directory as the value

To configure SSL/HTTPS with Lodestone Core, you'll need to place your SSL certificate and key files in a specific location and format. Here's the detailed step-by-step guide:

1. Create a directory named tls under the main Lodestone directory (LODESTONE_PATH).

2. Store your SSL certificate and key files within this newly created tls directory. They should be named as cert.pem and key.pem respectively.

   Note: If you have a fullchain.pem or another certificate file, you can simply rename it to cert.pem.

3. Once the certificate and key files are in place, start Lodestone Core. During the boot-up sequence, you should observe a message indicating either "TLS enabled" or "Invalid TLS config".

   • "TLS enabled" confirms that the SSL/HTTPS setup was successful.
   • "Invalid TLS config" signifies that there was a problem with the configuration. If you encounter this, double-check the certificate and key files, their names, and their location.

4. Depending on your SSL certificate source, you may need to do the following:

   • Self-signed certificate: If you're using a self-signed certificate, you'll need to manually add it to your browser's trust store to avoid security warnings.

   • Publicly trusted certificate (e.g., Let's Encrypt): If your certificate comes from a publicly trusted Certificate Authority (CA) such as Let's Encrypt, you should remove the existing Lodestone Core instance from your dashboard and re-add it using its domain name.