The server configuration is located in a JSON file at config/local.json and is divided into several sections.
Many of these parameters can be managed directly from the settings screen in the administration panel. This provides a user-friendly interface for adjusting the server configuration without having to manually edit the JSON file.
"environment" : "development"This setting defines the environment in which the application is running. By default, it is set to "development". In this mode, the application does not perform NIP98 authentication checks, making it useful for testing purposes. However, for security reasons, it is crucial to switch this setting to "production" before deploying a server to the public. In "production" mode, the application will enforce NIP98 authentication checks as an additional security measure.
"server": {
"host": "localhost",
"port": 3000,
"pubkey": "",
"secretKey": "",
"tosFilePath" : "resources/tos.md"
}The server configuration includes the host and port on which the server runs. It also includes the pubkey and secretKey for Nostr authentication, and tosFilePath is the path to the terms of service file.
If the pubkey and secretKey do not exist or do not match, the server will automatically generate a new pair of keys upon startup. This ensures that the server always has a valid pair of keys for Nostr authentication, even if the provided keys are missing or incorrect.
This section of the configuration file specifies the modules that are available for use in the application. Each key-value pair within this object represents a module. The key is the name of the module, and the value is a boolean indicating whether the module is enabled (true) or disabled (false).
By enabling or disabling modules in this configuration, you can control which features are available in the application. This allows for a flexible setup where only the necessary modules are active, potentially improving performance and reducing resource usage.
"availableModules": {
"nostraddress" :{
"name": "nostraddress",
"enabled": true,
"path": "/nostraddress",
"methods": ["GET"],
"description": "This module returns the pubkey for a nostraddress name for each domain."
},
"media":{
"name": "media",
"enabled": true,
"path": "/media",
"methods": ["GET","POST","PUT","DELETE"],
"description": "This module handles media uploads, downloads, media tags, etc."
},
"lightning" :{
"name": "lightning",
"enabled": true,
"path": "/lightningaddress",
"methods": ["GET","PUT", "DELETE"],
"description": "This module handles ightning redirections for a nostraddress."
},
"verify" :{
"name": "verify",
"enabled": true,
"path": "/verify",
"methods": ["POST"],
"description": "This module can verify a nostr note integrity and timestamp."
},
"register" : {
"name": "register",
"enabled": true,
"path": "/register",
"methods": ["POST"],
"description": "This module handles usernames creation from trusted pubkeys."
},
"domains" : {
"name": "domains",
"enabled": true,
"path": "/domains",
"methods": ["GET", "PUT"],
"description": "This module handle lists of registered domains and usernames."
},
"admin" : {
"name": "admin",
"enabled": true,
"path": "/admin",
"methods": ["GET","POST"],
"description": "Admin API, reboot, update remove and modify fields, server status, etc."
},
"frontend" : {
"name": "frontend",
"enabled": true,
"path": "/",
"methods": ["GET","POST"],
"description": "This module handles the frontend, login page, register, dashboard, etc."
},
"payments" : {
"name": "payments",
"enabled": false,
"path": "/payments",
"methods": ["POST"],
"description": "This module handles payments, balance, invoices, etc."
}
}"database": {
"host": "127.0.0.1",
"user": "",
"password": "",
"database": "",
"droptables": false
}Database configuration, including the host, username, password, database name, and whether to drop existing tables. The database configuration can also be set through environment variables as shown in the snippet below:
DATABASE_HOST
DATABASE_USER
DATABASE_PASSWORD
DATABASE_DATABASE
"redis": {
"host": "127.0.0.1",
"port": "6379",
"user": "default",
"password": "",
"expireTime": 300
}Redis configuration, including the host, port, username, password, and key expiration time. The Redis configuration can also be set through environment variables as shown in the snippet below:
REDIS_HOST
REDIS_PORT
REDIS_USER
REDIS_PASSWORD
"media" : {
"maxMBfilesize": 100,
"tempPath": "tmp/",
"mediaPath": "media/",
"notFoundFilePath" : "resources/file-not-found.webp",
"allowPublicUploads" : true,
"returnURL" : "",
"transform" : {...}
}The Media files configuration includes settings for maximum file size (in MB), an image file path for when a file is not found, a setting for whether public uploads are allowed, a custom return URL, and settings for media file transformations.
If the returnURL is not defined in the configuration, the application will default to returning https:///media. Here, is the name of the server where the application is hosted. This default URL points to the location where the media files are stored on the server.
"torrent": {
"enableTorrentSeeding": false,
"torrentPort": 6881,
"dhtPort": 6882
}Torrent configuration, including whether torrent seeding is enabled and the ports for Torrent and DHT.Disabled by default
"logger" : {
"minLevel": "5",
"filename": "nostrcheck-api",
"size": "50M",
"interval": "60d",
"compression": "gzip",
"logPath": "logs/"
}Logger configuration, including the minimum log level, log file name, maximum log file size, log rotation interval, compression type, and logs path.
"session" : {
"secret": "",
"maxAge": 2592000000
}The session configuration includes settings for the session secret and the maximum session age.
The secret is a key used to sign the session ID cookie. If it's not specified in the configuration, the application will automatically generate a session secret. This ensures that even if the secret is not explicitly set, the session ID cookie will still be signed, providing an additional layer of security.
The maxAge setting determines the maximum age (in milliseconds) of a session. After this period, the session will expire.
"storage" : {
"type": "local",
"local" : {
"mediaPath": "media/",
"tempPath": "tmp/"
},
"remote" : {
"endpoint": "https://<your_r2_account_id>.r2.cloudflarestorage.com",
"accessKeyId": "<your_r2_access_key_id>",
"secretAccessKey": "<your_r2_secret_access_key>",
"region": "auto",
"s3ForcePathStyle": true,
"bucketName": "your-bucket-name"
}
}The storage configuration includes settings for the storage type and the storage path.
The storage type determines the method of storage used by the application. This could be local file storage, cloud-based storage, or a database. If it's not specified in the configuration, the application will default to using local file storage. This ensures that even if the storage type is not explicitly set, the application will still have a method to store and retrieve data.
The storage path is the location where the data will be stored. This could be a directory on the local machine for file storage, a URL for cloud-based storage, or a database name for database storage. If it's not specified in the configuration, the application will default to a standard location. This ensures that even if the storage path is not explicitly set, the application will know where to store and retrieve data.
"payments": {
"paymentProvider": "nwc",
"LNAddress": "quentintaranpino@getalby.com",
"satoshi": {
"mediaMaxSatoshi": "5001",
"registerMaxSatoshi": "9900"
},
"paymentProviders": {
"lnbits": {
"nodeUrl": "http://localhost:5000",
"readKey": "123345235235"
},
"nwc": {
"url": "nostr+walletconnect://..."
}
},
"checkInterval": 10000,
"invoicePaidInterval": "60",
"allowUnpaidFiles": true,
"allowUnpaidUploads": true,
"sendMessageToPubkey": false
},
The payments configuration includes settings for the payment provider, maximum payment amounts, and provider-specific settings.
The paymentProvider field specifies the service used to process payments. If it's not specified in the configuration, the application will need to have a default provider or handle the lack of a provider appropriately.
The satoshi field contains settings for maximum payment amounts for different types of transactions. For example, mediaMaxSatoshi could be the maximum amount of satoshis that a user can pay for a media file, and registerMaxSatoshi could be the maximum amount for user registration.
The LNAddress field is the Lightning Network address for receiving payments.
This configuration ensures that the application has the necessary information to process payments, set payment limits, and interact with the chosen payment provider.
If the configuration file does not exist, the application will automatically generate a new one with the following structure:
{
"environment" : "development",
"server": {
"host": "localhost",
"port": 3000,
"pubkey": "",
"secretKey": "",
"tosFilePath" : "resources/tos.md",
"availableModules": {
"nostraddress" :{
"name": "nostraddress",
"enabled": true,
"path": "/nostraddress",
"methods": ["GET"],
"description": "This module returns the pubkey for a nostraddress name for each domain."
},
"media":{
"name": "media",
"enabled": true,
"path": "/media",
"methods": ["GET","POST","PUT","DELETE"],
"description": "This module handles media uploads, downloads, media tags, etc."
},
"lightning" :{
"name": "lightning",
"enabled": true,
"path": "/lightningaddress",
"methods": ["GET","PUT", "DELETE"],
"description": "This module handles ightning redirections for a nostraddress."
},
"verify" :{
"name": "verify",
"enabled": true,
"path": "/verify",
"methods": ["POST"],
"description": "This module can verify a nostr note integrity and timestamp."
},
"register" : {
"name": "register",
"enabled": true,
"path": "/register",
"methods": ["POST"],
"description": "This module handles usernames creation from trusted pubkeys."
},
"domains" : {
"name": "domains",
"enabled": true,
"path": "/domains",
"methods": ["GET", "PUT"],
"description": "This module handle lists of registered domains and usernames."
},
"admin" : {
"name": "admin",
"enabled": true,
"path": "/admin",
"methods": ["GET","POST"],
"description": "Admin API, reboot, update remove and modify fields, server status, etc."
},
"frontend" : {
"name": "frontend",
"enabled": true,
"path": "/",
"methods": ["GET","POST"],
"description": "This module handles the frontend, login page, register, dashboard, etc."
},
"payments" : {
"name": "payments",
"enabled": false,
"path": "/payments",
"methods": ["POST"],
"description": "This module handles payments, balance, invoices, etc."
}
}
},
"database": {
"host": "127.0.0.1",
"user": "",
"password": "",
"database": "",
"droptables": false
},
"redis": {
"host": "127.0.0.1",
"port": "6379",
"user": "default",
"password": "",
"expireTime": 300
},
"media" : {
"maxMBfilesize": 100,
"tempPath": "tmp/",
"mediaPath": "media/",
"notFoundFilePath" : "resources/file-not-found.webp",
"allowPublicUploads" : true,
"returnURL" : "",
"transform" : {
"enabled": true
"media":{
"undefined" : {
"width" : "640",
"height" : "480"
},
"image" : {
"width" : "1280",
"height" : "960"
},
"video" : {
"width" : "720",
"height" : "480"
}
},
"avatar" : {
"width" : "400",
"height" : "400"
},
"banner" : {
"width" : "900",
"height" : "300"
}
}
},
"torrent": {
"enableTorrentSeeding": false,
"torrentPort": 6881,
"dhtPort": 6882
},
"logger" : {
"minLevel": "5",
"filename": "nostrcheck-api",
"size": "50M",
"interval": "60d",
"compression": "gzip",
"logPath": "logs/"
},
"session" : {
"secret": "",
"maxAge": 2592000000
}
}This automatic generation of a configuration file ensures that the application can run with default settings even if a configuration file is not provided.