| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
This ensures no new clients can start connecting during shutdown
|
| |
|
|
|
|
| |
To allow running things in it.
|
| |
|
| |
|
|
|
|
| |
The more compact these are, the better
|
|
|
|
|
| |
Parsing --flags puts it into 'opts', so --outdated wasn't passed to
luarocks, breaking that functionality
|
|
|
|
|
| |
But then this is the internal API which is weird and unfriendly to
expose externally. Lots of methods to wrap tho ... one day.
|
|
|
|
|
|
| |
There was a separate boolean option to enable TLS before, but it was
merged with the port number option and it seems the typed API interface
got confused.
|
|
|
|
| |
The inet_ntop binding was added in 8b612ec00e4a and included in 0.11.0
|
|
|
|
| |
Less code!
|
|
|
|
|
| |
After a survey of ACME clients it seems *.crt and *fullchain* should
work for the majority. The rest get to manually copy their files.
|
|
|
|
|
| |
The more modern and user friendly frontend, should be in every supported
version of Debian and Ubuntu by now
|
|
|
|
|
| |
This ensures that registration actually works even if allow_registration
is not enabled.
|
|
|
|
|
| |
This hack is not needed since a9c975a0f113 so can be removed when
included with Prosody.
|
|
|
|
|
|
| |
Usually on port 443 to avoid restrictive firewalls.
Thanks to Holger for discussion
|
|
|
|
|
| |
Much harder to get boolean options wrong than accidentally adding
something unrecognised to a Set.
|
|
|
|
|
|
|
|
| |
The connection events are more appropriate here, where the s2s-created
events happens a bit later or earlier in a sessions lifetime depending
on its direction and for outgoing connections isn't actually the
creation time (which happens immediately after pressing enter, so not
very interesting), but rather closer to the connection time.
|
|
|
|
|
| |
Allows doing things based on connections rather than sessions, which may
have been created before or after.
|
|
|
|
|
| |
RFC 4627 JSON - util.json
RFC 6901 JSON Pointer - util.jsonpointer
|
| |
|
| |
|
|
|
|
| |
It is very often a confusing mistake that leads to support questions
|
|
|
|
| |
Makes it reachable from the shell if nothing else
|
| |
|
|
|
|
| |
Dare to enable by default?
|
|
|
|
|
| |
This seems like the thing to do for time, which is usually divided into
divisors divisible by 60, or multiplied by multiples of 60
|
|
|
|
| |
IANA registry files have XSLT references, which are harmless to ignore.
|
|
|
|
|
| |
These should generally be safe to just ignore, which should be the
default behavior of Expat and LuaExpat
|
|
|
|
|
|
|
| |
http://[::]:5280/ is as sensible as http://*:5280/ so why not
This might be a bit weird when listening no multiple interfaces but not
sure we can really do anything sensible then anyway.
|
|
|
|
|
| |
This might make the global routes less confusing sometimes, or at least
valid URLs instead of http://*:5280/ which doesn't make much sense.
|
|
|
|
| |
Because why not I guess. This mirrors the corresponding luarocks command
|
|
|
|
|
|
|
|
|
|
| |
This way you don't need to set the server URL in the config to use this,
you could just ^C^V an install line from a web page that says
prosodyctl install https://modules.example.com/mod_example.src.rock
Drop the help message in this case since it'll be all messed up by being
given an URL or rock filename.
|
|
|
|
|
| |
Only when the help is shown because of invalid arguments should a
non-zero status code be returned to indicate a problem.
|
|
|
|
| |
Reads nicer, but adds more code. Can always be reverted later I suppose.
|
|
|
|
|
|
|
| |
This way the host-agnostic http://*:5280/ handler is not enabled, but
BOSH can still be used with any local VirtualHost
Ref #1712
|
|
|
|
|
|
|
| |
This way the host-agnostic http://*:5280/ handler is not enabled, but
BOSH can still be used with any local VirtualHost
Ref #1712
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Metadata in modules is added using lines formatted as:
--% key: value
Where key is a valid identifier string, and value is also a string (leading
and trailing whitespace are trimmed during parsing).
The initial supported keys are:
--% requires_core_features: feature1, feature2, ...
--% conflicts_core_features: feature1, feature2. ...
These 'features' map to features reported by the new core.features module.
A benefit of this load-time metadata approach compared to e.g. something like
module:requires()/module:conflicts() is that we can continue to look in module
search paths for a suitable module. Aborting an already-loaded module due to
a version conflict would be too late.
|
| |
|
|
|
|
|
| |
A "feature" is a simple string, and it's expected that we will add to (and
maybe remove from) this list over the course of time.
|
|
|
|
|
| |
Load filters can choose to block the loading of certain files, and optionally
return some metadata about the loaded file.
|
| |
|