trace.moe
Anime Scene Search Engine
Trace back the scene where an anime screenshots is taken from.
It tells you which anime, which episode, and the exact moment this scene appears.
Try this image yourself.
Web Integrations
Link to trace.moe from other websites, you can pass image URL in query string like this:
https://trace.moe/?url=http://searchimageurl
trace.moe API
For Bots/Apps, refer to https://soruly.github.io/trace.moe-api/
System Overview
This repo is just an index page for the whole trace.moe system. It consists of different parts as below:
Client-side (gray parts):
- trace.moe-www - web server serving the webpage trace.moe
- trace.moe-WebExtension - browser add-ons to help copying and pasting images
- trace.moe-telegram-bot - official Telegram Bot
Server-side (blue and red parts):
- trace.moe-api - API server for image search and database updates
- trace.moe-media - media server for video storage and scene preview generation
- LireSolr - image analysis and search plugin for Solr
- trace.moe-worker - includes hasher, loader and watcher
Others:
- anilist-crawler - getting anilist info and store in mariaDB
- slides - past presentation slides on the project
Hosting your own trace.moe system
You're going to need these docker images.
| Parts | Docker CI Build | Docker Image |
|---|---|---|
| MariaDB |  |
|
| Adminer |  |
|
| redis |  |
|
| liresolr |  |
 |
| trace.moe-www |  |
 |
| trace.moe-api |  |
 |
| trace.moe-media |  |
 |
| trace.moe-worker-hasher |  |
 |
| trace.moe-worker-loader | |
 |
| trace.moe-worker-watcher | |
 |
- Copy
.env.exampleto.envand update config as you need
WWW_PORT=3310
API_PORT=3311
MEDIA_PORT=3312
ADMINER_PORT=3313
SOLR_PORT=8983
NEXT_PUBLIC_API_ENDPOINT=http://172.17.0.1:3311 # external URL
NEXT_PUBLIC_MEDIA_ENDPOINT=http://172.17.0.1:3312 # external URL
WATCH_DIR=/home/soruly/trace.moe-incoming/ # suggest using fast drives
MEDIA_DIR=/home/soruly/trace.moe-media/ # suggest using large drives
HASH_DIR=/home/soruly/trace.moe-hash/ # suggest using fast drives
SOLR_DIR=/home/soruly/mycores # suggest using super fast drives
TRACE_MEDIA_SALT=YOUR_TRACE_MEDIA_SALT
TRACE_API_SALT=YOUR_TRACE_API_SALT
TRACE_API_SECRET=YOUR_TRACE_API_SECRET
MARIADB_ROOT_PASSWORD=YOUR_MARIADB_ROOT_PASSWORD
- Ensure the directories are created and are empty before starting the containers. And for
SOLR_DIR, you must set the owner to uid,gid to 8983
mkdir -p /home/soruly/trace.moe-incoming/
mkdir -p /home/soruly/trace.moe-media/
mkdir -p /home/soruly/trace.moe-hash/
mkdir -p /home/soruly/mycores
sudo chown 8983:8983 /home/soruly/mycores- Start the containers
docker-compose up- Once the cluster is ready, you can adding files to incoming folder
The files in incoming folder must be contained in 1-level folders, e.g.
trace.moe-incoming/foo.mp4 <= not ok
trace.moe-incoming/1/foo.mp4 <= ok
trace.moe-incoming/1/bar/foo.mp4 <= ok, but will be uploaded as /1/foo.mp4
trace.moe assumes the folder name is anilist ID. If your data is not related to anilist ID, you can use any id/text you want. The system would still work without anilist data.
Do not create the folders in the incoming directory. You should first put video files in folders, then move/copy the folders into the incoming directory.
Once the video files are in incoming directory, the watcher would start uploading the video to trace.moe-media. When it's done, it would delete the video in incoming directory. After Hash worker and Load workers complete the job, you can search the video by image in your www website at WWW_PORT.