Simplify Illustration Management

[Arthi-chaud]

We currently have 4 Illustration Models (Artist, Release, Playlist, Track).

• There should be a single table for illustration models.
• There should be a single API endpoint to serve the images /illustrations/{id}
• Updating a resource's illustration should insert a new row in the database and delete the previous one

---

The current Illustration file system's structure uses the relations between the illustrated models. This makes it very easy for a user to navigate through it.

However, since manual modifications on this FS does not trigger changes in the database, this transparency is useless.
Moreover, the structure causes massive overhead when fetching/serving an image file (need to fetch the parent model(s) to build the path).

• The Illustration File System's structure should organize illustrations by their ID.

Example: /images/3/cover.jpg instead of:

• /images/artist_slug/cover.jpg
• /images/artist_slug/album_slug/release_slug/cover.jpg
• /images/artist_slug/album_slug/release_slug/disc_index/cover.jpg
• /images/artist_slug/album_slug/release_slug/disc_index/track_index/cover.jpg

From a client perspective, this new architecture comes with the pros of canceling cache when an illustration changes, since the ID of the illustration will change.