mirror of
https://github.com/movie-web/docs.git
synced 2025-09-13 09:03:27 +00:00
Port all documents to MDX
This commit is contained in:
mrjvs
99
pages/extra/selfhost.mdx
Normal file
99
pages/extra/selfhost.mdx
Normal file
@@ -0,0 +1,99 @@
|
||||
### Guide to full Self-Deployment of movie-web with Docker Compose
|
||||
|
||||
1. **Install Docker and Docker Compose:**
|
||||
|
||||
Ensure that Docker and Docker Compose are installed on your system. You can follow the official Docker documentation for installation instructions:
|
||||
- [Install Docker](https://docs.docker.com/get-docker/)
|
||||
|
||||
2. **Create a Docker Compose file:**
|
||||
|
||||
Create a new file named `docker-compose.yml` in your project directory and paste the following content into it:
|
||||
|
||||
```yaml
|
||||
version: '3.8'
|
||||
|
||||
services:
|
||||
postgres:
|
||||
image: postgres
|
||||
restart: unless-stopped
|
||||
environment:
|
||||
POSTGRES_USER: movie_web_user
|
||||
POSTGRES_DB: movie_web_backend
|
||||
POSTGRES_PASSWORD: YourPasswordHere
|
||||
networks:
|
||||
- movie-web-network
|
||||
|
||||
movie-web-backend:
|
||||
image: ghcr.io/movie-web/backend:latest
|
||||
restart: unless-stopped
|
||||
environment:
|
||||
MWB_SERVER__CORS: "https://movie-backend.example.tld https://movie.example.tld"
|
||||
MWB_SERVER__PORT: 8080
|
||||
MWB_POSTGRES__CONNECTION: postgresql://movie_web_user:YourPasswordHere@postgres:5432/movie_web_backend
|
||||
MWB_CRYPTO__SESSION_SECRET: 32CHARACTERLONGSECRET
|
||||
MWB_META__NAME: Server name
|
||||
MWB_META__DESCRIPTION: Server Description
|
||||
MWB_POSTGRES__MIGRATE_ON_BOOT: "true"
|
||||
MWB_SERVER__TRUSTPROXY: "true"
|
||||
MWB_SERVER__TRUSTCLOUDFLARE: "true"
|
||||
# This is needed to resolve errors running migrations on some platforms - does not affect the application
|
||||
MIKRO_ORM_MIGRATIONS_DISABLE_FOREIGN_KEYS: "false"
|
||||
ports:
|
||||
- "8080:8080"
|
||||
depends_on:
|
||||
- postgres
|
||||
networks:
|
||||
- movie-web-network
|
||||
|
||||
movie-web-frontend:
|
||||
build:
|
||||
context: https://github.com/movie-web/movie-web.git
|
||||
args:
|
||||
TMDB_READ_API_KEY: "YourTMDBReadAPIKeyHere"
|
||||
CORS_PROXY_URL: "https://cors.example.tld https://second.cors.example.tld"
|
||||
BACKEND_URL: "https://backend.example.tld"
|
||||
DMCA_EMAIL: "YourEmail"
|
||||
PWA_ENABLED: "true"
|
||||
APP_DOMAIN: "YourDomainHere"
|
||||
OPENSEARCH_ENABLED: "true"
|
||||
GA_ID: "Google ID Here"
|
||||
ports:
|
||||
- "80:80"
|
||||
networks:
|
||||
- movie-web-network
|
||||
restart: unless-stopped
|
||||
|
||||
movie-web-proxy:
|
||||
image: ghcr.io/movie-web/simple-proxy:latest
|
||||
ports:
|
||||
- "3000:3000"
|
||||
networks:
|
||||
- movie-web-network
|
||||
restart: unless-stopped
|
||||
|
||||
networks:
|
||||
movie-web-network:
|
||||
driver: bridge
|
||||
|
||||
**Important:**
|
||||
* Replace `YourPasswordHere` with your secure database password.
|
||||
* Generate a strong session secret and replace `32CharacterLongStringHere`.
|
||||
```
|
||||
**Important:**
|
||||
* Replace `YourPasswordHere` with your secure database password.
|
||||
* Generate a strong session secret and replace `32CharacterLongStringHere`.
|
||||
* Replace `TMDBReadAPIKey` with your api key learn more [here](https://movie-web.github.io/docs/client/tmdb).
|
||||
* replace `yourDomainHere` with whatever you'll be using to access your main site, like movie-web.app
|
||||
* replace `meta__name` and `meta__description`
|
||||
2. **Start the Backend:** Open a terminal in the directory containing `docker-compose.yml` and execute:
|
||||
|
||||
```bash
|
||||
docker compose up --detach
|
||||
```
|
||||
**Accessing Your Backend**
|
||||
|
||||
Your services should be accessible on `(YourPrivateIP):port`. To share it outside your local network, you'll need to configure port forwarding or cloudflared tunnel.
|
||||
|
||||
**Optional: Implementing a Reverse Proxy**
|
||||
|
||||
To enhance your SSL and domain configuration, it's advisable to establish a reverse proxy, such as Nginx. For an optimal choice in this regard, Cloudflare Zero Trust Tunnel is recommended. You can find more information [here](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/).
|
||||
43
pages/extra/streaming.mdx
Normal file
43
pages/extra/streaming.mdx
Normal file
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: 'Streaming'
|
||||
---
|
||||
|
||||
# Streaming
|
||||
|
||||
This page explains all the different ways you can enable movie-web to stream your favorite movies & TV shows, each with their own pros and cons.
|
||||
|
||||
{/* ## Method 1 - Browser extension
|
||||
|
||||
The movie-web browser extension is the easiest way to be able to watch media with fast streaming speeds, it is available for both [Chrome] and [Firefox].
|
||||
|
||||
This method is great if you only use movie-web on your computer. If you use a mobile device or smart TV, you'll unfortunately have to stick to using a proxy since these devices don't usually support browser extensions.
|
||||
|
||||
Since this method uses your own IP, it is undetectable by streaming services, so you can use it to watch your favorite shows without worrying about getting blocked by their servers.
|
||||
*/}
|
||||
|
||||
## Method 1 - Self-hosted proxy
|
||||
|
||||
Self-hosting a proxy is an easy way to get faster streaming speeds, [we have a guide](../2.proxy/1.deploy.md) that explains how to set up one for **free**.
|
||||
|
||||
This method is recommended if you want to host a proxy for your friends and or family to use, as it is the faster than using the public proxy and the most reliable way to stream media at the moment.
|
||||
|
||||
{/* This method is recommended if you want to host a proxy for your friends and family to use, or if you want to use movie-web on a device that doesn't support the [browser extension](#method-1---browser-extension), such as a smart TV or mobile device.*/}
|
||||
|
||||
1. Set up a proxy using one of our [guides](../2.proxy/1.deploy.md#deploying-the-proxy), [though we recommend Netlify](../2.proxy/1.deploy.md#method-1---netlify-easy).
|
||||
2. Once that's done, go to the **Connections** section of the **Settings page** on your movie-web instance of chocie.
|
||||
3. Enable `Use custom proxy workers` if it's not already enabled.
|
||||
4. Add a new custom proxy by clicking `Add new worker`.
|
||||
5. Copy the URL of the proxy you deployed before, and paste it into the empty text box.
|
||||
|
||||
|
||||
::alert{type="info"}
|
||||
If you're self-hosting the client, you can use the [`VITE_CORS_PROXY_URL`](../3.client/3.configuration.md#vite_cors_proxy_url) variable to set the proxy URL for everyone who uses your client.
|
||||
::
|
||||
|
||||
## Method 2 - Public proxy
|
||||
|
||||
The public proxy is the easiest way to get started with movie-web as it is the default, it is hosted by us and is completely free to use.
|
||||
|
||||
If you are using the main website, then you are most likely already using the public proxy. Unfortunately you will most likely be getting slower speeds and your video might be buffering more often, which is why we recommend using a self-hosted proxy if you can.
|
||||
|
||||
This is not the case with self-hosted clients, there is no proxy set up by default on self-hosted clients and you will need to [set up one yourself](../2.proxy/1.deploy.md).
|
||||
Reference in New Issue
Block a user