Generating the Bundle
The generation of the bundle is very simple, on the root folder execute the following command
Code Block | ||||
---|---|---|---|---|
| ||||
node build-bundle.js |
This command will generate a folder call ESUI_<version> (e.g. ESUI_3.0.0) this folder will contain only the necessary files for a proper execution. This folder can be moved to any other location and executed as any other Enterprise Search instance.
If the bundle must be moved to another location, a zip can be generate using
Code Block | ||||
---|---|---|---|---|
| ||||
node build-bundle.js -z |
This will create a zip file ready to be moved, with an additional README_AFTER_UNZIP.txt, with additional instructions to execute before running the instance, which will explain below.
When trying to run an unzipped bundle as any other instance, some issues will pop-up, due to broken references due the zip process. To prevent this every zip bundle as an additional set of instructions to rebuild this references, this process is completely off-line. We'll review those instructions here, but as we said, they will be available in the README_AFTER_UNZIP.txt
First execute the following command
Code Block |
---|
node init.js |
This command will "install" the local dependencies with the broken references. It is not an proper installation, since we are not adding anything new to the instance, we are only updating some files.
Once the script has finished, we can run the instance normally, that's it.