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
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,8 +22,7 @@
22
22
- Copy `variables.tf.example` to `variables.tf`
23
23
- Open `variables.tf` file.
24
24
- Specify `rds_db_version`, the default is `postgres:16.1`. Only PostgreSQL version can be specified.
25
-
- Set the credentials for database in `cloudbeaver-db-env`. By default it is `postgres`.
26
-
25
+
- You must set the database password in `cloudbeaver-db-env`. The password is empty by default and the service will not start without it.
27
26
5. Configure the deployment in `variables.tf` file as follows:
28
27
- Set your `aws_account_id`, you can get it by logging into your AWS console:
29
28
@@ -33,8 +32,8 @@
33
32
34
33

35
34
36
-
- Ensure that the `alb_certificate_Identifier` variable contains the ID from [AWS Certificate Manager](#importing-an-ssl-certificate-in-aws) corresponding to the domain name specified in the `CLOUDBEAVER_PUBLIC_URL` variable within variables.tf. The domain name in `CLOUDBEAVER_PUBLIC_URL` must match the domain for which the certificates have been issued.
37
-
- You can customize the deployment version by updating the `cloudbeaver_version` environment variable. The default version is `25.2.0`.
35
+
- Ensure that the `alb_certificate_Identifier` variable contains the ID from [AWS Certificate Manager](#importing-an-ssl-certificate-in-aws) corresponding to your domain name. The domain name must match the domain for which the certificates have been issued.
36
+
- You can customize the deployment version by updating the `cloudbeaver_version` environment variable.
38
37
39
38
6. Run `terraform init` and then `terraform apply` in `ecs-fargate` directory to create the ECS cluster and complete the deployment.
Copy file name to clipboardExpand all lines: README.md
+67-2Lines changed: 67 additions & 2 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.3
3
+
### Version 26.0
4
4
5
5
CloudBeaver Enterprise is a client-server application.
6
6
It requires server deployment. You can deploy it in several ways:
@@ -53,6 +53,15 @@ environment:
53
53
```
54
54
This step is only required for Nginx, as HAProxy resolves service names via Docker DNS automatically.
55
55
56
+
#### Java tool options
57
+
58
+
Java does not read system environment variables. To pass Java parameters to the Java process, use the `JAVA_TOOL_OPTIONS` variable in your `.env` file.
### Configuring and starting the CloudBeaver cluster
57
66
1. Clone repository
58
67
```sh
@@ -62,7 +71,7 @@ This step is only required for Nginx, as HAProxy resolves service names via Dock
62
71
- Navigate to `cloudbeaver-deploy`
63
72
- Copy `.env.example` to `.env`
64
73
- Edit the `.env` file to set configuration properties
65
-
-It is highly recommended to change the default database password in `CLOUDBEAVER_DB_PASSWORD` variable
74
+
-You must set the `CLOUDBEAVER_DB_PASSWORD` variable before starting the cluster. The database password is empty by default and the service will not start without it.
66
75
3. Start the cluster
67
76
-`docker-compose up -d` or `docker compose up -d`
68
77
4. Ensure the following TCP ports are available in your network stack
@@ -73,6 +82,61 @@ This step is only required for Nginx, as HAProxy resolves service names via Dock
73
82
### Stopping the cluster
74
83
`docker-compose down`
75
84
85
+
### Using external database
86
+
87
+
By default, CloudBeaver stores all data in an internal PostgreSQL database. If you want to use it, skip this step.
88
+
89
+
If you want to use another database, you can configure it by editing the `.env` file:
90
+
91
+
1. Change `CLOUDBEAVER_DB_DRIVER` to driver for a database you want to use, for example: `postgres-jdbc`/`mariaDB`/`oracle_thin`/`microsoft`
92
+
2. Change `CLOUDBEAVER_DB_URL` to the JDBC connection URL for your database.
93
+
3. Set `CLOUDBEAVER_DB_USER` and `CLOUDBEAVER_DB_PASSWORD` with your database credentials.
94
+
95
+
#### Configure PostgreSQL database
96
+
97
+
Connect to your Postgres database and run:
98
+
```
99
+
CREATE SCHEMA IF NOT EXISTS cb;
100
+
```
101
+
102
+
#### Configure MySQL/MariaDB database
103
+
104
+
**Note:** The MySQL driver is not included by default. To use MySQL as an internal database, connect using the MariaDB driver.
105
+
106
+
Connect to your MariaDB or MySQL database and run:
107
+
```
108
+
CREATE SCHEMA IF NOT EXISTS cb;
109
+
```
110
+
111
+
You might need to add additional parameters to the `CLOUDBEAVER_DB_URL`:
112
+
113
+
-`allowPublicKeyRetrieval=true` — to allow the client to automatically request the public key from the server.
114
+
-`autoReconnect=true` — to prevent the connection from closing after 8 hours of inactivity.
Copy file name to clipboardExpand all lines: k8s/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
@@ -30,6 +30,7 @@ Previously, the volumes were owned by the ‘root’ user, but now they are owne
30
30
-`cd cloudbeaver-deploy/k8s`
31
31
-`cp ./values.yaml.example ./values.yaml`
32
32
- Edit chart values in `values.yaml` (use any text editor)
33
+
- You must set the `cloudbeaver_db_password` variable before deploying the cluster. The database password is empty by default and the deployment will fail without it.
33
34
- Configure domain and SSL certificate (optional)
34
35
- Add an A record in your DNS hosting for a value of `cloudbeaverBaseDomain` variable with load balancer IP address.
35
36
- If you set the *HTTPS* endpoint scheme, then create a valid TLS certificate for the domain endpoint `cloudbeaverBaseDomain` and place it into `k8s/ingressSsl`:
0 commit comments