Skip to content

Add documentation for LAN access using TAIGA_DOMAIN #159

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

Open
LeoR4Zm wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add documentation for LAN access using TAIGA_DOMAIN #159

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
22 changes: 22 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -528,3 +528,25 @@ server {
## Change between subpath and subdomain

If you're changing Taiga configuration from default subdomain (https://taiga.mycompany.com) to subpath (http://mycompany.com/subpath) or vice versa, on top of adjusting the configuration as said above, you should consider changing the TAIGA_SECRET_KEY so the refresh works properly for the end user.

## Accessing Taiga from Other Devices on the Local Network

By default, Taiga may use:

TAIGA_DOMAIN=localhost:9000

This only works when accessing the service from the same machine.

To allow access from other devices on the same network, update the
`.env` configuration to use the host machine's local IPv4 address:

TAIGA_DOMAIN=<your-local-ip>:9000

Example:

TAIGA_DOMAIN=192.168.1.25:9000

After modifying the configuration, restart the containers:

docker compose down
./launch-taiga.sh