| .. | ||
| dist | ||
| env | ||
| template/conf | ||
| test-data | ||
| .gitignore | ||
| experiment.sh | ||
| nginx-site.conf | ||
| readme.md | ||
| reconvert.sh | ||
| setup.sh | ||
Run
When developing locally, this directory will contain run-time data required for the search engine. In a clean check-out, it only contains the tools required to bootstrap this directory structure.
Requirements
While the system is designed to run bare metal in production, for local development, you're strongly encouraged to use docker or podman. These are a bit of a pain to install, but if you follow this guide you're on the right track.
Set up
To go from a clean check out of the git repo to a running search engine, follow these steps. You're assumed to sit in the project root the whole time.
- Run the one-time setup, it will create the basic runtime directory structure and download some models and data that doesn't come with the git repo because git deals poorly with large binary files.
$ run/setup.sh
- Compile the project and build docker images
$ ./gradlew assemble docker
- Initialize the database
$ docker-compose up -d mariadb
$ ./gradlew flywayMigrate
- Bring the system online. We'll run it in the foreground in the terminal this time
because it's educational to see the logs. Add
-dto run in the background.
$ docker-compose up
- You should now be able to access the system.
| Address | Description |
|---|---|
| https://localhost:8080/ | User-facing GUI |
| https://localhost:8081/ | Operator's GUI |
- Download Sample Data
TODO: How?
Experiment Runner
The script experiment.sh is a launcher for the experiment runner, which is useful when
evaluating new algorithms in processing crawl data.