prosody / homebrew-prosody

The Prosody XMPP server
http://prosody.im
MIT License
9 stars 10 forks source link

Missing .dist sample #15

Open seanbethard opened 6 months ago

seanbethard commented 6 months ago

It's missing or it's good at hiding.

It is recommended to use the configuration file provided with the packages for your platform, if possible, as they may contain ready-configured default options specific to your platform.

prosody (stable)> prosody --help

prosody [ -D | -F ] [ --config /path/to/prosody.cfg.lua ]
  -D, --daemonize       Run in the background
  -F, --no-daemonize    Run in the foreground
  --config FILE         Specify config file

prosody (stable)> touch ~/.prosody prosody (stable)> prosody --config ~/.prosody

Prosody was unable to find the configuration file.
We looked for: ~/.prosody
*A SAMPLE CONFIG FILE IS INCLUDED IN THE PROSODY DOWNLOAD CALLED* prosody.cfg.lua.dist
Copy or rename it to prosody.cfg.lua and edit as necessary.
More help on configuring Prosody can be found at https://prosody.im/doc/configure
Good luck!
Zash commented 6 months ago

https://hg.prosody.im/trunk/file/0.12/prosody.cfg.lua.dist should have been installed as prosody.cfg.lua in (etc+"prosody").

The config file needs to have a .lua file ending, .prosody is not enough. Not sure what you expect to happen if you hand Prosody an empty file anyway.

seanbethard commented 6 months ago

Thanks for following up. I'm not sure what you mean by etc+"prosody" but I don't see anything in etc or Cellar on 14.2.1.

I expect that my new config file is recognized. I expect the error above to be gone or to see a different error about an issue with the config file that I specified with --config, such as an incorrect file extension.

Zash commented 6 months ago

This configure argument specifies where it puts the config file, but I have no idea what that does. https://github.com/prosody/homebrew-prosody/blob/e55d4e5bfaf2cd6886eeeca0e6b101304c0784f9/prosody.rb#L33

prosodyctl about should give you all the relevant paths and other information.

Seems there's no error for incorrect file extension, not that there's more than one option. This is the wrong issue tracker for that tho.