treehouse
/
mastodon
19
8
Fork 5
Code Issues 32 Pull Requests Projects 1 Releases Wiki Activity

Update instructions - make everything self contained
ci/woodpecker/pr/woodpecker Pipeline was successful Details
ci/woodpecker/push/woodpecker Pipeline was successful Details

pull/19/head
Rin 2022-11-23 19:31:10 +11:00
parent 842498649d
commit 401a51b67b
Signed by: Rin
GPG Key ID: 0C8733C13A7E1293
1 changed files with 14 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
SETUP.md
View File

@ -35,18 +35,15 @@ In the following instructions, replace USER with your *nix user name.
1. Add yourself to the postgres group with `sudo usermod -a -G postgres USER`. You'll need to log out and back in to
update your groups.
2. Run `sudo mkdir /run/postgresql` to create said folder if it doesn't exist.
3. Run `sudo chown postgres:postgres /run/postgresql` to change the owner to postgres.
4. Run `sudo chmod g+w /run/postgresql` to allow `postgres` group members to write to the folder.
5. Navigate to the root of this repo.
6. Set up a local DB cluster with `pg_ctl -D data/postgres15 initdb -o '-U mastodon --auth-host=trust'`.
7. Run it with `pg_ctl -D data/postgres15 start`.
8. Run `bundle config set --local path 'vendor/bundle`. This will store the all the ruby gems locally so that we can
2. Navigate to the root of this repo.
2. Set up a local DB cluster with `pg_ctl -D data/postgres15 initdb -o '-U mastodon --auth-host=trust'`.
3. Add the line `unix_socket_directories='.'` to `data/postgres15/postgresql.conf`.
4. Run the DB with `pg_ctl -D data/postgres15 start`.
5. Run `bundle config set --local path 'vendor/bundle`. This will store the all the ruby gems locally so that we can
avoid interfering with system config.
9. Run `bundle install`.
10. Run `yarn install`.
11. Run `export $(grep -v '^#' .env.dev | xargs)` to source in our dev vars. You may want to alias this.
12. Run `bundle exec rake db:setup`. If this fails, you can use `bundle exec rake db:reset` to forcibly regenerate it.
6. Run `bundle install`.
7. Run `yarn install`.
8. Run `bundle exec rake db:setup`. If this fails, you can use `bundle exec rake db:reset` to forcibly regenerate it.
## Running Mastodon
@ -70,6 +67,12 @@ Happy to troubleshoot with someone better with Ruby than us >_<'/.
## Webpack Issues
If Webpack compalins about being unable to find some assets or locales:
Try:
1. `rm -rf node_modules`
2. `yarn install`
If this doesn't help, try:
1. yarn add webpack
2. git restore package.json yarn.lock