zelo72/documentation
1
0
Fork 0
mirror of https://github.com/mastodon/documentation synced 2025-04-11 22:56:17 +02:00
Code Issues 6 Releases Wiki Activity

Development: Fix bundle install instructions and expand on running rails (#133)

Browse Source
This commit is contained in:
zorun 2017-04-27 11:15:53 +02:00 committed by wxcafé
parent 00103cbf95
commit 371864c39e
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Running-Mastodon/Development-guide.md
View File

@ -11,9 +11,9 @@ In fact, all you need is described in the [production guide](Production-guide.md
- To prefix any commands with `RAILS_ENV=production` since the default environment is "development" anyway - To prefix any commands with `RAILS_ENV=production` since the default environment is "development" anyway
- Any cronjobs - Any cronjobs
The command to install Ruby project dependencies does not require any flags, i.e. simply The command to install Ruby project dependencies is the following:
bundle install bundle install --with development
Similarly, installing JavaScript dependencies doesn't require any flags: Similarly, installing JavaScript dependencies doesn't require any flags:
@ -21,9 +21,13 @@ Similarly, installing JavaScript dependencies doesn't require any flags:
By default the development environment wants to connect to a `mastodon_development` database on localhost using your user/ident to login to Postgres (i.e. not a md5 password) By default the development environment wants to connect to a `mastodon_development` database on localhost using your user/ident to login to Postgres (i.e. not a md5 password)
You can run Mastodon with: To setup the `mastodon_development` database, run:
rails s bundle exec rails db:setup
You can then run Mastodon with:
bundle exec rails server
And open `http://localhost:3000` in your browser. Background jobs run inline (aka synchronously) in the development environment, so you don't need to run a Sidekiq process. And open `http://localhost:3000` in your browser. Background jobs run inline (aka synchronously) in the development environment, so you don't need to run a Sidekiq process.