Make all pages MDX compliant + added logo back

This commit is contained in:
mrjvs
2024-03-30 21:10:20 +01:00
parent 268014552c
commit 8108d28feb
23 changed files with 205 additions and 154 deletions

View File

@@ -12,13 +12,13 @@ There is always a possibility for something to go wrong while trying to deploy y
If the test succeeds, then your TMDB configuration is correct and the issue is with something else.
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"}
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)
## Everything I try to watch fails
**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, 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).
You should have at least 1 Worker registered, if you don't, you should [deploy a worker](../proxy/deploy.mdx#method-1---cloudflare-easy) and [set it up in the client](../client/configuration.mdx#vite_cors_proxy_url).
If any Worker fails the test, you should double check its URL and see if its up to date with the latest updates.
@@ -26,19 +26,19 @@ If any Worker fails the test, you should double check its URL and see if its up
**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.
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 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.](../client/configuration.mdx#vite_backend_url)
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 test gives you an error, your [backend URL configuration option](../client/configuration.mdx#vite_backend_url) likely has a typo.
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.
## 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.
It is likely that you haven't installed the PWA version of movie-web. Please read the [upgrade guide](../client/upgrade.mdx) 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`](../4.backend/2.configuration.md#postgresssl) variable on your backend, enable it and the connection should work.
You are most likely missing the [`postgres.ssl`](../backend/configuration.mdx#postgresssl) variable on your backend, enable it and the connection should work.
## Permission denied to set parameter "session_replication_role"