The new datafari UI based on React can be used directly into Datafari starting from Datafari 5.0.
...
The new Datafari UI currently in Alpha is directly integrated into the code of Datafari.
To use it simply enter /datafariuiinto the URL of your Datafari.
For example, if you access to Datafari by this URL : https://mydatafari.com/Datafari the path to access to the React DatafariUI will be :
...
| Info |
|---|
The next steps are for a local build installing all the dependencies into your local server. note that a Dockerfile is present at the root of the project to easily compile the source code without installing any dependencies. The package after the build is present into “ |
Install the dependencies locally
...
This will create a build folder containing the production version of the DatafariUI. By default, this build expects to be reachable on the server using the path any.domain.test/datafariui.
This can be modified by changing content of the following file at the root of the project:
...
I found it best to put it as part of the installation folder, which is by default /opt/datafari.
You can copy the build folder to /opt/datafari/www for exemple:
| Code Block |
|---|
cp -R build /opt/datafari/www |
...
| Info |
|---|
Assuming the production build of datafariUI has been copied to |
It is necessary to add some elements to the tomcat.conf apache configuration file that is shipped with datafari to serve datafariUI.
...
Save the configuration file, restart apache2 and you should be able to reach datafariui through: mydomain.test/datafariui
Development Configuration
...
The development server can be configured to be served at any path, the default is the same as the production one, i.e. /datafariui. It can be changed in the file:
...
the app is expected to be deployed at
/datafariuiand it is most likely been deployed at the root of the dev server i.e.Datafari’s APIs won’t be available as datafariui expects Datafari to be deployed on the same domain at the
/Datafaripath and it is not the case right now
...