lasasmassive.blogg.se - Winrunner end of life

#Winrunner end of life movie#
#Winrunner end of life install#
#Winrunner end of life verification#
#Winrunner end of life series#

Originally used for actually searching, this use case was quite rare in real world usage. The search is run via the *nix find command. As long as google gives you a token, you can be a user! Search Authentication is OPEN, as I don't really care who is using this.

#Winrunner end of life verification#

Google OAuth has been implemented and token verification is performed on certain paths to control authorization. Video streaming is also implemented (handling ranges) within the requests. I primarily use these for streaming logs and dashboard style stats. I decided not to use web sockeets just to try something different and because the client never actually sends any data back to the server beyond the initial request.

This allows the consumer to recieve near real time updates without polling. Several API's expose streams via http to the client.

#Winrunner end of life series#

The data retrieved is used to significantly enhance user experience by providing for airing times, series images, descriptions, studio etc etc. While not perfect, any mistakes can be corrected and manually set. The application will try to guess the series based on the folder name. The AniList GraphQL API has been leveraged to retrieve most information regarding the various series. I would have transcoded them into webp v9 formats, however the trancoding process would take WAYYYY to long with my hardware since I'm not youtube. webp using the imagemin package.įfmpeg is also used to transcode files into mp4's playable by most web browsers.

Thumbnail Generation is done via ffmpeg and spawned by node through child_process.exec or child_process.execFile. Points of Interest Thumbnail Generation & Transcoding on the fly! You can manage your node processes with a manager such as pm2 if you wish.

NG_ROOT: Hosts the related angular project from this directory if specified.

ANI_LIST_RESTORE_FILE: Convenience file for restoring of previously loaded metadata, mainly so we don't hit the aniList api too hard on load.

HEALTH_MONITOR_INTERVAL: How often to run health monitoring (set to -1 for off), this will log the executor process counts & waiting counts (for externally spawned tasks).

MAX_CLI_WORKERS: Max Command line processes spawned at once,.

MAX_THUMBNAILS: How many thumbnails to generate per file,.

THUMBNAIL_BASE: Where to store our video thumbnails, should be a sub directory of the images dir.

SERIES_IMAGE_BASE: Where to store our images relating to series metadata, should be a sub directory of the images dir.

#Winrunner end of life movie#

TRANSCODE_DIR: Where to store movie transcodes and subtitles.

DB_PATH: Database Directory (for LevelDb).

SHARE_PATH: Which folder to share (absolute path preferred).

API_PORT: The port that we want the server to run on.

You will likely have to modify the config.json to set the application up properly. This project depends on several packages to provide additional functionality. Almost any relatively modern version should work (I am on v12). To run this you'll need nodeJs (as this IS a node project). Sudo mount -verbose -t drvfs //server/folder/to/share /local/mount/point Programs Needed I have tested with WSL and mounted my network share manually (during development) using the following command. As long as these are in your PATH then there should not be many problems.

It does leverage the use of the *nix find command as well as ffmpeg. I have run this on multiple debian based versions of linux. This is the server portion of the application.

Add folders to custom lists (favourites, recommended).

Analyze and fetch Metadata for (most) anime.

The current repository is an updated version with many quality of life features that makes it a joy (for me) to use. The first version was rudientary and lacking in features. I originally ran this on a raspberry pi and it was bare able to transcode the media on the fly for web playback.

#Winrunner end of life install#

The purpose is similar to plex (in fact I attempted to use plex first), however I disliked the fact that I would have to install plex clients on all my devices. It allows me to access and browse through my media as if it were another resource like youtube. I wrote this as a simple way for me to access my network shared video files. The server facilitates all calls for this web app! Why does this exist? NodeJs server to facilitate the analysis and serving of media (mainly video) files on a local server.