![]() ![]() If you already have a PostgreSQL database with old schema and contents, you can upgrade it to the new schema. Then, in the ejabberd configuration file, add this line: new_sql_schema: true When creating a new database, use the new schema to create the tables: mysql -u ejabberd_test ejadb < sql/ This is not enabled by default and needs explicit configuration in ejabberd.yml file. This means you can set one single database to serve all the virtual hosts. With the new database schema, all the tables that include the username, have also server_host. The commit also deprecates the following functions: Given that the option was not very well known and understood, it’s not simply deprecated but completely removed. Since we got rid of all bottleneck processes and we have a connection pool for every database, the option is no longer needed and in fact is detrimental: in practice, what you get is just a bunch of overloaded processes in the IQ handlers pool no matter how much you increase the iqdisc value. The option can be used to override configuration options of a particular PubSub node. ![]() Note that the module won’t generate CAPTCHA challenges for messages: they will still be rejected if drop is set to true. The option also implies that option drop is set to true. When the option is set to true, the module will generate CAPTCHA challenges for incoming subscription requests. New ‘captcha’ option for mod_block_strangers The default value is none, which means nothing is whitelisted. It’s an ACL where deny means the message will be rejected (or a CAPTCHA would be generated for a presence), and allow means the sender is whitelisted and the stanza will pass through. The option is supposed to be used when allow_local_users and allow_transports are not enough. New ‘access’ option for mod_block_strangers ![]() it implies that convert option is configured. Note that the option only takes effect when an avatar is about to convert to a different format, i.e. The option takes positive integer values. The option controls how many avatars a user can upload per minute. legacy behavior is emulated: the only reason for this is to maintain backward compatibility with existing deployments. This behavior is considered harmful in the case when it’s desired to multiplex different components on the same port, so, to disable it, set global_routes to false. The option emulates legacy behavior which registers all routes defined in hosts on a component connected. New ‘global_routes’ option for ejabberd_service Note that the option might have a slight performance impact, so use it with care on loaded machines. The option might be useful to protect client software from sophisticated bugs related to XML validation as well as for client developers who want to catch validation errors at an early stage of development. If an error occurs, the packet will be bounced with the corresponding error reason. If set to true, all incoming XML packets are fully validated against known schemas. This is a global option (you cannot set it per domain) and the default is 30 seconds. If the timer fires, the stream is considered as failed and the underlying connection gets closed. The option can be used to specify a period (in seconds) for a stream negotiation to complete. New configuration options New ‘negotiation_timeout’ option ![]() After two months of active development, we’re happy to announce the release of ejabberd 18.03 which includes many improvements, new options, and bugfixes. ![]()
0 Comments
Leave a Reply. |