Final rewordings, postgres.ssl, dark/light icon + dir based titles.

This commit is contained in:
qtchaos
2024-01-02 04:13:28 +02:00
parent 927b23873f
commit f6de7b2240
21 changed files with 87 additions and 65 deletions

View File

@@ -2,7 +2,7 @@
title: 'Start self-hosting'
---
# How to self host
# How to self-host
::alert{type="info"}
We **do not** provide support on how to self-host. If you can't figure it out then tough luck. Please do not make GitHub issues or ask in our Discord server for support on how to self-host.
@@ -21,7 +21,7 @@ This method is the easiest to self-host and is recommended for most users.
## 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.
If you want to own your own data, it's possible to self-host just the account server and nothing else.
This method is only recommended if you have experience hosting databases or other similar stateful applications.
1. [Set up the Backend!](../4.backend/1.deploy.md)
@@ -29,7 +29,7 @@ This method is only recommended if you have experience hosting databases or othe
## Method 3 - Host everything
If you want an instance that's completely isolated from the official movie-web. You can selfhost all of the parts yourself, though this method is not recommended for inexperienced hosters.
If you want an instance that's completely isolated from the official movie-web. You can self-host all of the parts yourself, though this method is not recommended for inexperienced hosters.
1. [Set up the Proxy!](../2.proxy/1.deploy.md)
2. [Set up the Backend!](../4.backend/1.deploy.md)

View File

@@ -2,9 +2,9 @@
title: 'PWA vs no-PWA'
---
# About Selfhosting PWA
# About Self-hosting PWA
So that clients can have a more native app-like experience on mobile, movie-web has a function to support Progessive Web Apps (PWA). You can learn more about what a PWA is [here](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/What_is_a_progressive_web_app).
So that clients can have a more native app-like experience on mobile, movie-web has a function to support Progressive Web Apps (PWA). You can learn more about what a PWA is [here](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/What_is_a_progressive_web_app).
In movie-web version 3, PWAs were enabled by default. Unfortunately, PWAs tend to come with caching complications that can be tricky to resolve. That's why we have **disabled** PWAs by default in movie-web version 4. If you are upgrading from version 3, please [read our upgrade guide](../3.client/5.upgrade.md) for more information.
@@ -12,12 +12,12 @@ In movie-web version 3, PWAs were enabled by default. Unfortunately, PWAs tend t
Enabling PWAs means that you cannot disable it again - Please only proceed if you know what you are doing!
::
## If you are running movie-web on a hoster such as Vercel
## If you are running movie-web on a hosting platform such as Vercel
If your hosting is building movie-web from the source, you can enable PWAs using environment variables. The full environment variable reference can be found [here](../3.client/3.configuration.md) but for PWAs we are only interested in `VITE_PWA_ENABLED`.
If your hosting is building movie-web from the source, you can enable PWAs using the [`VITE_PWA_ENABLED`](../3.client/3.configuration.md#vite_pwa_enabled) environment variable.
Setting [`VITE_PWA_ENABLED`](../3.client/3.configuration.md#vite_pwa_enabled) to `true` will generate a [service worker file](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Making_PWAs_installable#service_worker) and a [web app manifest](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Making_PWAs_installable#the_web_app_manifest) which enable the website to be installed from a [web browser both on Desktop and on Mobile](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Making_PWAs_installable#installation_from_the_web).
## If you are running movie-web using the .zip files
If you are downloading the movie-web `zip` files from our GitHub and installing them on a static website hoster, then all you need to do is to make sure to download the [`movie-web.pwa.zip`](https://github.com/movie-web/movie-web/releases/latest/download/movie-web.pwa.zip) file instead of the `movie-web.zip` file!
If you are downloading the movie-web `zip` files from our GitHub and installing them on a static website host, then all you need to do is to make sure to download the [`movie-web.pwa.zip`](https://github.com/movie-web/movie-web/releases/latest/download/movie-web.pwa.zip) file instead of the `movie-web.zip` file!

View File

@@ -4,43 +4,41 @@ title: 'Troubleshooting'
# Troubleshooting
There is always a possibility for something to go wrong while trying to deploy your own instance of movie-web. This page will contain common issues people come across while self-hosting and their solutions.
There is always a possibility for something to go wrong while trying to deploy your own instance of movie-web. This page will contain common issues people have come across while self-hosting and their solutions.
## "Failed to find media, try again!" while searching
This is likely a misconfigured TMDB api key. Verify that TMDB isn't working by going to `/admin` or `/#/admin`. Then clicking `Test TMDB`.
**This is likely a misconfigured TMDB API key.** To verify that TMDB is the issue, visit `/admin` or `/#/admin` and click on the `Test TMDB` button.
If it succeeds, the TMDB api key is correct and it will be a different issue.
If the test succeeds, then your TMDB configuration is correct and the issue is with something else.
If it does not work. Recheck your TMDB api key. **Make sure its the READ api key, not the normal api key.**
If the test fails, then you should recheck your credentials. [**Make sure you're using the Read Access Token, not the normal API Key.**](https://www.themoviedb.org/settings/api#v4_auth_key){target="\_blank"}
## Everything I try to watch fails
This is likely a misconfigured worker. Verify that the workers are the issue by going to `/admin` or `/#/admin`. Then clicking `Test workers`.
**This is likely a misconfigured Worker.** To make sure that the Workers are the issue, visit `/admin` or `/#/admin`, then click on the `Test workers` button.
You should have at least 1 worker registered.
You should have at least 1 Worker registered, if you don't, you should [deploy a worker](../2.proxy/1.deploy.md#method-1---cloudflare-easy) and [set it up in the client](../3.client/3.configuration.md#vite_cors_proxy_url).
If any worker fails the test, you should double check its URL and double check if the worker has the correct code.
If any Worker fails the test, you should double check its URL and see if its up to date with the latest updates.
## I can't make an account or login
This is likely misconfigured or broken backend. Verify the backend by going to `/admin` or `/#/admin`. Then clicking `Test backend`.
**This is likely misconfigured or broken backend.** To verify that the backend is the issue, visit `/admin` or `/#/admin`, then click on the `Test backend` button.
It should give you the name that you have configured as backend with the latest version of the backend.
If the backend is online and properly configured it should display the name and version of the backend. If the name and description of the test don't match your own instance, [make sure you have your backend URL set correctly.](../3.client/3.configuration.md#vite_backend_url)
If the test gives you an error, your backend URL configuration option likely has a typo.
If the test gives you an error, your [backend URL configuration option](../3.client/3.configuration.md#vite_backend_url) likely has a typo.
If the version is not the latest version, you should update your backend instance.
If the version that shows up on your backend is not the latest version, you should update your backend to keep up with the latest changes.
If the name and description of the results don't match your own instance, make sure you have your backend URL set correctly.
## I updated from version 3 to version 4 but still see the old version
## I updated from version 3 to version 4 but I still see the old version
It is likely that you haven't installed the PWA version of movie-web. Please read the [upgrade guide](../3.client/5.upgrade.md) for more details on the matter.
## I'm getting SSL issues when using a hosted postgres database
You are most likely missing the `postgres.ssl` variable on your backend, enable it and the connection should work.
You are most likely missing the [`postgres.ssl`](../4.backend/2.configuration.md#postgresssl) variable on your backend, enable it and the connection should work.
## Permission denied to set parameter "session_replication_role"

View File

@@ -1,3 +1,4 @@
title: 'Self-Hosting'
icon: mdi:server-network
navigation.redirect: /self-hosting/hosting-intro
titleTemplate: '%s | Self-Hosting'