Skip to content

support custom hostname #54

Description

@ljhskyso

currently, we don't support custom hostname, as it is always hardcoded to be localhost for now. this works for running only on local machine, but if we want to expose it as a service accessible remotely, it causes issues.

from issue:

I was trying to run in a separate computer because mine halts due to load when I run the project and my normal load. The websites are redirected to localhost, even if i entered the ip. Thus http://192.168.1.10:11970 redirects to http://localhost:11970/portal, I believe it is the case with some websockets and other ports you use.
I tried to modify the environment file replacing all the localhost elements to the ip of the computer but when I run the command npm run docker:prod:up, the environment file (.env.production) gets overwritten again with the default values.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions