Companion itself always runs as a HTTP server, so locally you should use http. Used to build a URL to reference the Companion instance itself, which is used for headers and cookies. server Ĭonfiguration options for the underlying server. See alsoĬOMPANION_REDIS_EXPRESS_SESSION_PREFIX. Will prefix all events with the name provided and a colon. Use a scope for the companion events at the Redis server. redisPubSubScope COMPANION_REDIS_PUBSUB_SCOPE This option can be used in place of redisUrl. In the future, we plan and changing the default to companion: and possibly To know where sess: comes from and it might collide with other apps. If you run a redis with many different apps in the same redis server, it’s hard To be loaded by the browser via Companion. Sessions are used for storing authentication state and for allowing thumbnails Set a custom prefix for redis keys created by This can be used to scale Companion horizontally Setting this to true disables the welcome message shown at /. COMPANION_COOKIE_DOMAIN Īllows you to customize the domain of the cookies created for Express sessions. The port on which to start the standalone server, defaults to 3020. Instance is only allowed to upload to your trusted servers and prevents uploadUrls COMPANION_UPLOAD_URLS Īn allowlist (array) of strings (exact URLs) or regular expressions. Using a secret file means passing an absolute path to a file with any extension, Instances on the same machine, then COMPANION_PORT should be different for
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |