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
Describe the bug
After successfully executing the commands (npm install and npm start) and being able to access ossinsight via the terminal, I encounter difficulties accessing it through the web browser. Additionally, seeking guidance on properly passing environmental variables (specifically ETL_DATABASE and API-related variables) when using a Docker Compose file.
To Reproduce:
Steps to reproduce the behavior:
Clone the repo.
Run npm install.
Run npm start.
Attempt to access via web browser.
Expected behavior
Expecting to access ossinsight seamlessly through the web browser after following the setup steps.
OS: [Mac OS 14.0]
Tried disabling firewall.
Ran an nginx service on port 3001 to check for firewall port issues; localhost:3001 was accessible.
Need guidance on passing environmental variables (ETL_DATABASE, API-related) using Docker Compose.
The text was updated successfully, but these errors were encountered:
Describe the bug
After successfully executing the commands (npm install and npm start) and being able to access ossinsight via the terminal, I encounter difficulties accessing it through the web browser. Additionally, seeking guidance on properly passing environmental variables (specifically ETL_DATABASE and API-related variables) when using a Docker Compose file.
To Reproduce:
Steps to reproduce the behavior:
Clone the repo.
Run npm install.
Run npm start.
Attempt to access via web browser.
Expected behavior
Expecting to access ossinsight seamlessly through the web browser after following the setup steps.
OS: [Mac OS 14.0]
Tried disabling firewall.
Ran an nginx service on port 3001 to check for firewall port issues; localhost:3001 was accessible.
Need guidance on passing environmental variables (ETL_DATABASE, API-related) using Docker Compose.
The text was updated successfully, but these errors were encountered: