pg_dump
and restoring the database from the dump using psql
.remote-data.tar
in your working directory.user-uploaded-data.tar
in your working directory.prune
the Docker containers, and remove the old volume(s):start-doltlab.sh
script. After the script completes, cd
into the directory containing the remote-data.tar
backup file and run:cd
into the directory containing user-uploaded-data.tar
and run:pg_dump
. To do so, keep DoltLab's services up and run:PGPASSWORD
should be the POSTGRES_PASSWORD
set when DoltLab was first deployed.postgres-dump.sql
, first stop the running DoltLab services, remove the stopped containers, and remove the old postgres server volume:postgres-dump.sql
file by adding the line SET session_replication_role = replica;
near the top of the file:start-doltlab.sh
script. After the script completes, cd
into the directory containing the postgres-dump.sql
file and run:docker logs <container name>
command. For example, to view to logs of doltlabapi
service, run:docker inspect
command, then cp
the logs to your working directory:scp
. You can then send this and any other log files to the DoltLab team member you're working with via email.start-doltlab.sh
script from the newer DoltLab version. This script will simply create new Docker volumes with the appropriate schema for that DoltLab version.v0.3.0+
v0.3.0
support schema migrations without data loss. To upgrade to a DoltLab version after v0.3.0
, simply stop your old version of DoltLab, then download and unzip the newer DoltLab version to the same location as your previous version. This will ensure that when you start the new version of DoltLab using the start-doltlab.sh
script, the old DoltLab version's Docker volumes get attached to the new version's containers.v0.2.0
to v0.3.0
v0.1.0
v0.2.0
section.v0.1.0
to v0.2.0
Without Data Lossv0.1.0
to v0.2.0
, leave DoltLab v0.1.0
's services running and connect a PostgreSQL client from inside the doltlab_doltlab
Docker network to the running doltlab_doltlabdb_1
server. On the DoltLab host machine, run:PGPASSWORD
should be the POSTGRES_PASSWORD
set when DoltLab v0.1.0
was first deployed. You should now see the SQL dump file called doltlab-v0.1.0-dump-data-only.sql
.doltlab-v0.1.0-dump-data-only.sql
file by adding the line SET session_replication_role = replica;
near the top of the file:v0.1.0
services and delete the Docker caches and stopped containers on the host by running:v0.1.0
's doltlab_doltlabdb_1
postgres server by running:v0.2.0
, unzip it's contents, and start DoltLab v0.2.0
's services by running the start-doltlab.sh
script.v0.2.0
's services are running with docker ps
:doltlab_doltlab
Docker network to the running doltlab_doltlabdb_1
server to perform the data dump import. Then, update the has_dolt
column in the users
table.v0.2.0
with your postgres data from DoltLab v0.1.0
.#doltlab
server.--auth-endpoint
, --login-url
, and --insecure
arguments to point your Dolt client at the DoltLab instance you want to authenticate against.--auth-endpoint
should point at the DoltLab RemoteAPI Server running on port 50051
. --login-url
should point at the DoltLab instance's credentials page. --insecure
a boolean flag, should be used since DoltLab does not currently support TLS gRPC
connections.--login-url
with credentials populated in the "Public Key" field. Simply add a "Description" and click "Create", then return to your terminal to see your Dolt client successfully authenticated.v0.39.0
, or to authenticate without using the dolt login
command, first run the dolt creds new command, which will output a new public key:v0.3.0
, Prometheus gRPC service metrics for DoltLab's Remote API Server, doltlabremoteapi
, and DoltLab's Main API server, doltlabapi
, are published on port 7770
.:7770/doltlabremoteapi
, and for DoltLab's Main API that's :7770/doltlabapi
.doltlabremoteapi
service metrics for our DoltLab demo instance here, http://doltlab.dolthub.com:7770/doltlabremoteapi and you can view the doltlabapi
service metrics here http://doltlab.dolthub.com:7770/doltlabapi.7770
on your DoltLab host.cAdvisor
, open port 8080
on your DoltLab host as well. cAdvisor
will display DoltLab's running containers via a web UI on :8080/docker
and will publish Prometheus metrics for DoltLab's container at :8080/metrics
by default.cAdvisor
as a Docker container in daemon mode with:9090
on the DoltLab host. Then, write the following prometheus.yml
file on the host:--add-host host.docker.internal:host-gateway
is only required if running the Prometheus server on the DoltLab host. If running it elsewhere, this argument may be omitted, and the host.docker.internal
hostname in prometheus.yml
can be changed to the hostname of your DoltLab host.v0.4.2
, connections to existing SMTP servers using implicit TLS (on port 465
, for example) are supported. To connect using implicit TLS, edit the docker-compose.yaml
included in the DoltLab zip. Under the doltlabapi
section, in the command
block, add the following argument:-emailInsecureTLS
.v0.4.1
, the default user admin
is created when DoltLab starts up, which allows admins to sign in to their DoltLab instance even if they are experiencing SMTP server connection issues.v0.4.2
, this tool is now included as an executable binary in DoltLab's zip, called smtp_connection_helper
../smtp_connection_helper --help
which will output:plain
authentication, run:plain
authentication with implicit TLS, run:docker-compose.yaml
file included in DoltLab's zip.doltlabapi
section, in the command
block, remove the argument -dolthubWhitelistAllowAll
. Restart your DoltLab instance for this to take effect.email_whitelist_elements
before permitting account creation. Only user's with email addresses present in this table will be able to create accounts on your DoltLab instance.email_whitelist_elements
table.v0.4.2
, a script to easily connect to your DoltLab instance's running PostgreSQL server is included in the zip, called shell-db.sh
.POSTGRES_PASSWORD
you used to start your DoltLab instance, as PGPASSWORD
here. Run:dolthubapi=#
PostgresSQL prompt connected to your DoltLab instance.INSERT
to allow a specific user with [email protected]
to create an account on your DolLab instance: