This deployment leverages docker compose
to deploy Hoop on local or remote machines for solution assessment.
docker compose version
to check which version you have installedhttp://localhost:8009
in your browser.
If you want to set up a custom Identity Provider or run it in a remote machine, follow the Download & Run in a remote machine guide below.
Download the Docker Compose file
Set the .env file
.env
file.
Check all the available configurations in the environment variables section..env
file must be at the same level as the docker-compose.yml file.env
file to add the following configuration lines for your host configurationRun
Manage the containers
Access the developer portal
http://localhost:8009
in your browser.
Or, if you are running this on a remote machine, access http://<vm-public-dns>:8009
in your browser.API_URL
environment variable properly to ensure the web app assets are served correctly. Check the following steps to configure it:
Set the full domain:
.env
file, the API_URL
should include the complete schema (e.g., https://yourdomain.com
). This will ensure that assets are served with the correct schema and domain.Updating your .env file:
.env
file and add the following:https://yourdomain.com
with the full schema and host where you will serve the Hoop Gateway. If you encounter any issues after setting the API_URL
, double-check your .env
file and provide details about your setup for troubleshooting.API_URL
variable is not set manually, it will default to 127.0.0.1
, which serves locally inside your virtual machine. To avoid this and serve the web app properly over the correct domain, ensure you update the .env
file with your intended domain.Handling IP and DNS forwarding:
API_URL
with an IP address and later use DNS port forwarding, the assets might not load correctly. The API_URL
should reflect the full domain, not just the IP.