Skip to content

Commit 0356181

Browse files
Adds docs about serving octane in HTTPS (#229)
* Adds docs about serving octane in HTTPS * Update README.md Co-authored-by: Taylor Otwell <[email protected]>
1 parent 85e4d40 commit 0356181

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -116,6 +116,14 @@ php artisan octane:start
116116

117117
By default, Octane will start the server on port 8000, so you may access your application in a web browser via `http://localhost:8000`.
118118

119+
#### Serving Your Application Via HTTPS
120+
121+
By default, applications running via Octane generate links prefixed with `http://`. The `OCTANE_HTTPS` environment variable, used within your application's `config/octane.php` configuration file, can be set to `true` when serving your application via HTTPS. When this configuration value is set to `true`, Octane will instruct Laravel to prefix all generated links with `https://`:
122+
123+
```php
124+
'https' => env('OCTANE_HTTPS', false),
125+
```
126+
119127
#### Watching For File Changes
120128

121129
Since your application is loaded in memory once when the Octane server starts, any changes to your application's files will not be reflected when you refresh your browser. For example, route definitions added to your `routes/web.php` file will not be reflected until the server is restarted. For convenience, you may use the `--watch` flag to instruct Octane to automatically restart the server on any file changes within your application:

0 commit comments

Comments
 (0)