5.2 KiB
FoundKey Setup and Installation Guide
This guide will assume that you have administrative rights, either as root or a user with sudo permissions. If you are using a non-root user, prefix the commands with sudo
except when you are logged into the foundkey user with su
.
This guide will also assume you're using Debian or a derivative like Ubuntu. If you are using another OS, you will need to adapt the comamnds and package names to match those that your OS uses.
Create FoundKey user
Running FoundKey as root is not a good idea. Create a separate user to run FoundKey.
adduser --disabled-password --disabled-login foundkey
Install dependencies
FoundKey requires the following packages to run:
Dependencies 📦
- Node.js (16.x/18.x)
- PostgreSQL (12.x minimum; 13.x+ is preferred)
- Redis
The following are needed to compile native npm modules:
- A C/C++ compiler like GCC or Clang
- Build tools like make
- Python (3.x)
Optional
To install the dependiencies on Debian (or derivatives like Ubuntu) you can use the following commands:
curl -fsSL https://deb.nodesource.com/setup_16.x | bash -
apt install build-essential python3 nodejs postgresql redis
# Optional dependencies
apt install ffmpeg
corepack enable # for yarn
Install FoundKey
-
Login to the
foundkey
usersu - foundkey
-
Clone the FoundKey repository
git clone --recursive https://akkoma.dev/FoundKeyGang/FoundKey foundkey
-
Navigate to the repository
cd foundkey
-
Install FoundKey's dependencies
yarn install
Configure FoundKey
-
Copy
.config/example.yml
to.config/default.yml
.cp .config/example.yml .config/default.yml
-
Edit
default.yml
with a text editor- Make sure you set the PostgreSQL and Redis settings correctly.
- Use a strong password for the PostgreSQL user and take note of it since it'll be needed later.
Build FoundKey
Build foundkey with the following:
NODE_ENV=production yarn build
If you're still encountering errors about some modules, use node-gyp:
npx node-gyp configure
npx node-gyp build
NODE_ENV=production yarn build
Setting up the database
Create the appropriate PostgreSQL users with respective passwords, and empty database as named in the configuration file.
Make sure the database connection also works correctly when run from the user that will later run FoundKey, or it could cause problems later. The encoding of the database should be UTF-8.
sudo -u postgres psql
create database foundkey with encoding = 'UTF8';
create user foundkey with encrypted password '{YOUR_PASSWORD}';
grant all privileges on database foundkey to foundkey;
\q
Next, initialize the database:
yarn run init
Running FoundKey
You can either run FoundKey manually or use the system service manager to start FoundKey automatically on startup.
Launching manually
Run NODE_ENV=production npm start
to launch FoundKey manually. To stop the server, use Ctrl-C.
Launch with systemd
Run systemctl --edit --full --force foundkey.service
, and paste the following:
[Unit]
Description=FoundKey daemon
[Service]
Type=simple
User=foundkey
ExecStart=/usr/bin/npm start
WorkingDirectory=/home/foundkey/foundkey
Environment="NODE_ENV=production"
TimeoutSec=60
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=foundkey
Restart=always
[Install]
WantedBy=multi-user.target
Save the file, then enable and start FoundKey.
systemctl enable --now foundkey
You can check if the service is running with systemctl status foundkey
.
Launch with OpenRC
Copy the following text to /etc/init.d/foundkey
:
#!/sbin/openrc-run
name=foundkey
description="FoundKey daemon"
command="/usr/bin/npm"
command_args="start"
command_user="foundkey"
supervisor="supervise-daemon"
supervise_daemon_args=" -d /home/foundkey/foundkey -e NODE_ENV=\"production\""
pidfile="/run/${RC_SVCNAME}.pid"
depend() {
need net
use logger
# alternatively, uncomment if using nginx reverse proxy
#use logger nginx
}
Mark the script as executable and enable the service to start on boot:
chmod +x /etc/init.d/foundkey
rc-update add foundkey
Start the FoundKey service:
rc-service foundkey start
You can check if the service is running with rc-service foundkey status
.
Updating FoundKey
Use git to pull in the latest changes and rerun the build and migration commands:
git pull
git submodule update --init
yarn install
NODE_ENV=production yarn build
yarn migrate
Then restart FoundKey if it's still running.
# Systemd
systemctl restart foundkey
# OpenRC
rc-service foundkey restart
If you encounter any problems with updating, please try the following:
yarn clean
oryarn cleanall
- Retry update (Don't forget
yarn install
)
If you have any questions or troubles, feel free to contact us on IRC: #foundkey
on irc.akkoma.dev
, port 6697
with SSL