Write a lot, like an actual lot. of documentation

Co-authored-by: William Oldham <github@binaryoverload.co.uk>
This commit is contained in:
mrjvs
2023-12-12 21:44:28 +01:00
parent c4d1622922
commit 042023dd11
21 changed files with 304 additions and 196 deletions

View File

@@ -10,24 +10,24 @@ We **do not** provide support on how to self-host. If you can't figure it out th
There are a few configurations of hosting movie-web. Each with their own benefits.
**If you don't know what to choose, go with method 1.**
## Method 1 - only host the frontend
## Method 1 - Only host the frontend
With this method, you only host the essential parts that make movie-web work. But keep using the account server from offical movie-web.
This method is the easiest to self-host and is recommended for most users.
1. [Setup the Proxy!](2.proxy.md)
2. [Setup the Client!](3.client.md)
1. [Setup the Proxy!](../2.proxy/1.deploy.md)
2. [Setup the Client!](../3.client/1.deploy.md)
## Method 2 - only host the account server
## Method 2 - Only host the account server
If you want to own your own data, it's possible to selfhost just the account server and nothing else.
This method is only recommended if you have experience hosting databases or other similar stateful applications.
1. [Setup the Backend!](4.backend.md)
2. [Configure the Client!](5.use-backend.md)
1. [Setup the Backend!](../4.backend/1.deploy.md)
2. [Configure the Client!](../3.client/1.deploy.md)
## Method 3 - host everything
## Method 3 - Host everything
If you want an instance that's completely isolated from official movie-web. You can selfhost all parts.
This method is not recommended for inexperienced hosters.
1. [Setup the Proxy!](2.proxy.md)
2. [Setup the Backend!](4.backend.md)
3. [Setup the Client!](3.client.md)
1. [Setup the Proxy!](../2.proxy/1.deploy.md)
2. [Setup the Backend!](../4.backend/1.deploy.md)
3. [Setup the Client!](../3.client/1.deploy.md)