Would live at http://thelounge.chat/docs/guides/ldap

This is not an issue but a "nice to have" feature.

The ability to hide the server's list on the left, the same way we can hide the nicknames list on the right.

Either we should update links to include last slash, or change it up so /docs actually loads without redirecting.

lounge is deprecated in CLI, it is recommended to use thelounge. Documentation should be changed to reflect that.

I believe it's more common to set it up on the root folder.

We can leave a note on that page that lounge can also be put in a subfolder.

Would live at http://thelounge.chat/docs/guides/identd-and-oident

oidentd: https://wiki.znc.in/Identfile#Using_identfile_with_oidentd

I have come to this client from Irssi, and when a user in a query with yourself, if they change nicks the server follows that change and update see here for the the specific c file for how it is handled.

It would be nice to see this added, I have little to no (node)js experience at all or I'd do it myself.

In trying to install The Lounge, I came across the Community page which I noticed had some bad links to other people's tutorials.

I ended up writing my own which tries to provide step-by-step instructions on how to install The Lounge on Ubuntu if anyone is interested or if you'd like to link to it.

• Depends on OS/Browser
• New Chrome versions require HTTPS (with trusted cert) on common port (443, 8443, maybe others?)

Things have changed on themes, and they're going to change a bit more after thelounge/thelounge#562 is merged, so we should update them after that.

system is not supported by certbot-auto anymore,so this method is no longer valid

Now that the navbar is sticky, linking to an anchor partially cuts it.

Something like https://stackoverflow.com/questions/10732690/offsetting-an-html-anchor-to-adjust-for-fixed-header

Would live at http://thelounge.chat/docs/guides/webirc

• See https://kiwiirc.com/docs/webirc
• See https://ircv3.net/specs/extensions/webirc.html
• Need to make clear that: 1) This needs collaborating with the IRC network; 2) config is per hostname
• You might not need it

Would live at http://thelounge.chat/docs/guides/znc

Point out that you might need to use ZNC at all.

Since our configuration file is technically a javascript file, escape sequences apply for \ character. On windows you have to specify paths with \ and thus your config has to contain paths like C:\\Users\\etc\\

Also explain that ~ can be used to expand to home path (even on Windows!)

Extracted from #84.

Issue: to be tagged as documentation

I am looking myself into creating a full guide for windows users that might feel left out a little on how to get the lounge set up from start to finish.

This guide will fully support:

• Windows 10, Windows 11 and Server 64 Bit OS installations.
• Batch script to install the core automatically.
• A simple batch script to start the service once fully installed.
• A manual way on how to install it, section by section.

Has anyone actually wanted to get the lounge up and running on windows OS
.. or failed or would like to know more information about it?

At the moment, version x.y.z gets fetched from GitHub tags. It should get fetched from npm, which is where we officially publish our releases.

We should suggest installing released versions.

We wouldn't want search engines to accidentally index that.

I presume we can detect the branch name when netlify is deploying, and change robots.txt into a template which put this in robots:

User-agent: *
Disallow: /

Configuring a third-party service to display Jekyll build error messages

This is a spin-off of #9. A new item could be added to the landing page, explaining why the fact it's community supported matters.

First try:

# Community supported

The development of TheLounge is made by a growing and dedicated community of people.
We try our best to be as friendly as possible and welcome any contributions.
(The Lounge is a fork of Shout, you can read more about it here [link]).

an option to allow users to create an account for themselves

The install doc for Ubuntu and Debian says to install Node.js with:

sudo apt-get -y install nodejs-legacy npm

On Debian Jessie, nodejs-legacy is in v0.10. It goes to v4.x in Stretch only, which will not be here before a year.

Same with Ubuntu Trusty Tahr, the current LTS and the following version, Wily Werefolf. It's in v4.x only since the last version, Xenial Xerus, released 2 months ago.

Considering we are dropping support for Node.js v0.10, we should probably specify in the doc that, unless people are running Debian Stretch or Ubuntu Xenial Xerus, they should be installing Node through Nodesource or whatever instead of apt-get. Any suggestions? (Ping @JocelynDelalande, it's been a while 😄).

Such as https://github.com/wooorm/remark-lint

http://nginx.org/en/docs/http/websocket.html
https://stackoverflow.com/questions/27526281/websockets-and-apache-proxy-how-to-configure-mod-proxy-wstunnel

Probably need to write some extra information about what the client is, what IRC is and stuff like that.

Also schema.org markup should improve some things.

So that we can do this: https://sarathlal.com/add-meta-description-in-jekyll-posts/

Hi!

I'm missing an example of how the config.js file is structured.

I read "Start by locating the config.js file in the configuration folder, which depends on how you installed The Lounge." but I am using the Docker image so I don't have a config.js anywhere.

I've created a Dockerfile with:

FROM thelounge/thelounge

ADD config.js /var/opt/thelounge/

I would expect there to be a minimal example of the complete config.js e.g. (not sure if this is correct)

module.exports = {
  // options here
}

This way it's very clear what the file should look like.

gr,

Tom

Starting May 1st, 2016, GitHub Pages will only support kramdown, Jekyll's default Markdown engine.

From https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0.

(At least on my Nexus 4)

• "The Lounge" appears on 2 lines
• "Documentation" does not show up in portrait mode

While trying to configure the default HOME location, I noticed the config that's autogenerated to ~/.lounge/config.js is missing the home option that's specified in the config docs.

It's unclear to me what the desired behaviour is. Is this option deprecated and the docs are outdated? Or are the docs correct and the option should be included in the config?

Would live at http://thelounge.chat/docs/guides/sasl

This is to be done after the documentation revamp.

There's practically not a lot of code, and we can easily rewrite it without using any libraries.

In _docs/getting_started/install.md, the section titled "Ubuntu / Debian" suggests using sudo apt-get -y install nodejs-legacy npm.

On Debian stable, nodejs == nodejs-legacy, which is version 0.10.29. Lounge does not run on node 0.10.29. This does not affect Debian testing, where nodejs-legacy is 4.x (4.6.1 right now) and is thus usable.

The instructions for Debian stable should recommend manually installing node 4.x (or above? Not sure how far up it goes).

Since it has an absolute position to the left of the headers, it can overflow out of view.

Would live at http://thelounge.chat/docs/guides/hexip

• Requires support from the server

Someone wrote a documentation about setting up HTTPS for The Lounge with self-signed certificates: https://nertant.com/2016/03/12/enabling-https-ssl-connection-with-the-lounge-self-hosted-irc-client/

Similarly, @YaManicKill made a wiki page some time ago about setting up Let's Encrypt certificates: https://github.com/thelounge/lounge/wiki/Enable-HTTPS-with-Let's-Encrypt

We should probably document this properly and "officially" in this repository instead.

We might want to answer the following questions first:

• Do we want to document about self-signed certificates? Actual CA-approved certificates? Both?
• Do we use Let's Encrypt as an example (therefore, implicitly recommending it) or assume reader comes with their own certificate?
• Where do we locate this in the docs?

This is a reminder for myself to add this to the new documentation.

In the meantime, I'll mark it as deprecated on the current website, like we did for #61.