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
# Example modified from https://docs.github.com/en/actions/publishing-packages/publishing-docker-images
3
+
name: Create and publish a Docker image
4
+
5
+
# Configures this workflow to run every time a change is pushed to selected tags and branches
6
+
on:
7
+
pull_request:
8
+
branches:
9
+
- main
10
+
push:
11
+
branches:
12
+
- main
13
+
tags:
14
+
- v**
15
+
16
+
# Defines two custom environment variables for the workflow. These are used for the Container registry domain, and a name for the Docker image that this workflow builds.
17
+
env:
18
+
REGISTRY: ghcr.io
19
+
IMAGE_NAME: ${{ github.repository }}
20
+
21
+
# There is a single job in this workflow. It's configured to run on the latest available version of Ubuntu.
22
+
jobs:
23
+
build-and-push-image:
24
+
runs-on: ubuntu-latest
25
+
# Sets the permissions granted to the `GITHUB_TOKEN` for the actions in this job.
26
+
permissions:
27
+
contents: read
28
+
packages: write
29
+
steps:
30
+
- name: Checkout repository
31
+
uses: actions/checkout@v4
32
+
# Uses the `docker/login-action` action to log in to the Container registry registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here.
33
+
- name: Log in to the Container registry
34
+
uses: docker/login-action@v3
35
+
with:
36
+
registry: ${{ env.REGISTRY }}
37
+
username: ${{ github.actor }}
38
+
password: ${{ secrets.PAT_TOKEN }}
39
+
# This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The `id` "meta" allows the output of this step to be referenced in a subsequent step. The `images` value provides the base name for the tags and labels.
40
+
- name: Extract metadata (tags, labels) for Docker
41
+
id: meta
42
+
uses: docker/metadata-action@v5
43
+
with:
44
+
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
45
+
# This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
46
+
# It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository.
47
+
# It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
Copy file name to clipboardExpand all lines: README.md
+4-2
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,10 @@
1
1
## DuckDB (via MotherDuck) Connector
2
2
3
-
The DuckDB Data Connector allows for connecting to a Motherduck hosted DuckDB database. This uses the [Typescript Data Connector SDK](https://github.com/hasura/ndc-sdk-typescript) and implements the [Data Connector Spec](https://github.com/hasura/ndc-spec).
3
+
## TODO: Fix README
4
4
5
-
In order to use this connector you will need Motherduck setup. This connector currently only supports querying.
5
+
The DuckDB Data Connector allows for connecting to a Motherduck hosted DuckDB database, or a local DuckDB database file. This uses the [Typescript Data Connector SDK](https://github.com/hasura/ndc-sdk-typescript) and implements the [Data Connector Spec](https://github.com/hasura/ndc-spec).
0 commit comments