1
1
mirror of https://github.com/kokonect-link/cherrypick synced 2024-12-05 10:18:38 +09:00
cherrypick/docs/setup.en.md
rinsuki 350310c4c2 ドキュメントのNode.js最小バージョンを修正 (#5700)
@typescript-eslint/parserが11.10.1以上じゃないと入らない

> error @typescript-eslint/parser@2.3.3: The engine "node" is incompatible with this module. Expected version "^8.10.0 || ^10.13.0 || >=11.10.1". Got "11.7.0"

https://github.com/syuilo/misskey/runs/274115939
2020-01-09 17:46:29 +09:00

3.7 KiB

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.

Japanese version also available - 日本語版もあります


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 📦

Optional
  • Yarn Optional but recommended for security reason. If you won't install it, use npx yarn instead of yarn.
  • Elasticsearch - required to enable the search feature
  • FFmpeg

3. Install Misskey

  1. Connect to misskey user.

    su - misskey

  2. Clone the misskey repo from master branch.

    git clone -b master git://github.com/syuilo/misskey.git

  3. Navigate to misskey directory

    cd misskey

  4. Checkout to the latest release

    git checkout master

  5. Install misskey dependencies.

    yarn

4. Configure Misskey

  1. Copy the .config/example.yml and rename it to default.yml.

    cp .config/example.yml .config/default.yml

  2. 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:

  1. npx node-gyp configure
  2. npx node-gyp build
  3. NODE_ENV=production yarn build

6. Init DB

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

  1. Create a systemd service here

    /etc/systemd/system/misskey.service

  2. 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
    
  3. Reload systemd and enable the misskey service.

    systemctl daemon-reload ; systemctl enable misskey

  4. Start the misskey service.

    systemctl start misskey

You can check if the service is running with systemctl status misskey.

How to update your Misskey server to the latest version

  1. git checkout master
  2. git pull
  3. yarn install
  4. NODE_ENV=production yarn build
  5. yarn migrate
  6. Restart your Misskey process to apply changes
  7. Enjoy

If you encounter any problems with updating, please try the following:

  1. yarn clean or yarn cleanall
  2. Retry update (Don't forget yarn install

If you have any questions or troubles, feel free to contact us!