Skip to content

Adds devmode.hostsAllowed property #3104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Jan 11, 2024
Merged

Adds devmode.hostsAllowed property #3104

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
651bed6
Adds devmode.hostsAllowed property
tepi Jan 5, 2024
692c01e
Note->plaintext; add reasoning
tepi Jan 8, 2024
498495f
Merge branch 'latest' into devmode-allowed-hosts
mshabarov Jan 8, 2024
2e27402
Merge branch 'latest' into devmode-allowed-hosts
russelljtdyer Jan 10, 2024
56f6ab3
First pass at editing.
russelljtdyer Jan 10, 2024
35acaff
Merge branch 'latest' into devmode-allowed-hosts
russelljtdyer Jan 10, 2024
4feeeec
Second pass at editing.
russelljtdyer Jan 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion articles/configuration/development-mode/dev-tools/index.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Development Tools
description: Vaadin tools that are available when running applications in development mode.
description: Vaadin tools available when running applications in development mode.
order: 209
---

Expand All @@ -9,6 +9,11 @@ order: 209

Boost productivity with the Vaadin Development Tools, such as Component Locator, that are available when running applications in development mode.

Current and future functionality of Vaadin Development Tools may offer developers ways to alter the application configuration or even application code. Therefore, it may not be desirable to enable access to Development Tools for everyone -- even when running an application in development mode.

By default, Development Tools can be accessed only from loopback addresses. To configure hosts for Development Tools access, please see `devmode.hostsAllowed` <<{articles}/configuration/properties/#properties,configuration property>>.


== Topics

section_outline::[]
Expand Down
4 changes: 4 additions & 0 deletions articles/configuration/properties.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,10 @@ The following table contains the properties that are defined in the [classname]`
|`false`
|Closes the Vaadin session if no UI is active. A UI is considered active if it's open on the client-side and has any activity -- besides heartbeat requests. By default, heartbeat requests keep the Vaadin session open even when there is no user interaction. Set to `true` to close idle sessions. See `heartbeatInterval` below.

|`devmode.hostsAllowed`
|`null`
|Defines the hosts allowed to access Vaadin development tools. A comma-separated list of allowed hosts should be provided as the value. The `?` and `*` wildcards can be used (e.g., `192.168.1.*,172.17.?.*`). Loopback addresses are always allowed, regardless of the value set here.

|`devmode.liveReload.enabled`
|`true`
|Enables live reload. When using a server-side <<live-reload/index#, live reload tool>>, the browser is refreshed after code is rebuilt on the server. Set to `false` to disable automatic reloading of the browser. This applies only to development mode.
Expand Down