Deployment
Authored by briiian · Last updated Before opening up your self-hosted Cardinal apps to real traffic, you should take a moment to review the best practices outlined on this page to ensure that your setup is ready for production.
Self-hosted setups come in many shapes and sizes, so this is a general purpose guide meant to apply to all types of configurations.
🔸 Orange: Important
🔹 Blue: Recommended
Security
🔸 Disable the guest account
The guest account is an admin without a password. You should disable it before sharing your Media Server with anyone that you don't trust with full admin access.
🔸 Enable SECURE_COOKIES if you are using HTTPS
If you are accessing your Media Server over HTTPS, enabling SECURE_COOKIES will allow your Media Server to issue cookies with stricter security settings. More information on how sessions work is available on the Media Server → Accounts page.
🔸 Use good account security practices
Use a password manager to generate a strong and unique password for each of your accounts, whether they are local accounts or Cardinal accounts. For cloud accounts, enable MFA.
🔸 Only join servers that you trust
You just never know, man.
Performance
🔹 Use fast storage
Installing Cardinal Media Server on an SSD will result in much faster day-to-day speeds than if it was installed on a regular hard drive.
🔹 Enable SQLITE_WAL
If you are using SQLite, have a look at the SQLITE_WAL environment variable to see if you can enable it.
🔹 Use the recommended folder structures
The indexing guide outlines the best way to structure your media files in your folders for each media type. Using the recommended structures will result in better indexing results.
Was this article helpful?