I'm trying to setup Appwrite in a server, first issue is that I wasn't able to download the docker-compose and the .env from the links provided in the doc. but I found my way around and used them from the CLI.
- Is it safe to use a standalone MariaDB (instead of the dockerized one) after removing the service from docker-compose as well as the dependency from other services?
- Is it safe to change the HTTPS port "443"?
- Is it safe to change the default web port "80"?
Hey,
for your questions
Is standalone MariaDB safe? Sure! just make sure it's up and running before you're starting the docker compose. and the values in the
.envfile are a match to your local one.
Is it safe to change the HTTPS port "443"? Totally! as long as your connection is with SSL you'll get the same level of data-protection.
Is it safe to change the default web port "80"? Yes, although it's recommend to force SSL by setting the `_APP_OPTIONS_FORCE_HTTPS` to
enabled
The reason to use 443/80 is for the convince of not needing to write ports and letting the browser handle it for you.
Also for self-hosting I also recommending taking a look at this
And yes, it looks like the manual is missing the links to the .env and docker-compose.yml files.
I highly recommend having your Appwrite instance exposed on the standard ports. Some things might not work properly like certificates or oauth redirects if not on standard ports.
Im running self-hosted and had troubles with **not ** exposing appwrite on 443 and 80 respectively.
if you need help, please create a new <#1072905050399191082> post rather than posting on an old thread
I dont, it was just a supplying comment.
Recommended threads
- Upgrading selfhost version?
It is okay to upgrade version to higher one, of my current version is 1.7.4 to 1.8.1. Is that safe to do cause my clients already have data on that? Also is a...
- Appwrite cloud DB server error 500
Getting this error
- appwrite indexes not working (?
i have this index: ``` "indexes": [ { "key": "single-user-per-event", "type": "unique", ...