puniko/FoundKey
1
0
Fork 0
forked from FoundKeyGang/FoundKey
Code Issues Pull requests Projects Releases Packages Wiki Activity

docs: Update install guide to use tag-merge strategy (#117)

Browse source 
Adapted from @toast 's guide: https://mk.toast.cafe/notes/93o9n4tfsi

Reviewed-on: FoundKeyGang/FoundKey#117
This commit is contained in:
Norm 2023-03-23 16:34:01 +00:00
parent 7821bbc28d
commit da246ce419
1 changed files with 31 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

47
docs/install.md
View file

@ -38,22 +38,29 @@ Create a separate non-root user to run FoundKey:
adduser --disabled-password --disabled-login foundkey adduser --disabled-password --disabled-login foundkey
``` ```
The following steps will require logging into the `foundkey` user, so do that now.
```sh
su - foundkey
```
## Install FoundKey ## Install FoundKey
1. Login to the `foundkey` user We recommend using a local branch and merging in upstream releases as they get tagged. This allows for easy local customization of your install.
`su - foundkey` First, clone the FoundKey repo:
```sh
git clone https://akkoma.dev/FoundKeyGang/FoundKey
cd FoundKey
```
2. Clone the FoundKey repository Now create your local branch. In this example, we'll be using `toast.cafe` as the local branch name and release `v13.0.0-preview1` as the tag to track. To create that branch:
```sh
git checkout tags/v13.0.0-preview1 -b toast.cafe
```
`git clone --recursive https://akkoma.dev/FoundKeyGang/FoundKey foundkey` Updating will be covered in a later section. For now you'll want to install the dependencies using Yarn:
```sh
3. Navigate to the repository yarn install
```
`cd foundkey`
4. Install FoundKey's dependencies
`yarn install`
## Configure FoundKey ## Configure FoundKey
1. Copy `.config/example.yml` to `.config/default.yml`. 1. Copy `.config/example.yml` to `.config/default.yml`.
@ -185,14 +192,22 @@ rc-service foundkey start
You can check if the service is running with `rc-service foundkey status`. You can check if the service is running with `rc-service foundkey status`.
### Updating FoundKey ### Updating FoundKey
Use git to pull in the latest changes and rerun the build and migration commands: When a new release comes out, simply fetch and merge in the new tag. If you plan on making additional changes on top of that tag, we suggest using the `--squash` option with `git merge`.
```sh
git fetch -t
git merge tags/v13.0.0-preview2
# you are now on the "next" release
```
Now you'll want to update your dependencies and rebuild:
```sh ```sh
git pull
git submodule update --init
yarn install yarn install
# Use build-parallel if your system has 4GB or more RAM and want faster builds # Use build-parallel if your system has 4GB or more RAM and want faster builds
NODE_ENV=production yarn build NODE_ENV=production yarn build
```
Next, run the database migrations:
```sh
yarn migrate yarn migrate
``` ```