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

Fix numbering <_<
ci/woodpecker/push/woodpecker Pipeline was successful Details
ci/woodpecker/pr/woodpecker Pipeline was successful Details

Rin 2022-11-21 21:27:58 +11:00
parent 5928dec1f5
commit 8f59e1a853
Signed by: Rin
GPG Key ID: 0C8733C13A7E1293
1 changed files with 13 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
SETUP.md
View File

@ -38,29 +38,27 @@ update your groups.
2. Run `sudo mkdir /run/postgresql` to create said folder if it doesn't exist. 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. 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. 4. Run `sudo chmod g+w /run/postgresql` to allow `postgres` group members to write to the folder.
1. Navigate to the root of this repo. 5. 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'`. 6. Set up a local DB cluster with `pg_ctl -D data/postgres15 initdb -o '-U mastodon --auth-host=trust'`.
3. Run it with `pg_ctl -D data/postgres15 start`. 7. Run it with `pg_ctl -D data/postgres15 start`.
4. Run `bundle config set --local path 'vendor/bundle`. This will store the all the ruby gems locally so that we can 8. 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. avoid interfering with system config.
5. Run `bundle install`. 9. Run `bundle install`.
6. Run `yarn install`. 10. Run `yarn install`.
1. Run `export $(grep -v '^#' .env.dev | xargs)` to source in our dev vars. You may want to alias this. 11. Run `export $(grep -v '^#' .env.dev | xargs)` to source in our dev vars. You may want to alias this.
7. Run `bundle exec rake db:setup`. If this fails, you can use `bundle exec rake db:reset` to forcibly regenerate it. 12. Run `bundle exec rake db:setup`. If this fails, you can use `bundle exec rake db:reset` to forcibly regenerate it.
## Running Mastodon ## Running Mastodon
To make our lives easier, we'll use `foreman` to run the site, so use `gem install foreman` to get that going. 1. To make our lives easier, we'll use `foreman` to run the site, so use `gem install foreman`.
2. Run `export RAILS_ENV=development` and `export NODE_ENV=development`.
Then:
1. Run `export RAILS_ENV=development` and `export NODE_ENV=development`.
a. Put these in your shell's .rc, or a script you can source if you want to skip this step in the future. a. Put these in your shell's .rc, or a script you can source if you want to skip this step in the future.
2. Run `bundle exec rake assets:precompile`. 3. Run `bundle exec rake assets:precompile`.
a. If this explodes, complaining about `Hash`, you'll need to `export NODE_OPTIONS=--openssl-legacy-provider`. Same a. If this explodes, complaining about `Hash`, you'll need to `export NODE_OPTIONS=--openssl-legacy-provider`. Same
deal as the above. deal as the above.
b. After doing this, you will need to `bundle exec rake assets:clobber` and then re-run b. After doing this, you will need to `bundle exec rake assets:clobber` and then re-run
`bundle exec rake assets:precompile`. `bundle exec rake assets:precompile`.
3. Run `foreman start` 4. Run `foreman start`
# Updates/Troubleshooting # Updates/Troubleshooting