diff --git a/packages/dolt/content/architecture/sql/go-mysql-server.md b/packages/dolt/content/architecture/sql/go-mysql-server.md
index 3c606eed2..6155b82c8 100644
--- a/packages/dolt/content/architecture/sql/go-mysql-server.md
+++ b/packages/dolt/content/architecture/sql/go-mysql-server.md
@@ -2,8 +2,6 @@
title: Go MySQL Server
---
-# Go MySQL Server
-
[go-mysql-server](https://github.com/dolthub/go-mysql-server) is the
query engine for Dolt. It's a MySQL compatible parser, server, and
query execution engine written in pure Go. As with Dolt, its goal is
diff --git a/packages/dolt/content/architecture/sql/vitess.md b/packages/dolt/content/architecture/sql/vitess.md
index b1d0026e4..04ebbfe4e 100644
--- a/packages/dolt/content/architecture/sql/vitess.md
+++ b/packages/dolt/content/architecture/sql/vitess.md
@@ -2,8 +2,6 @@
title: Vitess
---
-# Vitess
-
Dolt's SQL server runs on [a fork of
Vitess](https://github.com/dolthub/vitess). Vitess is a MySQL database
sharding solution that was created to scale YouTube:
diff --git a/packages/dolt/content/concepts/dolt/rdbms/replication.md b/packages/dolt/content/concepts/dolt/rdbms/replication.md
index 982de2365..bccc4b933 100644
--- a/packages/dolt/content/concepts/dolt/rdbms/replication.md
+++ b/packages/dolt/content/concepts/dolt/rdbms/replication.md
@@ -2,8 +2,6 @@
title: Replication
---
-# Replication
-
## What is Replication?
Replication is the ability for an RDBMS to synchronize a primary server with one or more read replicas. In this configuration, the primary database serves reads and writes while the replicas only serve reads.
diff --git a/packages/dolt/content/introduction/installation/application-server.md b/packages/dolt/content/introduction/installation/application-server.md
index e8b0f6a25..2b85b46a4 100644
--- a/packages/dolt/content/introduction/installation/application-server.md
+++ b/packages/dolt/content/introduction/installation/application-server.md
@@ -2,8 +2,6 @@
title: Application Server
---
-# Application Server
-
These instructions are for bootstrapping dolt as an application
database server. They assume you are starting from scratch on a Linux
machine without dolt installed or running.
diff --git a/packages/dolt/content/other/versioning.md b/packages/dolt/content/other/versioning.md
index b464d26ae..3c0627782 100644
--- a/packages/dolt/content/other/versioning.md
+++ b/packages/dolt/content/other/versioning.md
@@ -2,15 +2,14 @@
title: Versioning
---
-# Versioning
-
Dolt uses a three digit versioning format – `major`.`minor`.`patch`. For major, minor, and patch version bumps, you can expect:
-- **Patch version bumps** (e.g. `1.0.0` → `1.0.1`) – Patch version bumps will **NOT** change any interfaces; they include bug fixes, performance improvements, and additive features. You can safely pick up patch releases without having to update your application code.
-- **Minor version bumps** (e.g. `1.0.0` → `1.1.0`) – Minor version bumps signal that the release contains an interface change, such as changing the signature of a Dolt CLI command or stored procedure. Your application code may require an update to move to a minor version bump if it is using an affected interface. Affected interfaces are called out in release notes.
+
+- **Patch version bumps** (e.g. `1.0.0` → `1.0.1`) – Patch version bumps will **NOT** change any interfaces; they include bug fixes, performance improvements, and additive features. You can safely pick up patch releases without having to update your application code.
+- **Minor version bumps** (e.g. `1.0.0` → `1.1.0`) – Minor version bumps signal that the release contains an interface change, such as changing the signature of a Dolt CLI command or stored procedure. Your application code may require an update to move to a minor version bump if it is using an affected interface. Affected interfaces are called out in release notes.
- **Major version bumps** (e.g. `1.0.0` → `2.0.0`) - Major version bumps signal a significant change that requires database data to be migrated, for example, [moving to a new low-level storage format](https://www.dolthub.com/blog/2022-11-01-dolthub-migrate-button/). Major version bumps will be extremely rare.
# Internal Feature Version
-In addition to the external version number, Dolt also uses an internal "feature" version that is incremented when persisted data structures change in a backwards incompatible way. When you use a version of Dolt with a new feature version, once it writes data to your database, older clients with a lower feature version will no longer be able to read or write that database. You can check the feature version of your database by running `dolt version --feature` from within the database's directory.
+In addition to the external version number, Dolt also uses an internal "feature" version that is incremented when persisted data structures change in a backwards incompatible way. When you use a version of Dolt with a new feature version, once it writes data to your database, older clients with a lower feature version will no longer be able to read or write that database. You can check the feature version of your database by running `dolt version --feature` from within the database's directory.
-Feature version bumps will be called out in a version's release notes and will be released as a minor version bump. We avoid feature bumps as much as possible because they can be disruptive to customers, but they are occasionally needed when an existing data structure does not provide enough forward compatibility to support a new feature.
+Feature version bumps will be called out in a version's release notes and will be released as a minor version bump. We avoid feature bumps as much as possible because they can be disruptive to customers, but they are occasionally needed when an existing data structure does not provide enough forward compatibility to support a new feature.
diff --git a/packages/dolt/content/reference/cli/git-comparison.md b/packages/dolt/content/reference/cli/git-comparison.md
index cd5f56ab2..1e52e42db 100644
--- a/packages/dolt/content/reference/cli/git-comparison.md
+++ b/packages/dolt/content/reference/cli/git-comparison.md
@@ -4,8 +4,6 @@ title: "Git Comparison"
We aim to match our CLI command behavior as closely to their Git equivalent as possible. This page lists the commands that are currently supported, and any known limitations.
-# Git Comparison
-
## Setup and Config
| Component | Supported | Notes and limitations |
@@ -67,10 +65,10 @@ We aim to match our CLI command behavior as closely to their Git equivalent as p
## Patching
| Component | Supported | Notes and limitations |
-| :------------ |:----------| :-------------------- |
-| `cherry-pick` | ✅ | |
-| `rebase` | ✅ | |
-| `revert` | ✅ | |
+| :------------ | :-------- | :-------------------- |
+| `cherry-pick` | ✅ | |
+| `rebase` | ✅ | |
+| `revert` | ✅ | |
## Debugging
@@ -82,13 +80,12 @@ We aim to match our CLI command behavior as closely to their Git equivalent as p
## Administration
| Component | Supported | Notes and limitations |
-|:----------------|:----------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| :-------------- | :-------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `clean` | 🟠 | [does not completely match Git's behavior](https://github.com/dolthub/dolt/issues/6313) |
-| `gc` | ✅ | |
-| `fsck` | ❌ | |
-| `reflog` | ✅ | [does not completely match Git's behavior](https://www.dolthub.com/blog/2023-11-17-dolt-reflog/):
only supports named references (not Git's special refs) shows deleted refs |
-| `filter-branch` | ✅ | |
-
+| `gc` | ✅ | |
+| `fsck` | ❌ | |
+| `reflog` | ✅ | [does not completely match Git's behavior](https://www.dolthub.com/blog/2023-11-17-dolt-reflog/):
only supports named references (not Git's special refs) shows deleted refs |
+| `filter-branch` | ✅ | |
## Plumbing Commands
diff --git a/packages/doltgres/content/.gitbook/assets/create_dynamo_table.png b/packages/doltgres/content/.gitbook/assets/create_dynamo_table.png
new file mode 100644
index 000000000..6d37abcf7
Binary files /dev/null and b/packages/doltgres/content/.gitbook/assets/create_dynamo_table.png differ
diff --git a/packages/doltgres/.gitbook/assets/doltgres-preview.png b/packages/doltgres/content/.gitbook/assets/doltgres-preview.png
similarity index 100%
rename from packages/doltgres/.gitbook/assets/doltgres-preview.png
rename to packages/doltgres/content/.gitbook/assets/doltgres-preview.png
diff --git a/packages/doltgres/content/.gitbook/assets/how-garbage-is-created.png b/packages/doltgres/content/.gitbook/assets/how-garbage-is-created.png
new file mode 100644
index 000000000..2f0b2f5ec
Binary files /dev/null and b/packages/doltgres/content/.gitbook/assets/how-garbage-is-created.png differ
diff --git a/packages/doltgres/content/.gitbook/assets/saved-query-dolthub.png b/packages/doltgres/content/.gitbook/assets/saved-query-dolthub.png
new file mode 100644
index 000000000..259d3a191
Binary files /dev/null and b/packages/doltgres/content/.gitbook/assets/saved-query-dolthub.png differ
diff --git a/packages/doltgres/content/concepts/rdbms/replication.md b/packages/doltgres/content/concepts/rdbms/replication.md
index 0dc54a7fc..658fe1785 100644
--- a/packages/doltgres/content/concepts/rdbms/replication.md
+++ b/packages/doltgres/content/concepts/rdbms/replication.md
@@ -2,8 +2,6 @@
title: Replication
---
-# Replication
-
## What is Replication?
Replication is the ability for an RDBMS to synchronize a primary server with one or more read
diff --git a/packages/doltgres/content/introduction/README.md b/packages/doltgres/content/introduction/README.md
index 59e5cc513..ea241099f 100644
--- a/packages/doltgres/content/introduction/README.md
+++ b/packages/doltgres/content/introduction/README.md
@@ -1,4 +1,4 @@
-
+
DoltgreSQL, or Doltgres for short, is a Postgres-compatible version of [Dolt](https://www.doltdb.com). It is currently in [pre-alpha release](#doltgres-is-pre-alpha). Dolt is the world's first version controlled SQL database. It is like Git and MySQL had a baby. Doltgres is like Git and Postgres had a baby.
diff --git a/packages/doltgres/content/reference/sql/server/backups.md b/packages/doltgres/content/reference/sql/server/backups.md
index df6d0288e..a30583ac9 100644
--- a/packages/doltgres/content/reference/sql/server/backups.md
+++ b/packages/doltgres/content/reference/sql/server/backups.md
@@ -54,7 +54,7 @@ pushing to a remote can serve as a backup for some use cases.
### Configure a remote
-This example uses DoltgresHub as a remote, but you can use Doltgres with [other remotes like
+This example uses DoltHub as a remote, but you can use Doltgres with [other remotes like
filesystem, AWS S3, and GCS](https://www.dolthub.com/blog/2021-07-19-remotes/).
```sql
diff --git a/packages/doltgres/content/reference/sql/server/replication.md b/packages/doltgres/content/reference/sql/server/replication.md
index 526a801b0..b5f17242c 100644
--- a/packages/doltgres/content/reference/sql/server/replication.md
+++ b/packages/doltgres/content/reference/sql/server/replication.md
@@ -101,7 +101,7 @@ call dolt_commit('-Am', 'trigger replication');
After a `DOLT_COMMIT()`, changes are pushed to the configured remote.
-
+
#### Stopping Replication
@@ -184,7 +184,7 @@ You must restart the replica server for changes to take effect.
Now back on the primary:
```sql
-insert into test values (2,2);
+insert into test values (2,2);
call dolt_commit('-am', 'Inserted (2,2)');
+----------------------------------+
| hash |
@@ -224,7 +224,7 @@ Now I'm going to make a new branch on the primary and insert a new value on it.
```sql
call dolt_checkout('-b', 'branch1');
-insert into test values (3,3);
+insert into test values (3,3);
call dolt_commit('-am', 'Inserted (3,3)');
```
@@ -315,8 +315,8 @@ On `dolt-1.db`, we will have a `config.yaml` like:
```yaml
cluster:
standby_remotes:
- - name: standby
- remote_url_template: http://dolt-2.db:50051/{database}
+ - name: standby
+ remote_url_template: http://dolt-2.db:50051/{database}
bootstrap_role: primary
bootstrap_epoch: 1
remotesapi:
@@ -328,8 +328,8 @@ On `dolt-2.db`, we will have:
```yaml
cluster:
standby_remotes:
- - name: standby
- remote_url_template: http://dolt-1.db:50051/{database}
+ - name: standby
+ remote_url_template: http://dolt-1.db:50051/{database}
bootstrap_role: standby
bootstrap_epoch: 1
remotesapi:
@@ -660,9 +660,9 @@ things to consider when choosing how to configure replication.
files to a remote storage solution and having the read replica download the
files from there. On the other hand, direct replication may be less scalable in
the number of read replicas which it can gracefully handle, since the primary
- itself is responsible for pushing each write to each standby server. For read
- replicas, read latency for direct replication is always faster, since no
- communication to a remote must take place. You can expect increased read latency
+ itself is responsible for pushing each write to each standby server. For read
+ replicas, read latency for direct replication is always faster, since no
+ communication to a remote must take place. You can expect increased read latency
on every transaction start of aremote-based read replica.
4. The ability to replicate writes with direct replication is not coupled with
diff --git a/packages/doltlab/.gitbook/assets/aws_remote_backup_dynamodb.png b/packages/doltlab/content/.gitbook/assets/aws_remote_backup_dynamodb.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/aws_remote_backup_dynamodb.png
rename to packages/doltlab/content/.gitbook/assets/aws_remote_backup_dynamodb.png
diff --git a/packages/doltlab/.gitbook/assets/aws_remote_backup_dynamodb_example.png b/packages/doltlab/content/.gitbook/assets/aws_remote_backup_dynamodb_example.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/aws_remote_backup_dynamodb_example.png
rename to packages/doltlab/content/.gitbook/assets/aws_remote_backup_dynamodb_example.png
diff --git a/packages/doltlab/.gitbook/assets/aws_remote_backup_s3.png b/packages/doltlab/content/.gitbook/assets/aws_remote_backup_s3.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/aws_remote_backup_s3.png
rename to packages/doltlab/content/.gitbook/assets/aws_remote_backup_s3.png
diff --git a/packages/doltlab/.gitbook/assets/aws_remote_backup_s3_example.png b/packages/doltlab/content/.gitbook/assets/aws_remote_backup_s3_example.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/aws_remote_backup_s3_example.png
rename to packages/doltlab/content/.gitbook/assets/aws_remote_backup_s3_example.png
diff --git a/packages/doltlab/.gitbook/assets/create_deployment_1.png b/packages/doltlab/content/.gitbook/assets/create_deployment_1.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/create_deployment_1.png
rename to packages/doltlab/content/.gitbook/assets/create_deployment_1.png
diff --git a/packages/doltlab/.gitbook/assets/create_deployment_2.png b/packages/doltlab/content/.gitbook/assets/create_deployment_2.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/create_deployment_2.png
rename to packages/doltlab/content/.gitbook/assets/create_deployment_2.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab-custom-logo.png b/packages/doltlab/content/.gitbook/assets/doltlab-custom-logo.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab-custom-logo.png
rename to packages/doltlab/content/.gitbook/assets/doltlab-custom-logo.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab-enterprise-works.png b/packages/doltlab/content/.gitbook/assets/doltlab-enterprise-works.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab-enterprise-works.png
rename to packages/doltlab/content/.gitbook/assets/doltlab-enterprise-works.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab-labeled-colors.png b/packages/doltlab/content/.gitbook/assets/doltlab-labeled-colors.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab-labeled-colors.png
rename to packages/doltlab/content/.gitbook/assets/doltlab-labeled-colors.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab-preview.png b/packages/doltlab/content/.gitbook/assets/doltlab-preview.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab-preview.png
rename to packages/doltlab/content/.gitbook/assets/doltlab-preview.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab-starbucks-logo.png b/packages/doltlab/content/.gitbook/assets/doltlab-starbucks-logo.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab-starbucks-logo.png
rename to packages/doltlab/content/.gitbook/assets/doltlab-starbucks-logo.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab-starbucks.png b/packages/doltlab/content/.gitbook/assets/doltlab-starbucks.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab-starbucks.png
rename to packages/doltlab/content/.gitbook/assets/doltlab-starbucks.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab_nlb_basic_config.png b/packages/doltlab/content/.gitbook/assets/doltlab_nlb_basic_config.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab_nlb_basic_config.png
rename to packages/doltlab/content/.gitbook/assets/doltlab_nlb_basic_config.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab_nlb_listeners.png b/packages/doltlab/content/.gitbook/assets/doltlab_nlb_listeners.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab_nlb_listeners.png
rename to packages/doltlab/content/.gitbook/assets/doltlab_nlb_listeners.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab_nlb_security_group.png b/packages/doltlab/content/.gitbook/assets/doltlab_nlb_security_group.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab_nlb_security_group.png
rename to packages/doltlab/content/.gitbook/assets/doltlab_nlb_security_group.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab_nlb_select_load_balancer.png b/packages/doltlab/content/.gitbook/assets/doltlab_nlb_select_load_balancer.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab_nlb_select_load_balancer.png
rename to packages/doltlab/content/.gitbook/assets/doltlab_nlb_select_load_balancer.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab_okta_app.png b/packages/doltlab/content/.gitbook/assets/doltlab_okta_app.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab_okta_app.png
rename to packages/doltlab/content/.gitbook/assets/doltlab_okta_app.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab_okta_settings.png b/packages/doltlab/content/.gitbook/assets/doltlab_okta_settings.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab_okta_settings.png
rename to packages/doltlab/content/.gitbook/assets/doltlab_okta_settings.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab_profile_settings.png b/packages/doltlab/content/.gitbook/assets/doltlab_profile_settings.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab_profile_settings.png
rename to packages/doltlab/content/.gitbook/assets/doltlab_profile_settings.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab_saml_settings.png b/packages/doltlab/content/.gitbook/assets/doltlab_saml_settings.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab_saml_settings.png
rename to packages/doltlab/content/.gitbook/assets/doltlab_saml_settings.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab_saml_signin.png b/packages/doltlab/content/.gitbook/assets/doltlab_saml_signin.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab_saml_signin.png
rename to packages/doltlab/content/.gitbook/assets/doltlab_saml_signin.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab_target_group_health_checks.png b/packages/doltlab/content/.gitbook/assets/doltlab_target_group_health_checks.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab_target_group_health_checks.png
rename to packages/doltlab/content/.gitbook/assets/doltlab_target_group_health_checks.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab_target_group_register_targets.png b/packages/doltlab/content/.gitbook/assets/doltlab_target_group_register_targets.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab_target_group_register_targets.png
rename to packages/doltlab/content/.gitbook/assets/doltlab_target_group_register_targets.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab_target_group_type.png b/packages/doltlab/content/.gitbook/assets/doltlab_target_group_type.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab_target_group_type.png
rename to packages/doltlab/content/.gitbook/assets/doltlab_target_group_type.png
diff --git a/packages/doltlab/.gitbook/assets/doltlab_target_group_vpc.png b/packages/doltlab/content/.gitbook/assets/doltlab_target_group_vpc.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/doltlab_target_group_vpc.png
rename to packages/doltlab/content/.gitbook/assets/doltlab_target_group_vpc.png
diff --git a/packages/doltlab/.gitbook/assets/enable_writes.png b/packages/doltlab/content/.gitbook/assets/enable_writes.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/enable_writes.png
rename to packages/doltlab/content/.gitbook/assets/enable_writes.png
diff --git a/packages/doltlab/.gitbook/assets/gcp_remote_backup_bucket.png b/packages/doltlab/content/.gitbook/assets/gcp_remote_backup_bucket.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/gcp_remote_backup_bucket.png
rename to packages/doltlab/content/.gitbook/assets/gcp_remote_backup_bucket.png
diff --git a/packages/doltlab/.gitbook/assets/gcp_remote_backup_bucket_example.png b/packages/doltlab/content/.gitbook/assets/gcp_remote_backup_bucket_example.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/gcp_remote_backup_bucket_example.png
rename to packages/doltlab/content/.gitbook/assets/gcp_remote_backup_bucket_example.png
diff --git a/packages/doltlab/.gitbook/assets/getting-started/admin-logged-in-fresh-doltlab.png b/packages/doltlab/content/.gitbook/assets/getting-started/admin-logged-in-fresh-doltlab.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/getting-started/admin-logged-in-fresh-doltlab.png
rename to packages/doltlab/content/.gitbook/assets/getting-started/admin-logged-in-fresh-doltlab.png
diff --git a/packages/doltlab/.gitbook/assets/getting-started/create-new-key-pair.png b/packages/doltlab/content/.gitbook/assets/getting-started/create-new-key-pair.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/getting-started/create-new-key-pair.png
rename to packages/doltlab/content/.gitbook/assets/getting-started/create-new-key-pair.png
diff --git a/packages/doltlab/.gitbook/assets/getting-started/doltlab-add-credentials.png b/packages/doltlab/content/.gitbook/assets/getting-started/doltlab-add-credentials.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/getting-started/doltlab-add-credentials.png
rename to packages/doltlab/content/.gitbook/assets/getting-started/doltlab-add-credentials.png
diff --git a/packages/doltlab/.gitbook/assets/getting-started/doltlab-admin-db.png b/packages/doltlab/content/.gitbook/assets/getting-started/doltlab-admin-db.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/getting-started/doltlab-admin-db.png
rename to packages/doltlab/content/.gitbook/assets/getting-started/doltlab-admin-db.png
diff --git a/packages/doltlab/.gitbook/assets/getting-started/doltlab-aws-ec2-instance-type.png b/packages/doltlab/content/.gitbook/assets/getting-started/doltlab-aws-ec2-instance-type.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/getting-started/doltlab-aws-ec2-instance-type.png
rename to packages/doltlab/content/.gitbook/assets/getting-started/doltlab-aws-ec2-instance-type.png
diff --git a/packages/doltlab/.gitbook/assets/getting-started/doltlab-aws-ec2-launch-summary.png b/packages/doltlab/content/.gitbook/assets/getting-started/doltlab-aws-ec2-launch-summary.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/getting-started/doltlab-aws-ec2-launch-summary.png
rename to packages/doltlab/content/.gitbook/assets/getting-started/doltlab-aws-ec2-launch-summary.png
diff --git a/packages/doltlab/.gitbook/assets/getting-started/doltlab-aws-ec2-pub-ip.png b/packages/doltlab/content/.gitbook/assets/getting-started/doltlab-aws-ec2-pub-ip.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/getting-started/doltlab-aws-ec2-pub-ip.png
rename to packages/doltlab/content/.gitbook/assets/getting-started/doltlab-aws-ec2-pub-ip.png
diff --git a/packages/doltlab/.gitbook/assets/getting-started/doltlab-aws-ec2-security-rules.png b/packages/doltlab/content/.gitbook/assets/getting-started/doltlab-aws-ec2-security-rules.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/getting-started/doltlab-aws-ec2-security-rules.png
rename to packages/doltlab/content/.gitbook/assets/getting-started/doltlab-aws-ec2-security-rules.png
diff --git a/packages/doltlab/.gitbook/assets/getting-started/doltlab-aws-ec2-storage.png b/packages/doltlab/content/.gitbook/assets/getting-started/doltlab-aws-ec2-storage.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/getting-started/doltlab-aws-ec2-storage.png
rename to packages/doltlab/content/.gitbook/assets/getting-started/doltlab-aws-ec2-storage.png
diff --git a/packages/doltlab/.gitbook/assets/getting-started/doltlab-create-user-error.png b/packages/doltlab/content/.gitbook/assets/getting-started/doltlab-create-user-error.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/getting-started/doltlab-create-user-error.png
rename to packages/doltlab/content/.gitbook/assets/getting-started/doltlab-create-user-error.png
diff --git a/packages/doltlab/.gitbook/assets/getting-started/doltlab-push.png b/packages/doltlab/content/.gitbook/assets/getting-started/doltlab-push.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/getting-started/doltlab-push.png
rename to packages/doltlab/content/.gitbook/assets/getting-started/doltlab-push.png
diff --git a/packages/doltlab/.gitbook/assets/getting-started/fresh-doltlab.png b/packages/doltlab/content/.gitbook/assets/getting-started/fresh-doltlab.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/getting-started/fresh-doltlab.png
rename to packages/doltlab/content/.gitbook/assets/getting-started/fresh-doltlab.png
diff --git a/packages/doltlab/.gitbook/assets/gmail_app_password_no_worky.png b/packages/doltlab/content/.gitbook/assets/gmail_app_password_no_worky.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/gmail_app_password_no_worky.png
rename to packages/doltlab/content/.gitbook/assets/gmail_app_password_no_worky.png
diff --git a/packages/doltlab/.gitbook/assets/gmail_app_passwords_are_here.png b/packages/doltlab/content/.gitbook/assets/gmail_app_passwords_are_here.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/gmail_app_passwords_are_here.png
rename to packages/doltlab/content/.gitbook/assets/gmail_app_passwords_are_here.png
diff --git a/packages/doltlab/.gitbook/assets/gmail_search_app_passwords.png b/packages/doltlab/content/.gitbook/assets/gmail_search_app_passwords.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/gmail_search_app_passwords.png
rename to packages/doltlab/content/.gitbook/assets/gmail_search_app_passwords.png
diff --git a/packages/doltlab/.gitbook/assets/hosted_deployment_configuration.png b/packages/doltlab/content/.gitbook/assets/hosted_deployment_configuration.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/hosted_deployment_configuration.png
rename to packages/doltlab/content/.gitbook/assets/hosted_deployment_configuration.png
diff --git a/packages/doltlab/.gitbook/assets/hosted_deployment_started copy.png b/packages/doltlab/content/.gitbook/assets/hosted_deployment_started copy.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/hosted_deployment_started copy.png
rename to packages/doltlab/content/.gitbook/assets/hosted_deployment_started copy.png
diff --git a/packages/doltlab/.gitbook/assets/hosted_deployment_started.png b/packages/doltlab/content/.gitbook/assets/hosted_deployment_started.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/hosted_deployment_started.png
rename to packages/doltlab/content/.gitbook/assets/hosted_deployment_started.png
diff --git a/packages/doltlab/.gitbook/assets/hosted_dolt_workbench.png b/packages/doltlab/content/.gitbook/assets/hosted_dolt_workbench.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/hosted_dolt_workbench.png
rename to packages/doltlab/content/.gitbook/assets/hosted_dolt_workbench.png
diff --git a/packages/doltlab/.gitbook/assets/hosted_infra.jpg b/packages/doltlab/content/.gitbook/assets/hosted_infra.jpg
similarity index 100%
rename from packages/doltlab/.gitbook/assets/hosted_infra.jpg
rename to packages/doltlab/content/.gitbook/assets/hosted_infra.jpg
diff --git a/packages/doltlab/.gitbook/assets/ld-logo.png b/packages/doltlab/content/.gitbook/assets/ld-logo.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/ld-logo.png
rename to packages/doltlab/content/.gitbook/assets/ld-logo.png
diff --git a/packages/doltlab/.gitbook/assets/multihost_doltlab.svg b/packages/doltlab/content/.gitbook/assets/multihost_doltlab.svg
similarity index 100%
rename from packages/doltlab/.gitbook/assets/multihost_doltlab.svg
rename to packages/doltlab/content/.gitbook/assets/multihost_doltlab.svg
diff --git a/packages/doltlab/.gitbook/assets/oci_remote_backup_bucket.png b/packages/doltlab/content/.gitbook/assets/oci_remote_backup_bucket.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/oci_remote_backup_bucket.png
rename to packages/doltlab/content/.gitbook/assets/oci_remote_backup_bucket.png
diff --git a/packages/doltlab/.gitbook/assets/oci_remote_backup_bucket_example.png b/packages/doltlab/content/.gitbook/assets/oci_remote_backup_bucket_example.png
similarity index 100%
rename from packages/doltlab/.gitbook/assets/oci_remote_backup_bucket_example.png
rename to packages/doltlab/content/.gitbook/assets/oci_remote_backup_bucket_example.png
diff --git a/packages/doltlab/content/enterprise/getting-started.md b/packages/doltlab/content/enterprise/getting-started.md
index 6e00399c3..c236d4319 100644
--- a/packages/doltlab/content/enterprise/getting-started.md
+++ b/packages/doltlab/content/enterprise/getting-started.md
@@ -28,7 +28,7 @@ ubuntu@ip-10-2-0-24:~/doltlab$ ./start.sh
Hit your DoltLab to make sure it works:
-
+
You'll notice you have an Enterprise logo and the footer says "ENTERPRISE" in the version string. If you see those, your DoltLab Enterprise is working.
@@ -38,7 +38,7 @@ Most Enterprise features are enabled by [passing arguments to the installer](../
As some of you know, [DoltHub was initially Liquidata](https://www.dolthub.com/blog/2020-09-25-dolthub-rebrand/) and the logo was pretty sick.
-
+
I'm going to make a DoltLab Enterprise instance that is Liquidata branded. Oh what could have been?
@@ -61,6 +61,6 @@ ubuntu@ip-10-2-0-24:~/doltlab$ ./installer --host=54.191.163.60 --enterprise-onl
Then I start my instance and I get a new look and feel.
-
+
Again, most of the features are enabled using the installer, so get used to running that to change your running DoltLab.
diff --git a/packages/doltlab/content/guides/basic.md b/packages/doltlab/content/guides/basic.md
index ef8716f2a..5b7d2febe 100644
--- a/packages/doltlab/content/guides/basic.md
+++ b/packages/doltlab/content/guides/basic.md
@@ -467,15 +467,15 @@ To quickly get up and running with an existing SMTP server, we recommend using [
After 2-Step Verification is set up, at the bottom of the page click "App passwords".
-
+
If you do not see "App Passwords" at the bottom of this page, return to the Security page and in the search bar, search for "App Passwords".
-
+
Next, name your app password, then click "Generate." You will be provided a password you can use with your DoltLab instance.
-
+
This generated password can be supplied along with your Gmail email address, as the `username`, to send emails with `smtp_connection_helper` and DoltLab.
@@ -683,31 +683,31 @@ To begin, you'll need to create a Hosted Dolt deployment that your DoltLab insta
You will then see a form where you can specify details about the host you need for your DoltLab instance:
-
+
In the image above you can see that we defined our Hosted Dolt deployment name as `my-doltlab-db-1`, selected an AWS EC2 host with 2 CPU and 8 GB of RAM in region `us-west-2`. We've also requested 200 GB of disk. For DoltLab, these settings should be more than sufficient.
We have also requested a replica instance by checking the "Enable Replication" box, and specifying `1` replica, although replication is not required for DoltLab.
-
+
If you want the ability to [clone this Hosted Dolt instance](https://www.dolthub.com/blog/2023-04-17-cloning-a-hosted-database/), check the box "Enable Dolt Credentials". And finally, if you want to use the SQL workbench feature for this hosted instance (which we recommend) you should also check the box "Create database users for the SQL Workbench".
You will see the hourly cost of running the Hosted Dolt instance displayed above the "Create Deployment" button. Click it, and wait for the deployment to reach the "Started" state.
-
+
Once the deployment has come up, the deployment page will display the connection information for both the primary host and the replica, and each will be ready to use. Before connecting a DoltLab instance to the primary host, though, there are a few remaining steps to take to ensure the host has the proper state before connecting DoltLab.
First, click the "Configuration" tab and uncheck the box "behavior_disable_multistatements". DoltLab will need to execute multiple statements against this database when it starts up. You can also, optionally, change the log_level to "debug". This log level setting will make sure executed queries appear in the database logs, which is helpful for debugging.
-
+
Click "Save Changes".
Next, navigate to the "Workbench" tab and check the box "Enable Writes". This will allow you to execute writes against this instance from the SQL workbench. Click "Update".
-
+
Then, with writes enabled, on this same page, click "Create database" to create the database that DoltLab expects, called `dolthubapi`.
@@ -757,7 +757,7 @@ Alternatively, rerun the [installer](../reference/installer.md) with `--doltlabd
Start DoltLab using the `./start.sh` script generated by the [installer](../reference/installer.md). Once DoltLab is running successfully against `my-doltlab-db-1`, you can create a database on DoltLab, for example called `test-db`, and you will see live changes to the database reflected in the Hosted Dolt workbench:
-
+
# Serve DoltLab over HTTPS natively
@@ -840,35 +840,35 @@ Because the host is in a private subnet with no public IP though, only the NLB w
Next, in AWS, create [target groups](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-target-group.html) for each DoltLab port that the NLB will forward requests to. These ports are:
`80/443`, `100`, `4321`, and `50051`.
-
+
When creating the target groups, select `Instances` as the target type. Then, select `TCP` as the port protocol, followed by the port to use for the target group. In this example we will map all target group ports to their corresponding DoltLab port, ie `80:80`, `100:100`, `4321:4321` and `50051:50051`. Select the same VPC used by your DoltLab host as well.
-
+
During target group creation, in the `Health Checks` section, click `Advanced health check settings` and select `Override` to specify the port to perform health checks on. Here, enter `2001`, the health check port for DoltLab's Envoy proxy, `doltlabenvoy`. We will use this same port for _all_ target group health checks.
-
+
After clicking `Next`, you will register targets for your new target group. Here you should see your DoltLab host. Select it and specify the port the target group will forward to.
-
+
Click `Include as pending below`, then click `Create target group`.
Once you've created your target groups you can create the NLB.
-
+
Be sure to select the Network Load balancer as the other types of load balancers may require different configurations.
Then, create an NLB in the same VPC and subnet as your DoltLab host that uses `Scheme: Internet-facing` and `Ip address type: IPV4`.
-
+
Additionally, select the the same availability zone that your DoltLab host uses. You can use the `default` security group for your NLB, however the ingress rules for this group will need to be updated before inbound traffic will be able to reach your NLB.
-
+
In the Listeners section, add listeners for each target group you created, specifying the NLB port to use for each one. But again, in this example we will forward on the same port. Click `Create load balancer`.
@@ -876,7 +876,7 @@ It make take a few minutes for the NLB to become ready. After it does, check eac
Next, edit the inbound rules for the security group attached to the NLB you created so that it allows connections on the listening ports.
-
+
On the NLB page you should now see the DNS name of your NLB which can be used to connect to your DoltLab instance.
diff --git a/packages/doltlab/content/guides/enterprise.md b/packages/doltlab/content/guides/enterprise.md
index 1ebdb2b33..bd5d97689 100644
--- a/packages/doltlab/content/guides/enterprise.md
+++ b/packages/doltlab/content/guides/enterprise.md
@@ -99,7 +99,7 @@ enterprise:
Once I save my changes, rerun the installer (`./installer`), and restart (`./start.sh`), I
should see my new Starbucks logo.
-
+
# Customize automated emails
@@ -268,7 +268,7 @@ they are used for:
Here is a visual guide for where customizable colors are used on the database
page on DoltLab:
-
+
In order to configure these customized colors, you'll need the
[RGB](https://en.wikipedia.org/wiki/RGB_color_model) value of each color. Each color value
@@ -358,7 +358,7 @@ $ ./start.sh
And now DoltLab is Starbucks branded!
-
+
See other examples of utilizing colors to brand DoltLab for some well-known companies
[here](https://dolthub.awsdev.ld-corp.com/blog/2024-05-23-customizing-doltlab-colors/#other-examples).
@@ -396,13 +396,13 @@ DoltLab Enterprise supports SAML single-sign-on. To configure your DoltLab insta
For example, [Okta](https://www.okta.com/), a popular IP, provides an endpoint for downloading the metadata descriptor for a SAML application after you register an application on their platform.
-
+
During registration, Okta will ask you for the "Single Sign On Url" and an "Audience Restriction" for the application.
Use the domain/host IP address of your DoltLab instance followed by `/sso/callback` for the "Single Sign On Url", and use that same domain/host IP address followed by just "/sso" for the "Audience Restriction". Since this example will be for `https://doltlab.dolthub.com`, we'll use `https://doltlab.dolthub.com/sso/callback` and `https://doltlab.dolthub.com/sso` respectively.
-
+
Be sure to also set "Name ID Format" to "Persistent".
@@ -439,15 +439,15 @@ Alternatively, the [installer](../reference/installer.md) can be run with the fo
When SAML single-sign-on is configured, you will see the SAML option on the sign-in page:
-
+
Next, as user `admin`, login to your DoltLab instance and navigate to `Profile` > `Settings` > `SSO`.
-
+
On this tab you will see the following:
-
+
`Assertion Consumer Service Url` displays the url where Okta should send the SAML assertion.
@@ -475,11 +475,11 @@ Dolt can use an [AWS Remote](https://www.dolthub.com/blog/2021-07-19-remotes/) a
For our example, let's create an AWS S3 bucket called `test-doltlab-application-db-backups`.
-
+
Let's also create a Dynamo DB table in the same AWS region, and call it `test-doltlab-backup-application-db-manifest`. Notice its uses the required partition key (primary key) `db`.
-
+
The AWS remote url for our DoltLab instance which is determined by the template `aws://[dolt_dynamo_table:dolt_remotes_s3_storage]/backup_name`, will be `aws://[test-doltlab-backup-application-db-manifest:test-doltlab-application-db-backups]/my_doltlab_backup`.
@@ -579,9 +579,9 @@ For more configuration options, please consult the [AlertManager documentaion](h
Finally, start DoltLab using the `./start.sh` script. DoltLab will create the first backup when started, and by default, will create backups at midnight each night. You will see your backups stored in your S3 bucket, and the manifest stored in your DynamoDB table.
-
+
-
+
Your DoltLab's Dolt server is now automatically backing up to your AWS remote.
@@ -589,7 +589,7 @@ Your DoltLab's Dolt server is now automatically backing up to your AWS remote.
To backup DoltLab's Dolt server to a GCP remote, first create a bucket in GCP. This will be the only required resource needed.
-
+
Next, add GCP JSON credentials to your DoltLab host. You can find information about GCP credentials [here](https://cloud.google.com/sdk/gcloud/reference/auth/application-default/login).
@@ -628,13 +628,13 @@ Finally, edit the `./alertmanager/alertmanager.yaml` file generated by the [inst
Once you start your Enterprise instance with `./start.sh`, it will now automatically back up its application Dolt server to your GCP bucket.
-
+
## OCI Remote Backup
To backup DoltLab's Dolt server to an OCI remote, first create a bucket in OCI. This will be the only required resource needed.
-
+
Next, install the `oci` CLI tool on your DoltLab host, and run `oci setup config` to create a configuration file with credentials authorized to access your bucket. You can find information about creating an config file [here](https://docs.oracle.com/en-us/iaas/Content/API/SDKDocs/cliinstall.htm#configfile).
@@ -690,7 +690,7 @@ Finally, edit the `./alertmanager/alertmanager.yaml` file generated by the [inst
Once you start your Enterprise instance with `./start.sh`, it will now automatically back up its application Dolt server to your OCI bucket.
-
+
# Deploy DoltLab across multiple hosts
@@ -698,7 +698,7 @@ DoltLab's services can be deployed across multiple hosts which allow DoltLab's s
The following guide will walkthrough deploying a DoltLab instance whose set of services each run on separate host machines.
-
+
The diagram above depicts the multi-host architecture for DoltLab. Each independent service runs on a distinct host, and is served behind it's own reverse proxy. Both the service and the proxy run via Docker compose, and are easily configured using the [installer](../reference/installer.md). At the time of this writing, multi-host deployments are only available over `http`. For `https` support, please [file an issue in our issues repository](https://github.com/dolthub/doltlab-issues).
diff --git a/packages/doltlab/content/introduction/getting-started.md b/packages/doltlab/content/introduction/getting-started.md
index b7adffd4a..ff6f7fc1f 100644
--- a/packages/doltlab/content/introduction/getting-started.md
+++ b/packages/doltlab/content/introduction/getting-started.md
@@ -16,29 +16,29 @@ To get your DoltLab ready host on AWS:
2. Select a Ubuntu 22.04 amd64 t2.xlarge instance.
-
+
3. Create a new RSA key pair for your instance in `.pem` format.
-
+
This will create a `.pem` file and download it locally.
3. Edit network settings and from the "Auto-assign public IP" drop-down menu choose "Enable".
-
+
4. Add security group rules for ports 22 (SSH), 80 (HTTP), 443 (HTTPS), 100 (CUSTOM), 4321 (CUSTOM), 50051 (CUSTOM) that allow ingress from anywhere. Specifics [here](https://docs.doltlab.com/introduction/installation#networking-requirements). You also may need to create a new VPC and Subnet here. Just use the defaults.
-
+
5. Add 300GB gp3 disk.
-
+
6. Click "Launch instance".
-
+
After this you should get a public IP for your new host. Mine was `54.191.163.60`.
@@ -262,7 +262,7 @@ cc278092afcb55de755e9b05725b86bb122eddd128264ee17134418dc154f455
Now the moment of truth, I hit the IP over `http`, not `https`, http://54.191.163.60/. Bam!
-
+
# Login as Admin
@@ -270,7 +270,7 @@ Now, your DoltLab is running but it's not very useful. Only logged in users can
The DoltLab instance ships with a default user configured called `admin`. It has a password `DoltLab1234`. If you click the Sign In button in the top corner and log in as `admin`, you get a more useful set of features.
-
+
# Basic Configuration
@@ -278,7 +278,7 @@ The DoltLab instance ships with a default user configured called `admin`. It has
A configured email server is required to create new users. If you try to create a user, you'll get an error that looks like this:
-
+
So, you only have a single admin user to play with for now.
@@ -288,7 +288,7 @@ You can build whatever database you can imagine using the web user interface. Th
Here's a simple test database I created using SQL.
-
+
## Clone Databases
@@ -326,7 +326,7 @@ $ dolt creds ls
* ioohq4v4itlhgse9sv10acrknngmr6hukvm93n7k1qvo856oudug
```
-
+
Now you should be able to make a change and push to your DoltLab.
@@ -348,7 +348,7 @@ To http://54.191.163.60:50051/admin/test
And I can now see my change on DoltLab!
-
+
You're now ready to try out all the Dolt and DoltLab experiences like Pull Requests, Issues, the SQL Workbench, and Diffs. Get testing and see if DoltLab is right for you and your team.
diff --git a/packages/doltlab/content/introduction/what-is-doltlab.md b/packages/doltlab/content/introduction/what-is-doltlab.md
index 968a16164..322071f1f 100644
--- a/packages/doltlab/content/introduction/what-is-doltlab.md
+++ b/packages/doltlab/content/introduction/what-is-doltlab.md
@@ -4,7 +4,7 @@ title: What is DoltLab?
# What is DoltLab?
-
+
DoltLab gets its name from the combination of Dolt and [GitLab](https://about.gitlab.com/), because GitLab is the version of GitHub that you can host yourself and DoltLab is the version of [DoltHub](https://www.dolthub.com) that you can host yourself.
diff --git a/packages/doltlab/content/older/pre-installer-administrator-guide.md b/packages/doltlab/content/older/pre-installer-administrator-guide.md
index b457abbe0..a3a289ae0 100644
--- a/packages/doltlab/content/older/pre-installer-administrator-guide.md
+++ b/packages/doltlab/content/older/pre-installer-administrator-guide.md
@@ -187,7 +187,7 @@ SET session_replication_role = replica;
...
```
-[Start DoltLab's services](../installation/start-doltlab.md) again using the `start-doltlab.sh` script. After the script completes, `cd` into the directory containing the `postgres-dump.sql` file and run:
+[Start DoltLab's services](./installation/start-doltlab-pre-installer.md) again using the `start-doltlab.sh` script. After the script completes, `cd` into the directory containing the `postgres-dump.sql` file and run:
> For DoltLab `v0.7.0` and later, use `--network doltlab` below.
@@ -597,31 +597,31 @@ To begin, you'll need to create a Hosted Dolt deployment that your DoltLab insta
You will then see a form where you can specify details about the host you need for your DoltLab instance:
-
+
In the image above you can see that we defined our Hosted Dolt deployment name as `my-doltlab-db-1`, selected an AWS EC2 host with 2 CPU and 8 GB of RAM in region `us-west-2`. We've also requested 200 GB of disk. For DoltLab, these settings should be more than sufficient.
We have also requested a replica instance by checking the "Enable Replication" box, and specifying `1` replica, although replication is not required for DoltLab.
-
+
If you want the ability to [clone this Hosted Dolt instance](https://www.dolthub.com/blog/2023-04-17-cloning-a-hosted-database/), check the box "Enable Dolt Credentials". And finally, if you want to use the SQL workbench feature for this hosted instance (which we recommend) you should also check the box "Create database users for the SQL Workbench".
You will see the hourly cost of running the Hosted Dolt instance displayed above the "Create Deployment" button. Click it, and wait for the deployment to reach the "Started" state.
-
+
Once the deployment has come up, the deployment page will display the connection information for both the primary host and the replica, and each will be ready to use. Before connecting a DoltLab instance to the primary host, though, there are a few remaining steps to take to ensure the host has the proper state before connecting DoltLab.
First, click the "Configuration" tab and uncheck the box "behavior_disable_multistatements". DoltLab will need to execute multiple statements against this database when it starts up. You can also, optionally, change the log_level to "debug". This log level setting will make sure executed queries appear in the database logs, which is helpful for debugging.
-
+
Click "Save Changes".
Next, navigate to the "Workbench" tab and check the box "Enable Writes". This will allow you to execute writes against this instance from the SQL workbench. Click "Update".
-
+
Then, with writes enabled, on this same page, click "Create database" to create the database that DoltLab expects, called `dolthubapi`.
@@ -715,7 +715,7 @@ Make sure that the `DOLT_PASSWORD` environment variable matches the password you
Once DoltLab is running successfully against `my-doltlab-db-1`, you can create a database on DoltLab, for example called `test-db`, and you will see live changes to the database reflected in the Hosted Dolt workbench:
-
+
# Serve DoltLab over HTTPS with a TLS reverse proxy
@@ -1035,35 +1035,35 @@ Similarly, edit the `docker-compose.yaml` file to expose port `2001` in the `dol
Next, in AWS, create [target groups](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-target-group.html) for each DoltLab port that the NLB will forward requests to. These ports are:
`80/443`, `100`, `4321`, and `50051`.
-
+
When creating the target groups, select `Instances` as the target type. Then, select `TCP` as the port protocol, followed by the port to use for the target group. In this example we will map all target group ports to their corresponding DoltLab port, ie `80:80`, `100:100`, `4321:4321` and `50051:50051`. Select the same VPC used by your DoltLab host as well.
-
+
During target group creation, in the `Health Checks` section, click `Advanced health check settings` and select `Override` to specify the port to perform health checks on. Here, enter `2001`, the port we added to DoltLab's envoy configuration file. We will use this same port for _all_ target group health checks.
-
+
After clicking `Next`, you will register targets for your new target group. Here you should see your DoltLab host. Select it and specify the port the target group will forward to.
-
+
Click `Include as pending below`, then click `Create target group`.
Once you've created your target groups you can create the NLB.
-
+
Be sure to select the Network Load balancer as the other types of load balancers may require different configurations.
Then, create an NLB in the same VPC and subnet as your DoltLab host that uses `Scheme: Internet-facing` and `Ip address type: IPV4`.
-
+
Additionally, select the the same availability zone that your DoltLab host uses. You can use the `default` security group for your NLB, however the ingress rules for this group will need to be updated before inbound traffic will be able to reach your NLB.
-
+
In the Listeners section, add listeners for each target group you created, specifying the NLB port to use for each one. But again, in this example we will forward on the same port. Click `Create load balancer`.
@@ -1071,7 +1071,7 @@ It make take a few minutes for the NLB to become ready. After it does, check eac
Next, edit the inbound rules for the security group attached to the NLB you created so that it allows connections on the listening ports.
-
+
On the NLB page you should now see the DNS name of your NLB which can be used to connect to your DoltLab instance.