You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: essential configuration options for deployers
This commit makes everything a ton easier for deployers, adding
configuration options to allow nip.io domains or all origins to access
Puter for ideal LAN or VPN configurations.
Copy file name to clipboardExpand all lines: doc/self-hosters/domains.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,19 @@
6
6
7
7
Ensure the hosting device has a static IP address to prevent potential connectivity issues due to IP changes. This setup will enable seamless access to Puter and its services across your local network.
8
8
9
+
### Using `nip.io`
10
+
11
+
We recommend this configuration for LAN setups. All you need to do is set the following
12
+
at root level in your configuration file:
13
+
14
+
```json
15
+
"allow_nipio_domains": true
16
+
```
17
+
18
+
Puter requires multiple origins to work correctly. `nip.io` is a wildcard DNS for IP addresses,
19
+
so Puter can still have multiple subdomains and you don't need to configure your own DNS or
20
+
hosts file.
21
+
9
22
### Using Hosts Files
10
23
11
24
The hosts file is a straightforward way to map domain names to IP addresses on individual devices. It's simple to set up but requires manual changes on each device that needs access to the domains.
0 commit comments