You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AWS/ecs-fargate/README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,7 @@
19
19
20
20
**Note:** only [Amazon RDS for PostgreSQL](https://aws.amazon.com/rds/postgresql/) is supported. RDS database will be set up as an internal database for this deployment.
21
21
- Navigate to `cloudbeaver-deploy/AWS/ecs-fargate`
22
+
- Copy `variables.tf.example` to `variables.tf`
22
23
- Open `variables.tf` file.
23
24
- Specify `rds_db_version`, the default is `postgres:16.1`. Only PostgreSQL version can be specified.
24
25
- Set the credentials for database in `cloudbeaver-db-env`. By default it is `postgres`.
Copy file name to clipboardExpand all lines: README.md
+36-8Lines changed: 36 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# CloudBeaver Enterprise deployment
2
2
3
-
### Version 25.0
3
+
### Version 25.1
4
4
5
5
CloudBeaver Enterprise is a client-server application.
6
6
It requires server deployment. You can deploy it on a single host (e.g. your local computer) or in a cloud.
@@ -11,9 +11,7 @@ It is the simplest way to install [CloudBeaver Enterprise Edition](https://dbeav
11
11
All you need is a Linux, macOS, or Windows machine with Docker.
12
12
13
13
CloudBeaver can be run in a [single docker container](https://dbeaver.com/docs/cloudbeaver/CloudBeaver-Enterprise-deployment-from-docker-image/).
14
-
However you can use Docker compose for additional product features such as:
15
-
- Load balancing
16
-
- Easy web server (HTTPS) configuration
14
+
However you can use Docker compose for easy web server (HTTPS) configuration.
17
15
18
16
### System requirements
19
17
- Minimum 4GB RAM
@@ -30,20 +28,49 @@ If a user with ‘UID=8978’ already exists in your environment, permission con
30
28
Additionally, the default Docker volumes directory’s ownership has changed.
31
29
Previously, the volumes were owned by the ‘root’ user, but now they are owned by the ‘dbeaver’ user (‘UID=8978’).
32
30
31
+
### Configuring proxy server (Nginx / HAProxy)
32
+
33
+
Starting from v25.1, CloudBeaver supports two types of proxy servers: Nginx and HAProxy. You can choose your preferred proxy type by setting the following variable in the .env file:
34
+
35
+
`PROXY_TYPE=haproxy` # Available options: nginx, haproxy
36
+
37
+
The default value is `haproxy`. Switching between proxy types is seamless: configuration files and SSL certificates are retained due to shared Docker volumes.
38
+
However, note that the container name has changed from `nginx` to `web-proxy`.
39
+
40
+
#### Proxy listen ports
41
+
42
+
When using Docker Compose with host networking mode (network_mode: host), you may configure proxy ports using these environment variables:
43
+
```
44
+
LISTEN_PORT_HTTP=80
45
+
LISTEN_PORT_HTTPS=443
46
+
```
47
+
These variables specify which ports the proxy listens to inside the container.
48
+
49
+
#### Notes for Nginx users
50
+
51
+
If you use Nginx as your proxy server and customize the `COMPOSE_PROJECT_NAME` in your .env file, make sure to pass this variable explicitly to the container environment:
52
+
```
53
+
environment:
54
+
- COMPOSE_PROJECT_NAME=${COMPOSE_PROJECT_NAME}
55
+
```
56
+
This step is only required for Nginx, as HAProxy resolves service names via Docker DNS automatically.
57
+
33
58
### Configuring and starting the CloudBeaver cluster
0 commit comments