foreman command

SETUP.md

@@ -42,6 +42,9 @@ On Arch, you will need:
 - `ruby-foreman`
 - `redis`
 - `postgresql`
+- `yarn`
+- `gmp`
+- `libidn`
 
 ### Windows
 
@@ -80,7 +83,7 @@ mkdir -p data/redis
 redis-server ./redis-dev.conf
 
 # [Optional] Stop Redis
-kill "$(cat ./data/redis/redis-dev.pid)"
+# kill "$(cat ./data/redis/redis-dev.pid)"
 ```
 
 ## Ruby
@@ -111,33 +114,38 @@ bundle exec rake db:setup
 ## Running Mastodon
 
 1. Run `export RAILS_ENV=development 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.
+    - 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`.
-  a. If this explodes, complaining about `Hash`, you'll need to `export NODE_OPTIONS=--openssl-legacy-provider`.
-  b. After doing this, you will need to run `bundle exec rake assets:clobber` and then re-run
-  `bundle exec rake assets:precompile`.
+    - If this explodes, complaining about `Hash`, you'll need to \
+      `export NODE_OPTIONS=--openssl-legacy-provider`.
+    - After doing this, you will need to run `bundle exec rake assets:clobber` \
+      and then re-run `bundle exec rake assets:precompile`.
 3. Run `foreman start`
 
 # Updates/Troubleshooting
 
 ## RubyVM/DebugInspector Issues
 
-Still unable to fix. Circumvent by removing `better_errors` and `binding_of_caller` from Gemfile.
+Still unable to fix. Circumvent by removing `better_errors` and
+`binding_of_caller` from Gemfile.
+
 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:
 
+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`
 3. `yarn install`
 
-Then re-run `foreman`. No. We have no idea why this worked.
+Then re-run `foreman start`. No. We have no idea why this worked.
 
-If the above instructions don't work, please contact @Rin here, or @tammy@social.treehouse.systems.
+If the above instructions don't work, please contact @Rin here, or \
+@tammy@social.treehouse.systems.