The existing UI development environment Docker setup is encountering numerous errors.
Setting up the UI project locally requires manual configuration file creation from sample files.
Done in this PR
I've addressed these issues by migrating the Docker environment to the latest version utilized in AgroPortal. This enhancement streamlines the local UI development environment setup process significantly.
The new way to run the UI locally
After cloning ontoportal_web_ui and having docker running.
use this command:
bin/ontoportal dev --api-url <api url> --api-key <apikey>
in BiodivPortal example:
bin/ontoportal dev --api-key 47a57aa3-7b54-4f34-b695-dbb5f5b7363e --api-url https://data.biodivportal.gfbio.org
Bilelkihal
commented
4 months ago
Problems
Done in this PR
I've addressed these issues by migrating the Docker environment to the latest version utilized in AgroPortal. This enhancement streamlines the local UI development environment setup process significantly.
The new way to run the UI locally
After cloning ontoportal_web_ui and having docker running. use this command:
bin/ontoportal dev --api-url <api url> --api-key <apikey>in BiodivPortal example:bin/ontoportal dev --api-key 47a57aa3-7b54-4f34-b695-dbb5f5b7363e --api-url https://data.biodivportal.gfbio.orgThe UI app is accessible from: localhost:3000