Tutorial for setting up AppFlowy on Hetzner Cloud #959

suntorytimed · 2024-10-01T12:02:12Z

using Hetzner Cloud server
using Hetzner Cloud Object Storage

The server and credentials used in the tutorial and shown in the screenshot got deleted and don't need to be censored.

* using Hetzner Cloud server * using Hetzner Cloud Object Storage

LenzGr · 2024-10-02T16:54:02Z

tutorials/install-and-configure-appflowy-with-hetzner-object-storage/01.en.md

+
+## Introduction
+
+In this tutorial we are going to setup our own AppFlowy Cloud server using the official documentation by AppFlowy. We will use a Hetzner Cloud Server and the new Hetzner Object Storage. This tutorial won't cover how you create a new project called "AppFlowy", and how Hetzner Cloud servers are created. We will purely focus on setting up AppFlowy, setting up a bucket and connecting it to our AppFlowy Cloud server.


Maybe add a few links here?

Suggested change

In this tutorial we are going to setup our own AppFlowy Cloud server using the official documentation by AppFlowy. We will use a Hetzner Cloud Server and the new Hetzner Object Storage. This tutorial won't cover how you create a new project called "AppFlowy", and how Hetzner Cloud servers are created. We will purely focus on setting up AppFlowy, setting up a bucket and connecting it to our AppFlowy Cloud server.

