"Fossies" - the Fresh Open Source Software Archive

Member "jitsi-meet-5079/doc/example-config-files/prosody.cfg.lua.example" (17 Jun 2021, 8496 Bytes) of package /linux/misc/jitsi-meet-5079.tar.gz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 -- Prosody XMPP Server Configuration
    2 --
    3 -- Information on configuring Prosody can be found on our
    4 -- website at http://prosody.im/doc/configure
    5 --
    6 -- Tip: You can check that the syntax of this file is correct
    7 -- when you have finished by running: prosodyctl check config
    8 -- If there are any errors, it will let you know what and where
    9 -- they are, otherwise it will keep quiet.
   10 --
   11 -- Good luck, and happy Jabbering!
   12 
   13 
   14 ---------- Server-wide settings ----------
   15 -- Settings in this section apply to the whole server and are the default settings
   16 -- for any virtual hosts
   17 
   18 -- This is a (by default, empty) list of accounts that are admins
   19 -- for the server. Note that you must create the accounts separately
   20 -- (see http://prosody.im/doc/creating_accounts for info)
   21 -- Example: admins = { "user1@example.com", "user2@example.net" }
   22 admins = { }
   23 daemonize = true
   24 cross_domain_bosh = true;
   25 component_ports = { 5347 }
   26 --component_interface = "192.168.0.10"
   27 
   28 -- Enable use of libevent for better performance under high load
   29 -- For more information see: http://prosody.im/doc/libevent
   30 --use_libevent = true
   31 
   32 -- This is the list of modules Prosody will load on startup.
   33 -- It looks for mod_modulename.lua in the plugins folder, so make sure that exists too.
   34 -- Documentation on modules can be found at: http://prosody.im/doc/modules
   35 modules_enabled = {
   36 
   37     -- Generally required
   38     "roster"; -- Allow users to have a roster. Recommended ;)
   39     "saslauth"; -- Authentication for clients and servers. Recommended if you want to log in.
   40     "tls"; -- Add support for secure TLS on c2s/s2s connections
   41     "dialback"; -- s2s dialback support
   42     "disco"; -- Service discovery
   43     "posix"; -- POSIX functionality, sends server to background, enables syslog, etc.
   44 
   45     -- Not essential, but recommended
   46     "private"; -- Private XML storage (for room bookmarks, etc.)
   47     "vcard"; -- Allow users to set vCards
   48 
   49     -- These are commented by default as they have a performance impact
   50     --"privacy"; -- Support privacy lists
   51     "compression"; -- Stream compression (requires the lua-zlib package installed)
   52 
   53     -- Nice to have
   54     "version"; -- Replies to server version requests
   55     "uptime"; -- Report how long server has been running
   56     "time"; -- Let others know the time here on this server
   57     "ping"; -- Replies to XMPP pings with pongs
   58     "pep"; -- Enables users to publish their mood, activity, playing music and more
   59     "register"; -- Allow users to register on this server using a client and change passwords
   60 
   61     -- Admin interfaces
   62     "admin_adhoc"; -- Allows administration via an XMPP client that supports ad-hoc commands
   63     --"admin_telnet"; -- Opens telnet console interface on localhost port 5582
   64 
   65     -- HTTP modules
   66     "bosh"; -- Enable BOSH clients, aka "Jabber over HTTP"
   67     --"http_files"; -- Serve static files from a directory over HTTP
   68 
   69     -- Other specific functionality
   70     --"groups"; -- Shared roster support
   71     --"announce"; -- Send announcement to all online users
   72     --"welcome"; -- Welcome users who register accounts
   73     --"watchregistrations"; -- Alert admins of registrations
   74     --"motd"; -- Send a message to users when they log in
   75     --"legacyauth"; -- Legacy authentication. Only used by some old clients and bots.
   76 
   77     -- jitsi
   78     "smacks";
   79     "carbons";
   80     "mam";
   81     "lastactivity";
   82     "offline";
   83     "pubsub";
   84     "adhoc";
   85     "websocket";
   86     "http_altconnect";
   87 }
   88 
   89 -- These modules are auto-loaded, but should you want
   90 -- to disable them then uncomment them here:
   91 modules_disabled = {
   92     --"offline"; -- Store offline messages
   93     --"c2s"; -- Handle client connections
   94     --"s2s"; -- Handle server-to-server connections
   95 }
   96 
   97 -- Disable account creation by default, for security
   98 -- For more information see http://prosody.im/doc/creating_accounts
   99 allow_registration = false
  100 
  101 -- These are the SSL/TLS-related settings. If you don't want
  102 -- to use SSL/TLS, you may comment or remove this
  103 ssl = {
  104     key = "/etc/prosody/certs/localhost.key";
  105     certificate = "/etc/prosody/certs/localhost.crt";
  106 }
  107 
  108 -- Force clients to use encrypted connections? This option will
  109 -- prevent clients from authenticating unless they are using encryption.
  110 
  111 --c2s_require_encryption = true
  112 
  113 -- Force certificate authentication for server-to-server connections?
  114 -- This provides ideal security, but requires servers you communicate
  115 -- with to support encryption AND present valid, trusted certificates.
  116 -- NOTE: Your version of LuaSec must support certificate verification!
  117 -- For more information see http://prosody.im/doc/s2s#security
  118 
  119 --s2s_secure_auth = false
  120 
  121 -- Many servers don't support encryption or have invalid or self-signed
  122 -- certificates. You can list domains here that will not be required to
  123 -- authenticate using certificates. They will be authenticated using DNS.
  124 
  125 --s2s_insecure_domains = { "gmail.com" }
  126 
  127 -- Even if you leave s2s_secure_auth disabled, you can still require valid
  128 -- certificates for some domains by specifying a list here.
  129 
  130 --s2s_secure_domains = { "jabber.org" }
  131 
  132 -- Required for init scripts and prosodyctl
  133 pidfile = "/var/run/prosody/prosody.pid"
  134 
  135 -- Select the authentication backend to use. The 'internal' providers
  136 -- use Prosody's configured data storage to store the authentication data.
  137 -- To allow Prosody to offer secure authentication mechanisms to clients, the
  138 -- default provider stores passwords in plaintext. If you do not trust your
  139 -- server please see http://prosody.im/doc/modules/mod_auth_internal_hashed
  140 -- for information about using the hashed backend.
  141 
  142 authentication = "internal_hashed"
  143 
  144 -- Select the storage backend to use. By default Prosody uses flat files
  145 -- in its configured data directory, but it also supports more backends
  146 -- through modules. An "sql" backend is included by default, but requires
  147 -- additional dependencies. See http://prosody.im/doc/storage for more info.
  148 
  149 --storage = "sql" -- Default is "internal"
  150 
  151 -- For the "sql" backend, you can uncomment *one* of the below to configure:
  152 --sql = { driver = "SQLite3", database = "prosody.sqlite" } -- Default. 'database' is the filename.
  153 --sql = { driver = "MySQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
  154 --sql = { driver = "PostgreSQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
  155 
  156 -- Logging configuration
  157 -- For advanced logging see http://prosody.im/doc/logging
  158 log = {
  159     info = "/var/log/prosody/prosody.log"; -- Change 'info' to 'debug' for verbose logging
  160     error = "/var/log/prosody/prosody.err";
  161     "*syslog";
  162 }
  163 
  164 ----------- Virtual hosts -----------
  165 -- You need to add a VirtualHost entry for each domain you wish Prosody to serve.
  166 -- Settings under each VirtualHost entry apply *only* to that host.
  167 
  168 --VirtualHost "localhost"
  169 
  170 VirtualHost "jitsi.example.com"
  171     -- enabled = false -- Remove this line to enable this host
  172     authentication = "anonymous"
  173     -- Assign this host a certificate for TLS, otherwise it would use the one
  174     -- set in the global section (if any).
  175     -- Note that old-style SSL on port 5223 only supports one certificate, and will always
  176     -- use the global one.
  177     ssl = {
  178         key = "/var/lib/prosody/jitsi.example.com.key";
  179         certificate = "/var/lib/prosody/jitsi.example.com.crt";
  180     }
  181 
  182     c2s_require_encryption = false
  183 
  184 VirtualHost "auth.jitsi.example.com"
  185     ssl = {
  186         key = "/var/lib/prosody/auth.jitsi.example.com.key";
  187         certificate = "/var/lib/prosody/auth.jitsi.example.com.crt";
  188     }
  189     authentication = "internal_hashed"
  190 
  191 ------ Components ------
  192 -- You can specify components to add hosts that provide special services,
  193 -- like multi-user conferences, and transports.
  194 -- For more information on components, see http://prosody.im/doc/components
  195 
  196 ---Set up a MUC (multi-user chat) room server on conference.example.com:
  197 --Component "conference.example.com" "muc"
  198 
  199 -- Set up a SOCKS5 bytestream proxy for server-proxied file transfers:
  200 --Component "proxy.example.com" "proxy65"
  201 
  202 ---Set up an external component (default component port is 5347)
  203 --
  204 -- External components allow adding various services, such as gateways/
  205 -- transports to other networks like ICQ, MSN and Yahoo. For more info
  206 -- see: http://prosody.im/doc/components#adding_an_external_component
  207 --
  208 --Component "gateway.example.com"
  209 --    component_secret = "password"
  210 
  211 Component "conference.jitsi.example.com" "muc"
  212 
  213 Component "jitsi-videobridge.jitsi.example.com"
  214     component_secret = "IfGaish6"