### Deploy Metube Server with Docker-Compose Source: https://metatube-community.github.io/wiki/server-deployment Set up Metube server deployment using Docker-Compose. This method involves creating a directory, downloading the docker-compose.yaml file from a GitHub repository, and then starting the services in detached mode. ```bash mkdir metatube-sdk-go && cd metatube-sdk-go ``` ```bash curl -sL https://raw.githubusercontent.com/metatube-community/metatube-sdk-go/main/docker-compose.yaml -o docker-compose.yaml ``` ```bash docker-compose up -d ``` -------------------------------- ### Metatube Backend HTTP Proxy Environment Variables Source: https://metatube-community.github.io/wiki/proxy-configuration This outlines the environment variables required to configure an HTTP proxy for the Metatube backend. Both HTTP_PROXY and HTTPS_PROXY must be set for proper proxy functionality. Examples are provided for both standard HTTP and SOCKS5 proxies. ```env HTTP_PROXY=http://192.168.1.2:7890 HTTPS_PROXY=http://192.168.1.2:7890 ``` ```env HTTP_PROXY=socks5://192.168.1.2:7891 HTTPS_PROXY=socks5://192.168.1.2:7891 ``` -------------------------------- ### Deploy Metube Server with Docker Source: https://metatube-community.github.io/wiki/server-deployment Deploy the Metube server using Docker containers. Supports both memory mode and recommended database mode with a DSN. Ensure Docker is installed. The commands provided will pull the latest image from GitHub Container Registry and map the host port 8080 to the container's port 8080. ```docker docker run -d -p 8080:8080 --name metatube ghcr.io/metatube-community/metatube-server:latest ``` ```docker docker run -d -p 8080:8080 -v $PWD/config:/config --name metatube ghcr.io/metatube-community/metatube-server:latest -dsn /config/metatube.db ``` -------------------------------- ### Configure HTTP Proxy in Docker Source: https://metatube-community.github.io/wiki/proxy-configuration This example shows how to pass an HTTP proxy environment variable to a Docker container during its creation. This ensures that the containerized application uses the specified proxy for its network requests. ```bash docker run -e HTTP_PROXY="http://ip:port" ``` -------------------------------- ### Run Metube Server Directly (Binary) Source: https://metatube-community.github.io/wiki/server-deployment Execute the Metube server binary directly on a machine. Supports memory mode or recommended database mode using a DSN. For Windows, it can be run via double-click; for Linux, background execution using nohup or systemd is suggested. The default port is 8080, configurable with the -port flag. ```bash ./metatube-server ``` ```bash ./metatube-server -dsn metatube.db ``` -------------------------------- ### Set Movie Provider Priority (v1.3-) Source: https://metatube-community.github.io/wiki/metadata-providers Provides an example of setting the priority for the AVBASE movie provider using an environment variable in older versions (v1.3 and earlier) of MetaTube Server. This method is distinct from the newer configuration syntax. ```bash export MT_MOVIE_PROVIDER_PRIORITY_AVBASE=1000 ``` -------------------------------- ### Update Metube Server Docker Container Source: https://metatube-community.github.io/wiki/server-deployment Commands to stop and remove an existing Metube server Docker container before redeploying with an updated image. This ensures a clean update process. Skip these commands if performing an initial installation. ```docker docker stop metatube ``` ```docker docker rm metatube ``` -------------------------------- ### Configure HTTP Proxy in Linux Source: https://metatube-community.github.io/wiki/proxy-configuration This snippet demonstrates how to set an HTTP proxy environment variable in a Linux environment. This is typically done to route outgoing HTTP traffic through a specified proxy server and port. ```shell export HTTP_PROXY="http://ip:port" ``` -------------------------------- ### Set Movie Provider Priority (v1.4+) Source: https://metatube-community.github.io/wiki/metadata-providers Demonstrates how to set the priority for the AVBASE movie provider using an environment variable in MetaTube Server version 1.4 and later. This allows manual adjustment of scraping source priorities for better data accuracy. ```bash export MT_MOVIE_PROVIDER_AVBASE__PRIORITY=1000 ``` -------------------------------- ### Set Actor Provider Priority (v1.4+) Source: https://metatube-community.github.io/wiki/metadata-providers Shows how to set the priority for the GFriends actor provider using an environment variable in MetaTube Server version 1.4 and later. This enables fine-grained control over which actor data sources are preferred. ```bash export MT_ACTOR_PROVIDER_GFRIENDS__PRIORITY=99 ``` -------------------------------- ### Set Actor Provider Priority (v1.3-) Source: https://metatube-community.github.io/wiki/metadata-providers Shows how to set the priority for the GFriends actor provider using an environment variable in older MetaTube Server versions (v1.3 and prior). This older syntax is used for configuring actor data source preferences. ```bash export MT_ACTOR_PROVIDER_PRIORITY_GFRIENDS=99 ``` -------------------------------- ### Remove Movie Provider (v1.3-) Source: https://metatube-community.github.io/wiki/metadata-providers Demonstrates how to remove the ARZON movie provider from consideration by setting its priority to 0 using an environment variable in MetaTube Server versions 1.3 and below. This allows for the exclusion of specific data sources. ```bash export MT_MOVIE_PROVIDER_PRIORITY_ARZON=0 ``` -------------------------------- ### Remove Movie Provider (v1.4+) Source: https://metatube-community.github.io/wiki/metadata-providers Illustrates how to remove the JavBus movie provider from scraping sources by setting its priority to 0 using an environment variable in MetaTube Server version 1.4 and later. This is useful for excluding unreliable or unwanted data sources. ```bash export MT_MOVIE_PROVIDER_JAVBUS__PRIORITY=0 ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.