//WARNING DO NOT USE THIS CONFIG, USE THE REGULAR EXAMPLE, CANOPY DOES NOT SUPPORT JSONC CONFIGS!
//This file merely exists to help you configure your actual config file
{
    //Display name on the nav bar and a coupla other places
    "instanceName": "Canopy",
    //Scream about exceptions in the console
    "verbose": false,
    //Port to bind to (most linux/unix systems req root for ports below 1000, you should probably use nginx if you want port 80 or 443)
    "port": 8443,
    //Lets the server know it's sitting behind a reverse-proxy
    "proxied": true,
    //Protocol (either HTTP or HTTPS)
    "protocol": "http",
    //Domain the server is available at, used for server-side link generation
    "domain": "localhost",
    //Path to YT-DLP Executable for scraping youtube, dailymotion, and vimeo
    //Dailymotion and Vimeo could work using official apis w/o keys, but you wouldn't have any raw file playback options :P
    "ytdlpPath": "/home/canopy/.local/pipx/venvs/yt-dlp/bin/yt-dlp",
    //Enable to migrate legacy DB and toke files dumped into the ./migration/ directory
    //WARNING: The migration folder is cleared after server boot, whether or not a migration took place or this option is enabled.
    //Keep your backups in a safe place, preferably a machine that DOESN'T have open inbound ports exposed to the internet/a publically accessible reverse proxy!
    "migrate": false,
    //Drops all legacy tokes out of the statistics file since doing so manually from mongosh is a lot of typing out obnoxious parentha-glyphics. 
    //Requires migration to be disabled before it takes effect.
    //WARNING: this does NOT affect user toke counts, migrated or otherwise. Use carefully!
    "dropLegacyTokes": false,
    //Enters the server into debug mode, allows specific commands to be emitted from the client-side dev console
    //Usually to get the server to dump some sort of internal data for debugging purposes.
    //Obviously, this means enabling this can have some gnar implications.
    //Probably don't enable this on your production server unless you REALLY REALLY have to, and you probably don't.
    "debug": false,
    //Server Secrets
    //Be careful with what you keep in secrets, you should use special chars, but test your deployment, as some chars may break account registration
    //An update to either kill the server and bitch about the issue in console is planned so it's not so confusing for new admins
    "secrets":{
        //Password secret used to pepper password hashes
        "passwordSecret": "CHANGE_ME",
        //Password secret used to pepper rememberMe token hashes
        "rememberMeSecret": "CHANGE_ME",
        //Session secret used to secure session keys
        "sessionSecret": "CHANGE_ME",
        //Altacha secret used to generate altcha challenges
        "altchaSecret": "CHANGE_ME",
        //IP Secret used to pepper IP Hashes
        "ipSecret": "CHANGE_ME"
    },
    //SSL cert and key locations
    "ssl":{
        "cert": "./server.cert",
        "key": "./server.key"
    },
    //DB configuration
    "db":{
        "address": "127.0.0.1",
        "port": "27017",
        "database": "canopy",
        "user": "canopy",
        "pass": "CHANGE_ME"
    },
    //maintainence email configuration
    "mail":{
        "host": "mail.42069.weed",
        "port": 465,
        "secure": true,
        "address": "toke@42069.weed",
        "pass": "CHANGE_ME"
    },
    //Fills the 'about ${instanceName}' section on the /about page, lets users know about your specific instance
    "aboutText":"<a href=\"https://ourfore.st/\">ourfore.st</a> is the one and only original canopy instance. Setup, ran, and administered by rainbownapkin herself. This site exists to provide a featureful, preformant, and comfy replacement for the TTN community."
}