support custom hostname
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.
+1 😀
I might not be able to help with the code. But , let me know if you need some help testing if it works. Thx! 🙂
I might not be able to help with the code. But , let me know if you need some help testing if it works. Thx! 🙂
@silgon hey - definitely.
we had an early implementation of this feature days ago, but we decided to pause this for now to work on the cloud deployment instead. after launching the cloud-hosted open-cuak, we will come back and resume implementing this feature.