Misskey Setup and Installation Guide
We thank you for your interest in setting up your Misskey server! This guide describes how to install and setup Misskey.
1. Create Misskey user
Running misskey as root is not a good idea so we create a user for that. In debian for exemple :
adduser --disabled-password --disabled-login misskey
2. Install dependencies
Please install and setup these softwares:
Dependencies 📦
- Node.js (16.x)
- PostgreSQL (12.x / 13.x is preferred)
- Redis
Optional
- Yarn Optional but recommended for security reason. If you won't install it, use
npx yarn
instead ofyarn
. - FFmpeg
3. Install Misskey
Connect to the
misskey
usersu - misskey
Clone the Misskey repository
git clone --recursive https://github.com/misskey-dev/misskey.git
Navigate to the repository
cd misskey
Check out the latest release
git checkout master
Install Misskey's dependencies
yarn install
4. Configure Misskey
Copy the
.config/example.yml
and rename it todefault.yml
.cp .config/example.yml .config/default.yml
Edit
default.yml
5. Build Misskey
Build misskey with the following:
NODE_ENV=production yarn build
If you're on Debian, you will need to install the build-essential
, python
package.
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
6. Init DB
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 Misskey, or it could cause problems later. The encoding of the database should be UTF-8.
sudo -u postgres psql create database misskey with encoding = 'UTF8'; create user misskey with encrypted password '{YOUR_PASSWORD}'; grant all privileges on database misskey to misskey; \q
Run the database initialisation
yarn run init
7. That is it.
Well done! Now, you have an environment that run to Misskey.
Launch normally
Just NODE_ENV=production npm start
. GLHF!
Launch with systemd
Create a systemd service here
/etc/systemd/system/misskey.service
Edit it, and paste this and save:
[Unit] Description=Misskey daemon [Service] Type=simple User=misskey ExecStart=/usr/bin/npm start WorkingDirectory=/home/misskey/misskey Environment="NODE_ENV=production" TimeoutSec=60 StandardOutput=syslog StandardError=syslog SyslogIdentifier=misskey Restart=always [Install] WantedBy=multi-user.target
Reload systemd and enable the misskey service.
systemctl daemon-reload ; systemctl enable misskey
Start the misskey service.
systemctl start misskey
You can check if the service is running with systemctl status misskey
.
Launch with OpenRC
Copy the following text to
/etc/init.d/misskey
:#!/sbin/openrc-run name=misskey description="Misskey daemon" command="/usr/bin/npm" command_args="start" command_user="misskey" supervisor="supervise-daemon" supervise_daemon_args=" -d /home/misskey/misskey -e NODE_ENV=\"production\"" pidfile="/run/${RC_SVCNAME}.pid" depend() { need net use logger # alternatively, uncomment if using nginx reverse proxy #use logger nginx }
Set the service to start on boot
rc-update add misskey
Start the Misskey service
rc-service misskey start
You can check if the service is running with rc-service misskey status
.
How to update your Misskey server to the latest version
git checkout master
git pull
git submodule update --init
yarn install
NODE_ENV=production yarn build
yarn migrate
- Restart your Misskey process to apply changes
- Enjoy
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!