Skip to content

Commit 2107ad9

Browse files
committed
Remove guide docs for rackup
Rackup now recommends to not use it: https://github.com/rack/rackup?tab=readme-ov-file#soft-deprecation I'd wager a guess and say that most apps (in a rails context) are already using either `bin/rails server` or just invoke their chosen server directly anyways. Additionally, this info outdated. `config.ru` is already generated in such a way that users don't have to change anything.
1 parent 852b143 commit 2107ad9

File tree

1 file changed

+0
-22
lines changed

1 file changed

+0
-22
lines changed

guides/source/rails_on_rack.md

Lines changed: 0 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -58,28 +58,6 @@ class Server < ::Rack::Server
5858
end
5959
```
6060

61-
### `rackup`
62-
63-
To use `rackup` instead of Rails' `bin/rails server`, you can put the following inside `config.ru` of your Rails application's root directory:
64-
65-
```ruby
66-
# Rails.root/config.ru
67-
require_relative "config/environment"
68-
run Rails.application
69-
```
70-
71-
And start the server:
72-
73-
```bash
74-
$ rackup config.ru
75-
```
76-
77-
To find out more about different `rackup` options, you can run:
78-
79-
```bash
80-
$ rackup --help
81-
```
82-
8361
### Development and Auto-reloading
8462

8563
Middlewares are loaded once and are not monitored for changes. You will have to restart the server for changes to be reflected in the running application.

0 commit comments

Comments
 (0)