In this tutorial we are going to setup our own [AppFlowy](https://appflowy.io/) Cloud server using the official documentation by AppFlowy. We will use a [Hetzner Cloud Server](https://hetzner.cloud) and the new [Hetzner Object Storage](https://docs.hetzner.com/storage/object-storage). This tutorial won't cover how you create a new project called "AppFlowy", and how Hetzner Cloud servers are created. We will purely focus on setting up AppFlowy, setting up a bucket and connecting it to our AppFlowy Cloud server.

LenzGr · 2024-10-02T16:56:24Z

tutorials/install-and-configure-appflowy-with-hetzner-object-storage/01.en.md

+
+```
+
+Remove following lines from the deploy.env, as we won't use those services:


Suggested change

Remove following lines from the deploy.env, as we won't use those services:

Remove following lines from the `deploy.env`file, as we won't use those services:

LenzGr · 2024-10-02T16:56:45Z

tutorials/install-and-configure-appflowy-with-hetzner-object-storage/01.en.md

+
+### Step 2.4 - Adjust the deploy.env
+
+Now we need to adjust the deploy.env file to use our own passwords and point to the Hetzner Object Storage. I recommend to keep the order of values identical, as we are going to commit our changes locally. This makes rebasing easier. At the time of creation of this tutorial you should adjust following values with your own password and SMTP configuration:


Suggested change

Now we need to adjust the deploy.env file to use our own passwords and point to the Hetzner Object Storage. I recommend to keep the order of values identical, as we are going to commit our changes locally. This makes rebasing easier. At the time of creation of this tutorial you should adjust following values with your own password and SMTP configuration:

Now we need to adjust the `deploy.env` file to use our own passwords and point to the Hetzner Object Storage. I recommend to keep the order of values identical, as we are going to commit our changes locally. This makes rebasing easier. At the time of creation of this tutorial you should adjust following values with your own password and SMTP configuration:

LenzGr · 2024-10-02T16:57:43Z

tutorials/install-and-configure-appflowy-with-hetzner-object-storage/01.en.md

+
+### Step 2.5 - Add and commit your changes
+
+Now we use git to store our changes in the git log and make it easier to pull updates from upstream. By using this method every change of defaults in the deploy.env and docker-compose.yml will result in merge conflicts when pulling an update, which you need to resolve before restarting/updating your server.


Suggested change

Now we use git to store our changes in the git log and make it easier to pull updates from upstream. By using this method every change of defaults in the deploy.env and docker-compose.yml will result in merge conflicts when pulling an update, which you need to resolve before restarting/updating your server.

Now we use git to store our changes in the git log and make it easier to pull updates from upstream. By using this method every change of defaults in the `deploy.env` and `docker-compose.yml` will result in merge conflicts when pulling an update, which you need to resolve before restarting/updating your server.

LenzGr · 2024-10-02T16:58:35Z

tutorials/install-and-configure-appflowy-with-hetzner-object-storage/01.en.md

+
+### Step 2.2 - Setup the nginx proxy of AppFlowy Cloud to use your SSL certificate
+
+Put your SSL certificate and private key in the folder ./nginx/ssl/ or adjust the location in the docker-compose.yml to point to your own certificates. Alternatively you can create a Let's Encrypt SSL certificate via DNS challenge on the Hetzner DNS service by using lego:


Suggested change

Put your SSL certificate and private key in the folder ./nginx/ssl/ or adjust the location in the docker-compose.yml to point to your own certificates. Alternatively you can create a Let's Encrypt SSL certificate via DNS challenge on the Hetzner DNS service by using lego:

Put your SSL certificate and private key in the folder `./nginx/ssl/` or adjust the location in the `docker-compose.yml` to point to your own certificates. Alternatively you can create a Let's Encrypt SSL certificate via DNS challenge on the Hetzner DNS service by using lego:

LenzGr · 2024-10-02T16:58:57Z

tutorials/install-and-configure-appflowy-with-hetzner-object-storage/01.en.md

+~/go/bin/lego --domains="appflowy.example.com" --email="[email protected]" --http run
+```
+
+And adjust the docker-compose.yml to point to the output folder of lego:


Suggested change

And adjust the docker-compose.yml to point to the output folder of lego:

And adjust the `docker-compose.yml` to point to the output folder of lego:

LenzGr · 2024-10-02T16:59:12Z

tutorials/install-and-configure-appflowy-with-hetzner-object-storage/01.en.md

+
+### Step 2.3 - Remove the minio service from the docker-compose.yml
+
+Remove the minio service from the docker-compose.yml by deleting following lines:


Suggested change

Remove the minio service from the docker-compose.yml by deleting following lines:

Remove the minio service from the `docker-compose.yml` by deleting following lines:

LenzGr · 2024-10-02T16:59:39Z

tutorials/install-and-configure-appflowy-with-hetzner-object-storage/01.en.md

+      - minio_data:/data
+```
+
+Don't forget to remove the minio_data volume from the volumes at the end of the docker-compose.yml. Only the postgres_data volume should remain:


Suggested change

Don't forget to remove the minio_data volume from the volumes at the end of the docker-compose.yml. Only the postgres_data volume should remain:

Don't forget to remove the `minio_data` volume from the volumes at the end of the `docker-compose.yml`. Only the `postgres_data `volume should remain:

LenzGr · 2024-10-02T17:00:15Z

tutorials/install-and-configure-appflowy-with-hetzner-object-storage/01.en.md

+
+## Step 3
+
+Start you AppFlowy Cloud server via docker-compose (or docker compose, depending on your installation method):


Suggested change

Start you AppFlowy Cloud server via docker-compose (or docker compose, depending on your installation method):

Start you AppFlowy Cloud server via `docker-compose` (or `docker compose`, depending on your installation method):

tutorial for setting up AppFlowy on Hetzner Cloud

48bf9e4

* using Hetzner Cloud server * using Hetzner Cloud Object Storage

LenzGr reviewed Oct 2, 2024

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Tutorial for setting up AppFlowy on Hetzner Cloud #959

Tutorial for setting up AppFlowy on Hetzner Cloud #959

suntorytimed commented Oct 1, 2024

LenzGr Oct 2, 2024

LenzGr Oct 2, 2024

LenzGr Oct 2, 2024

LenzGr Oct 2, 2024

LenzGr Oct 2, 2024

LenzGr Oct 2, 2024

LenzGr Oct 2, 2024

LenzGr Oct 2, 2024

LenzGr Oct 2, 2024


		## Introduction

		In this tutorial we are going to setup our own AppFlowy Cloud server using the official documentation by AppFlowy. We will use a Hetzner Cloud Server and the new Hetzner Object Storage. This tutorial won't cover how you create a new project called "AppFlowy", and how Hetzner Cloud servers are created. We will purely focus on setting up AppFlowy, setting up a bucket and connecting it to our AppFlowy Cloud server.


		```

		Remove following lines from the deploy.env, as we won't use those services:

	Remove following lines from the deploy.env, as we won't use those services:
	Remove following lines from the `deploy.env`file, as we won't use those services:


		### Step 2.4 - Adjust the deploy.env

		Now we need to adjust the deploy.env file to use our own passwords and point to the Hetzner Object Storage. I recommend to keep the order of values identical, as we are going to commit our changes locally. This makes rebasing easier. At the time of creation of this tutorial you should adjust following values with your own password and SMTP configuration:

	Now we need to adjust the deploy.env file to use our own passwords and point to the Hetzner Object Storage. I recommend to keep the order of values identical, as we are going to commit our changes locally. This makes rebasing easier. At the time of creation of this tutorial you should adjust following values with your own password and SMTP configuration:
	Now we need to adjust the `deploy.env` file to use our own passwords and point to the Hetzner Object Storage. I recommend to keep the order of values identical, as we are going to commit our changes locally. This makes rebasing easier. At the time of creation of this tutorial you should adjust following values with your own password and SMTP configuration:


		### Step 2.5 - Add and commit your changes

		Now we use git to store our changes in the git log and make it easier to pull updates from upstream. By using this method every change of defaults in the deploy.env and docker-compose.yml will result in merge conflicts when pulling an update, which you need to resolve before restarting/updating your server.


		### Step 2.2 - Setup the nginx proxy of AppFlowy Cloud to use your SSL certificate

		Put your SSL certificate and private key in the folder ./nginx/ssl/ or adjust the location in the docker-compose.yml to point to your own certificates. Alternatively you can create a Let's Encrypt SSL certificate via DNS challenge on the Hetzner DNS service by using lego:

	And adjust the docker-compose.yml to point to the output folder of lego:
	And adjust the `docker-compose.yml` to point to the output folder of lego:


		### Step 2.3 - Remove the minio service from the docker-compose.yml

		Remove the minio service from the docker-compose.yml by deleting following lines:

	Remove the minio service from the docker-compose.yml by deleting following lines:
	Remove the minio service from the `docker-compose.yml` by deleting following lines:

	Don't forget to remove the minio_data volume from the volumes at the end of the docker-compose.yml. Only the postgres_data volume should remain:
	Don't forget to remove the `minio_data` volume from the volumes at the end of the `docker-compose.yml`. Only the `postgres_data `volume should remain:


		## Step 3

		Start you AppFlowy Cloud server via docker-compose (or docker compose, depending on your installation method):

	Start you AppFlowy Cloud server via docker-compose (or docker compose, depending on your installation method):
	Start you AppFlowy Cloud server via `docker-compose` (or `docker compose`, depending on your installation method):

Tutorial for setting up AppFlowy on Hetzner Cloud #959

Are you sure you want to change the base?

Tutorial for setting up AppFlowy on Hetzner Cloud #959

Conversation

suntorytimed commented Oct 1, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment