Hi! Can you please help accessing the logs?

I am trying to set up jolt in a docker container and connect it to jellyfin. I have jellyfin instance set up and running, and is accessible from jolt container at http://jellyfin:8096. (I've been using jellyfin and jellyseerr since a month or so and they are working fine.) I added this address in the config.yaml file. But when I try to log in, there is no visual feedback and no message in docker logs. Can you help me finding out what is wrong?

Thanks,

I'll attempt to create an icon that fits better with source files included.
The icon should...

1. Provide light/dark modes
2. Have a style guide
3. Shouldn't be too complex
4. Require an icon that refers to a "jolt" ( bolt, speed, etc )

I'll update you with progress reports when I can :)

Not having any docker images to quickly spin the project in kube or on a NAS is hurting the project.

Having images ready to spin would lower the friction between project discovery and first run. Please consider providing official images.

Hey,

i wanted to check out the app but it is not working for me.
The login works fine, but the app and pages are empty.

I think there is a problem with the database. I used nearly complete the default config:

    04/15/2023 11:01:41 AM
    PostgreSQL Database directory appears to contain a database; Skipping initialization
    04/15/2023 11:01:41 AM
    04/15/2023 11:01:41 AM
    2023-04-15 09:01:41.682 UTC [1] LOG:  starting PostgreSQL 14.7 (Debian 14.7-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
    04/15/2023 11:01:41 AM
    2023-04-15 09:01:41.683 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
    04/15/2023 11:01:41 AM
    2023-04-15 09:01:41.683 UTC [1] LOG:  listening on IPv6 address "::", port 5432
    04/15/2023 11:01:41 AM
    2023-04-15 09:01:41.700 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
    04/15/2023 11:01:41 AM
    2023-04-15 09:01:41.773 UTC [27] LOG:  database system was shut down at 2023-04-10 19:35:22 UTC
    04/15/2023 11:01:42 AM
    2023-04-15 09:01:42.752 UTC [1] LOG:  database system is ready to accept connections
    04/15/2023 11:02:10 AM
    2023-04-15 09:02:10.860 UTC [41] FATAL:  role "root" does not exist
    04/15/2023 11:02:40 AM
    2023-04-15 09:02:40.990 UTC [51] FATAL:  role "root" does not exist
    04/15/2023 11:03:11 AM
    2023-04-15 09:03:11.132 UTC [60] FATAL:  role "root" does not exist
    04/15/2023 11:03:41 AM
    2023-04-15 09:03:41.279 UTC [69] FATAL:  role "root" does not exist
    04/15/2023 11:04:11 AM
    2023-04-15 09:04:11.404 UTC [79] FATAL:  role "root" does not exist

What is required?

In order to display seasons and episodes in the UI, as well as sync their watched status, they need to be efficiently fetched and cached from TMDB. The following logic will be used:

1. On fetch of TV show (GetOrCreateByTmdbID()) the service will check if the show has completed.
2. If not, seasons and episodes will be synced.
3. First, the last cached season will be checked, and updated if necessary.
4. All episodes of the last cached seasons, and newer seasons will be fetched from TMDB and updated.

Consumers will have to get seasons and episodes through the TvService to ensure that this logic is executed whenever these models are requested.

Any possibility on supporting plex and other various media servers?

What is the problem?

Since recommended movies are fetched from TMDB's movie recommendations API, and scored by the ratings given to their source movie, scores can easily be inflated by having them appear in lots of movies' recommendations.

Solution

The following models could improve the recommendation algorithm by using a normalized scoring system based on averages of the associated ratings:

type Suggestion struct {
  gorm.Model
  MediaType         string  // movies or tvs
  MediaID           uint
  UserID            uint
  SuggestionSources []SuggestionSource
}

func (s *Suggestion) Score() {
  return AvgScore(s.SuggestionSources)
}

type SuggestionSource struct {
  gorm.Model
  SuggestionID uint
  Suggestion   Suggestion
  MediaType    string
  MediaID      uint
  ReviewID     uint
  Review       Review
}

func (s *SuggestionSource) Score() {
  return s.Review.Rating
}

When viewing media in Jellyfin, add user profile pictures displayed with ratings alongside, with their respective reviews.

It will be great if in the future you could import review from other sites like senscritique / myanimelist / tmdb

What is required?

Jolt should sync watched shows, seasons and episodes from supported media servers. Currently Jellyfin.

A sync jellyfin command has already been prepared in the develop branch, which needs to be refactored to use the JellyfinService for this purpose.

The /Users/{userId}/Items?recursive=true&includeItemTypes=Series&enableUserData=true endpoint will return all available series for a user, and the UserData object will include the played state.

For seasons and episodes, the /Shows/{seriesId}/Seasons and /Shows/{seriesId}/Episodes endpoints will return similar data if the userId and enableUserData query parameters are included.

What needs to be done?

• Separate the Jellyfin servers from the auth providers.
• Support multiple Jellyfin configurations in jellyfin.
• Support an auth provider key in the configuration.
• Allow user to pick which Jellyfin server to log into.
• Map media to JellyfinItem and remove JellyfinID and JellyfinServerID attributes from entities.

Please don't end up like like Jellyfin or Jellyseerr (Overseerr) saying "sqlite is enough" and buiding upon only that. From the get go start decoupling the SQL from your code and making a module for SQLite and Postgres for example, if this takes on in the future you and people using it will be sooo much happier.

I've done it in Go here: https://github.com/aleksasiriski/rffmpeg-go/tree/main/processor