No description
Find a file
Reto Brunner fd50c6372e Work around node bug
node-gyp or node have a bug that prevents building with "text file busy"
if the kernel is too fast, so we have to disable IO_URING support. This
is cleary a hack and needs to be removed as soon as possible
https://github.com/nodejs/node/issues/48444 is the necro bumped thread
originally from docker
2024-05-18 13:22:18 +02:00
.SRCINFO Work around node bug 2024-05-18 13:22:18 +02:00
LICENSE Fix license template 2017-10-14 12:05:04 +03:00
Makefile v4.4.3 2024-04-06 14:15:34 +02:00
PKGBUILD Work around node bug 2024-05-18 13:22:18 +02:00
README.md Update repository link 2018-10-28 18:03:49 +02:00
system.service Revert split config/data dirs 2018-12-26 09:05:20 +01:00
sysusers.d Remove install file and split config/data dirs 2018-12-25 14:09:14 +01:00
tmpfiles.d use yarn to install, with the lockfile 2022-04-06 22:05:58 +02:00
user.service Added environment variable 2018-11-09 10:48:04 +01:00

Arch Linux package for The Lounge

This is a clone of the repository already available on the AUR.

This repository is to be used to track Arch Linux's specific issues with this package and allow users to contribute to it.

Installation

Please follow the usual Arch Linux documentation to install this package from the AUR either manually or using your favorite AUR helper. These instructions are only provided as a quick example, but as typical with Arch Linux you are strongly encouraged to read the approprite documentation.

Manually

$ git clone https://github.com/thelounge/thelounge-archlinux.git
$ cd arch-lounge
$ # optional: select your release (experimental, master, stable)
$ git checkout stable
$ makepkg
# pacman -U thelounge-*.pkg.*

With an AUR helper

with pacaur:

$ pacaur -aS thelounge

or with yaourt:

$ yaourt -aS thelounge

Configuration

The default system-wide documentation file is located at /etc/thelounge/config.js. Please note that user profiles and their IRC passwords are also stored there (moving to /var/lib/thelounge is planned but not yet done), so the directory is only readable by the thelounge user.

Running

The Lounge provides both a system-wide and per-user systemd unit.

System

Simply enable the thelounge.service unit, and your server should be up and running:

# systemctl enable --now thelounge.service

User

If you do not want to run the software system-wide, or host multiple users that wish to host their own instance of The Lounge, it can also be launched per user:

$ systemctl --user enable --now thelounge.service

Please note that for The Lounge to start on boot in this scenario, you will also require to have lingering enabled for this user:

# loginctl enable-linger $username