955bdcb2bc
* Rename all GitHub links from thepracticaldev/dev.to to forem/forem * Use new site name * Rename to Forem * Rename more dev.to to forem * Remove unnecessary redirects * Rename DEV to Forem * Use Forem instead of DEV for branding * Use Forem instead of DEV for licensing * Use seedling instead of DEV logo
42 lines
1.3 KiB
Markdown
42 lines
1.3 KiB
Markdown
---
|
|
title: Starting the Application
|
|
---
|
|
|
|
# Starting the application
|
|
|
|
We're a Rails app, and we use [Webpacker][webpacker] to manage some of our
|
|
JavaScript.
|
|
|
|
Start the application, Webpack, and our job runner [Sidekiq][sidekiq] by
|
|
running:
|
|
|
|
```shell
|
|
bin/startup
|
|
```
|
|
|
|
(This just runs `foreman start -f Procfile.dev`, for notes on how to install
|
|
Foreman, please see [Other Tools](/installation/others/))
|
|
|
|
Then point your browser to http://localhost:3000/ to view the site.
|
|
|
|
If you run into issues while trying to run `bin/setup` and the error message
|
|
isn't helpful, try running `bin/rails s -p 3000`. For example, you may need to
|
|
`yarn install` before starting the app.
|
|
|
|
If you're working on Forem regularly, you can use `alias start="bin/startup"` to
|
|
make this even easier. 😊
|
|
|
|
If you're using **`pry`** for debugging in Rails, note that using `foreman` and
|
|
`pry` together works, but it's not as clean as `bin/rails server`.
|
|
|
|
Here are some singleton commands you may need, usually in a separate
|
|
instance/tab of your shell.
|
|
|
|
- Running the job Sidekiq server (if using `bin/rails server`) -- this is mostly
|
|
for notifications and emails: **`bundle exec sidekiq`**
|
|
|
|
Current gotchas: potential environment issues with external services need to be
|
|
worked out.
|
|
|
|
[sidekiq]: https://github.com/mperham/sidekiq
|
|
[webpacker]: https://github.com/rails/webpacker
|