Go to file
Élie Michel cfa6db10c7 Make new LDAP options backward compatible
Also draft some kind of plugin system for auth, although it essentially consists in writing a function
and there is no mechanism to automatically fallback from one auth to another
2017-09-03 23:00:23 +02:00
client Merge pull request #1457 from thelounge/xpaw/requestIdleCallback 2017-08-26 20:57:15 +01:00
defaults Make new LDAP options backward compatible 2017-09-03 23:00:23 +02:00
scripts Do not hardcoded vendor bundles in webpack 2017-06-27 12:55:12 +03:00
src Make new LDAP options backward compatible 2017-09-03 23:00:23 +02:00
test Merge pull request #1446 from thelounge/parse-emoji 2017-08-26 20:34:40 +03:00
.editorconfig Use stylelint-config-standard 2017-06-22 11:23:50 +03:00
.eslintignore Webpack 2016-12-27 19:15:30 +02:00
.eslintrc.yml Update to eslint 4 and enforce extra rules 2017-06-19 09:58:29 +03:00
.gitattributes Add gitattributes to normalize line endings 2016-01-24 16:12:08 +02:00
.gitignore Ignore vapid.json generated during tests 2017-08-23 12:36:35 +03:00
.lounge_home Rename new file holding config location for consistency 2017-08-16 00:34:29 -04:00
.npmignore Ignore all dotfiles in npmignore 2017-06-29 12:49:07 +03:00
.npmrc Add .npmrc file; set save-exact to true so packages are installed pinned by default 2017-06-28 21:06:23 -07:00
.nycrc Exclude Webpack config from coverage report 2017-04-19 01:19:11 -04:00
.stylelintrc.yml Use leading-zero notation to get closer to stylelint standard config 2017-08-21 02:22:40 -04:00
.travis.yml Update node versions for travis 2017-05-31 09:49:39 +01:00
appveyor.yml Do not build feature branch with open pull requests on AppVeyor 2017-04-22 16:04:18 +03:00
CHANGELOG.md Add changelog entry for v2.4.0 2017-07-30 18:49:49 -04:00
CONTRIBUTING.md Add a SUPPORT file 2017-08-01 01:41:49 -04:00
index.js Enforce strict mode across all JS files with ESLint 2016-10-09 15:14:02 -04:00
LICENSE Update LICENSE notice to add ours on top of @erming and Shout 2016-02-10 06:20:05 +00:00
package.json chore(package): update npm-run-all to version 4.1.1 2017-08-28 08:33:07 +00:00
README.md Web Push Notifications 2017-08-22 10:54:18 +03:00
SUPPORT.md Add a SUPPORT file 2017-08-01 01:41:49 -04:00
webpack.config.js Fix general spelling errors 2017-08-25 18:02:28 +02:00

The Lounge

Modern web IRC client designed for self-hosting.

#thelounge IRC channel on freenode npm version Travis CI Build Status AppVeyor Build Status Dependencies Status

Overview

  • Modern features brought to IRC. Push notifications, link previews, new message markers, and more bring IRC to the 21st century.
  • Always connected. Remains connected to IRC servers while you are offline.
  • Cross platform. It doesn't matter what OS you use, it just works wherever Node.js runs.
  • Responsive interface. The client works smoothly on every desktop, smartphone and tablet.
  • Synchronized experience. Always resume where you left off no matter what device.

To learn more about configuration, usage and features of The Lounge, take a look at the website.

The Lounge is the official and community-managed fork of Shout, by Mattias Erming.

Installation and usage

The Lounge requires Node.js v4 or more recent.

Run this in a terminal to install (or upgrade) the latest stable release from npm:

[sudo] npm install -g thelounge

When installation is complete, run:

lounge start

For more information, read the documentation, wiki, or run:

lounge --help

Running from source

The following commands install and run the development version of The Lounge:

git clone https://github.com/thelounge/lounge.git
cd lounge
npm install
NODE_ENV=production npm run build
npm start

When installed like this, npm doesn't create a lounge executable. Use npm start -- <command> to run subcommands.

⚠️ While it is the most recent codebase, this is not production-ready! Run at your own risk. It is also not recommended to run this as root.

Development setup

Simply follow the instructions to run The Lounge from source above, on your own fork.

Before submitting any change, make sure to:

  • Read the Contributing instructions
  • Run npm test to execute linters and test suite
  • Run npm run build if you change or add anything in client/js or client/views