7.9 KiB

Raw Blame History

Installing AppFlowy-Cloud on an AWS EC2 Ubuntu Instance

This guide provides a step-by-step process for setting up an EC2 instance, installing Docker on Ubuntu, and deploying AppFlowy-Cloud, along with some optional Docker maintenance commands.

Only for demonstration purposes, we will be using a free-tier EC2 instance. However, we recommend using a paid instance for production deployments. If you have any questions, please feel free to reach out to us on Discord.

Setting Up an EC2 Instance

Launch an EC2 Instance:
- Visit the Amazon EC2 console.
- Select your preferred AWS Region.
- Choose "Launch instance" from the EC2 dashboard.
- Optionally, under "Name and tags," provide a name for your instance.
- For "Application and OS Images (Amazon Machine Image)," select "Quick Start" and choose Ubuntu.
- In "Key pair (login)," select an existing key pair or create a new one.
- Review and launch the instance from the Summary panel.

Installing Docker on Your EC2 Ubuntu Instance

Update Packages:
```
sudo apt update
```

Install Prerequisites:

sudo apt install apt-transport-https ca-certificates curl software-properties-common

Add Docker's Official GPG Key:

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -

Add Docker Repository:

sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"

Update Package Database with Docker Packages:
```
sudo apt update
```
Install Docker:
```
sudo apt install docker-ce
```
Check Docker Status:
```
sudo systemctl status docker
```
Add User to Docker Group (optional, to run Docker commands without sudo):
```
sudo usermod -aG docker ${USER}
```

Installing AppFlowy-Cloud

Clone Repository: Access your EC2 instance and clone the AppFlowy-Cloud repository:
```
git clone https://github.com/AppFlowy-IO/AppFlowy-Cloud
cd AppFlowy-Cloud
```
Configuration Setup: Create a .env file from the template. There will be values in the .env that needs to be change according to your needs Kindly read the comments in .env file.
```
cp deploy.env .env
```
Authentication Setup: Update OAuth redirect URIs in .env with your EC2 Public IPv4 DNS, e.g., http:ec2-13-228-28-244.ap-southeast-1.compute.amazonaws.com/gotrue/callback. Refer to the Authentication documentation for detailed setup instructions.
Start AppFlowy Services: Launch the services using Docker Compose:
```
docker-compose up -d
```
Verify Service Status: Check that all services are running:
```
docker ps -a
```

Post Install

Exposing your AppFlowy-Cloud

After installing AppFlowy-Cloud, the server will be serving at port 80 (http) and 443 (http). You might need to add Inbound Rule to expose the port.

To do so, go to EC2 -> Instances -> your instance id -> Security -> Click on the Security Group

Under Inbound Rules, Click "Edit inbound rules"
Click "Add Rule", select either http or https(if you have configured SSL Cert)
Once done, you should be able to see the AppFlowy-Cloud admin page at http://<your_ec2_host>/web/login

Note: There are certain risk involved in exposing ports in your EC2 Instances, this guide is for demonstration purposes and should not be used for production. You might want to limit IP to only trusted IP address, or use other strategies to mitigate risk.

Configuring Environment Secrets for AppFlowy-Cloud Client

Once you've successfully set up AppFlowy Cloud on your server, the next step is to configure the environment secrets for the AppFlowy-Cloud client. These settings are crucial for the client to communicate with your self-hosted server.

Verify Server Functionality:
- Ensure that your AppFlowy Cloud server is up and running without any issues.
Copy Configuration URLs:
- Use the following URLs as your environment secrets. These URLs correspond to the services running on your EC2 instance:
  - APPFLOWY_CLOUD_BASE_URL: http://ec2-13-228-28-244.ap-southeast-1.compute.amazonaws.com
  - APPFLOWY_CLOUD_WS_BASE_URL: ws://ec2-13-228-28-244.ap-southeast-1.compute.amazonaws.com/ws
  - APPFLOWY_CLOUD_GOTRUE_URL: http://ec2-13-228-28-244.ap-southeast-1.compute.amazonaws.com/gotrue
Configure the Client:
- Return to the Building AppFlowy with a Self-hosted Server guide.
- Follow the instructions to input these URLs into the appropriate fields in your AppFlowy-Cloud client's environment settings.

Additional Docker Commands (Optional)

These commands are helpful for Docker maintenance but use them with caution as they can affect your Docker setup.

Remove All Docker Containers:
```
docker rm -f $(sudo docker ps -a)
```
Restart Docker Service:
```
sudo systemctl restart docker
```
Clean Up Docker (excluding volumes):
```
docker system prune -af
```
Remove Docker Volumes:
```
docker system prune -af --volumes
```

Q & A

If you're encountering difficulties redirecting to the AppFlowy application after attempting to log in using Google, GitHub, or Discord OAuth, follow these steps for troubleshooting:

Check OAuth Configuration for Google:
- Ensure GOTRUE_EXTERNAL_GOOGLE_ENABLED is set to true.
- Verify that all other necessary Google OAuth credentials are correctly configured.
Apply Similar Checks for Other OAuth Providers:
- Follow the same verification process for other OAuth providers like GitHub and Discord. Make sure their respective configurations are correctly set.
The provided image illustrates the correct configuration settings.

2. Resolving the 'No Space Left on Device' Error when using free-tier EC2 instance

Encountering a 'No space left on device' error indicates that your device's storage is full. Here's how to resolve this:

1. Check Disk Usage

Start by checking your disk usage. This can be done with the following command in the terminal:

df -h

This command will display a summary of the disk space usage on your device, as shown below:

2. Clean Up Docker System

If your disk is indeed full, a quick way to free up space is by cleaning up your Docker system. Use the command:

docker system prune -af

Caution: This command removes all unused Docker images, containers, volumes, and networks. Be sure to backup any important data before proceeding.

3. Modify Docker Compose Configuration

Alternatively, you can selectively reduce Docker's disk usage:

Disable the Tunnel Server: Temporarily comment out or remove the tunnel server service in the docker-compose.yml file.
Disable Admin Frontend: Similarly, you can disable the admin_frontend service in the docker-compose.yml file. This involves commenting out the relevant sections.

Additionally, ensure that dependencies on the admin_frontend service are also commented out as needed.

7.9 KiB Raw Blame History