From 2e37ddef8eeebbfbe668f28bf9cf1ae3774412c4 Mon Sep 17 00:00:00 2001 From: commit111 Date: Tue, 26 Nov 2024 12:47:33 -0800 Subject: [PATCH 1/7] huginn changes only --- samples/huginn/README.md | 71 +++++++++++++++++++++++++++++++------ samples/huginn/compose.yaml | 24 +++++++++---- 2 files changed, 79 insertions(+), 16 deletions(-) diff --git a/samples/huginn/README.md b/samples/huginn/README.md index 803c2396..17ee8340 100644 --- a/samples/huginn/README.md +++ b/samples/huginn/README.md @@ -2,26 +2,77 @@ [![1-click-deploy](https://defang.io/deploy-with-defang.png)](https://portal.defang.dev/redirect?url=https%3A%2F%2Fgithub.com%2Fnew%3Ftemplate_name%3Dsample-huginn-template%26template_owner%3DDefangSamples) +This sample shows how to deploy Huginn with Defang. + Huginn is a system for building agents that perform automated tasks for you online. Huginn's Agents can monitor the web, respond to events, and act on your behalf. They propagate events along a directed graph. It's like a customizable IFTTT or Zapier on your own server, ensuring data privacy. ## Prerequisites 1. Download [Defang CLI](https://github.com/DefangLabs/defang) -2. Have a managed database service configured and have the connection details ready. Neon postgres is a good free option. -3. (optional) If you are using [Defang BYOC](https://docs.defang.io/docs/concepts/defang-byoc), make sure you have properly [authenticated your AWS account](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html). +2. Have a managed database service configured and ready, such as [Neon PostgreSQL](https://neon.tech/) +3. (Optional) If you are using [Defang BYOC](https://docs.defang.io/docs/concepts/defang-byoc) authenticate with your cloud provider account +4. (Optional for local development) [Docker CLI](https://docs.docker.com/engine/install/) + +## Development + +To run the application locally, you can use the following command: + +```bash +docker compose -f ./compose.yaml -f ./compose.dev.yaml up +``` +This will start the Postgres container and the Huginn container. Huginn will be available at `http://localhost:3000` with the username `admin` and password `password`. + +## Configuration + +For this sample, you will need to provide the following [configuration](https://docs.defang.io/docs/concepts/configuration): + +> Note that if you are using the 1-click deploy option, you can set these values as secrets in your GitHub repository and the action will automatically deploy them for you. + +### `DATABASE_NAME` +The name of the database. +```bash +defang config set DATABASE_NAME +``` + +### `DATABASE_USERNAME` +The username used with the database. +```bash +defang config set DATABASE_USERNAME +``` + +### `DATABASE_PASSWORD` +The password used with the database. +```bash +defang config set DATABASE_PASSWORD +``` + +### `DATABASE_HOST` +The host of the database. +```bash +defang config set DATABASE_HOST +``` + +## Deployment + +> [!NOTE] +> Download [Defang CLI](https://github.com/DefangLabs/defang) -## Local +### Defang Playground -For development, we use a Postgres container. The Postgres container is defined in the `compose.dev.yaml` file. The Huginn container is defined in the `compose.yaml` file, with some overrides in the `compose.dev.yaml` file so it can correctly connect to the local database container. +Deploy your application to the Defang Playground by opening up your terminal and typing: +```bash +defang compose up +``` -To start the local environment, run `docker compose -f ./compose.yaml -f ./compose.dev.yaml up`. This will start the Postgres container and the Huginn container. Huginn will be available at `http://localhost:3000` with the username `admin` and password `password`. +### BYOC (AWS) -## Deploying +If you want to deploy to your own cloud account, you can use Defang BYOC: -1. Open the terminal and type `defang login` -2. Add your database connection details using `defang config` by typing `defang config set ` where `` is the each of the following `DATABASE_NAME`, `DATABASE_USERNAME`, `DATABASE_PASSWORD`, `DATABASE_HOST`. For example `defang config set DATABASE_NAME` and pasting your database name. -3. Type `defang compose up` in the CLI. -4. Your app will be running within a few minutes. +1. [Authenticate your AWS account](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html), and check that you have properly set your environment variables like `AWS_PROFILE`, `AWS_REGION`, `AWS_ACCESS_KEY_ID`, and `AWS_SECRET_ACCESS_KEY`. +2. Run in a terminal that has access to your AWS environment variables: + ```bash + defang --provider=aws compose up + ``` --- diff --git a/samples/huginn/compose.yaml b/samples/huginn/compose.yaml index f9287476..1b9f35bb 100644 --- a/samples/huginn/compose.yaml +++ b/samples/huginn/compose.yaml @@ -1,5 +1,5 @@ services: - huginn: + huginn-app: image: ghcr.io/huginn/huginn restart: unless-stopped ports: @@ -10,7 +10,7 @@ services: resources: reservations: cpus: '1.0' - memory: '2G' + memory: 1G healthcheck: test: ["CMD", "curl", "-f", "http://localhost:3000/"] interval: 1m30s @@ -18,7 +18,19 @@ services: retries: 10 environment: - DATABASE_ADAPTER=postgresql - - DATABASE_NAME - - DATABASE_USERNAME - - DATABASE_PASSWORD - - DATABASE_HOST + - DATABASE_NAME=huginn + - DATABASE_USERNAME=huginn + - DATABASE_PASSWORD=${POSTGRES_PASSWORD} + - DATABASE_HOST=postgresx + postgresx: + image: postgres:14 + environment: + - POSTGRES_USER=huginn + - POSTGRES_PASSWORD + - POSTGRES_DB=huginn + ports: + - mode: host + target: 5432 + published: 5432 + networks: + - public From 4484648a5c8edf3e80395e154f193f438cd7445b Mon Sep 17 00:00:00 2001 From: commit111 Date: Tue, 26 Nov 2024 12:59:19 -0800 Subject: [PATCH 2/7] Revert "huginn changes only" This reverts commit 2e37ddef8eeebbfbe668f28bf9cf1ae3774412c4. accidental commit --- samples/huginn/README.md | 71 ++++++------------------------------- samples/huginn/compose.yaml | 24 ++++--------- 2 files changed, 16 insertions(+), 79 deletions(-) diff --git a/samples/huginn/README.md b/samples/huginn/README.md index 17ee8340..803c2396 100644 --- a/samples/huginn/README.md +++ b/samples/huginn/README.md @@ -2,77 +2,26 @@ [![1-click-deploy](https://defang.io/deploy-with-defang.png)](https://portal.defang.dev/redirect?url=https%3A%2F%2Fgithub.com%2Fnew%3Ftemplate_name%3Dsample-huginn-template%26template_owner%3DDefangSamples) -This sample shows how to deploy Huginn with Defang. - Huginn is a system for building agents that perform automated tasks for you online. Huginn's Agents can monitor the web, respond to events, and act on your behalf. They propagate events along a directed graph. It's like a customizable IFTTT or Zapier on your own server, ensuring data privacy. ## Prerequisites 1. Download [Defang CLI](https://github.com/DefangLabs/defang) -2. Have a managed database service configured and ready, such as [Neon PostgreSQL](https://neon.tech/) -3. (Optional) If you are using [Defang BYOC](https://docs.defang.io/docs/concepts/defang-byoc) authenticate with your cloud provider account -4. (Optional for local development) [Docker CLI](https://docs.docker.com/engine/install/) - -## Development - -To run the application locally, you can use the following command: - -```bash -docker compose -f ./compose.yaml -f ./compose.dev.yaml up -``` -This will start the Postgres container and the Huginn container. Huginn will be available at `http://localhost:3000` with the username `admin` and password `password`. - -## Configuration - -For this sample, you will need to provide the following [configuration](https://docs.defang.io/docs/concepts/configuration): - -> Note that if you are using the 1-click deploy option, you can set these values as secrets in your GitHub repository and the action will automatically deploy them for you. - -### `DATABASE_NAME` -The name of the database. -```bash -defang config set DATABASE_NAME -``` - -### `DATABASE_USERNAME` -The username used with the database. -```bash -defang config set DATABASE_USERNAME -``` - -### `DATABASE_PASSWORD` -The password used with the database. -```bash -defang config set DATABASE_PASSWORD -``` - -### `DATABASE_HOST` -The host of the database. -```bash -defang config set DATABASE_HOST -``` - -## Deployment - -> [!NOTE] -> Download [Defang CLI](https://github.com/DefangLabs/defang) +2. Have a managed database service configured and have the connection details ready. Neon postgres is a good free option. +3. (optional) If you are using [Defang BYOC](https://docs.defang.io/docs/concepts/defang-byoc), make sure you have properly [authenticated your AWS account](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html). -### Defang Playground +## Local -Deploy your application to the Defang Playground by opening up your terminal and typing: -```bash -defang compose up -``` +For development, we use a Postgres container. The Postgres container is defined in the `compose.dev.yaml` file. The Huginn container is defined in the `compose.yaml` file, with some overrides in the `compose.dev.yaml` file so it can correctly connect to the local database container. -### BYOC (AWS) +To start the local environment, run `docker compose -f ./compose.yaml -f ./compose.dev.yaml up`. This will start the Postgres container and the Huginn container. Huginn will be available at `http://localhost:3000` with the username `admin` and password `password`. -If you want to deploy to your own cloud account, you can use Defang BYOC: +## Deploying -1. [Authenticate your AWS account](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html), and check that you have properly set your environment variables like `AWS_PROFILE`, `AWS_REGION`, `AWS_ACCESS_KEY_ID`, and `AWS_SECRET_ACCESS_KEY`. -2. Run in a terminal that has access to your AWS environment variables: - ```bash - defang --provider=aws compose up - ``` +1. Open the terminal and type `defang login` +2. Add your database connection details using `defang config` by typing `defang config set ` where `` is the each of the following `DATABASE_NAME`, `DATABASE_USERNAME`, `DATABASE_PASSWORD`, `DATABASE_HOST`. For example `defang config set DATABASE_NAME` and pasting your database name. +3. Type `defang compose up` in the CLI. +4. Your app will be running within a few minutes. --- diff --git a/samples/huginn/compose.yaml b/samples/huginn/compose.yaml index 1b9f35bb..f9287476 100644 --- a/samples/huginn/compose.yaml +++ b/samples/huginn/compose.yaml @@ -1,5 +1,5 @@ services: - huginn-app: + huginn: image: ghcr.io/huginn/huginn restart: unless-stopped ports: @@ -10,7 +10,7 @@ services: resources: reservations: cpus: '1.0' - memory: 1G + memory: '2G' healthcheck: test: ["CMD", "curl", "-f", "http://localhost:3000/"] interval: 1m30s @@ -18,19 +18,7 @@ services: retries: 10 environment: - DATABASE_ADAPTER=postgresql - - DATABASE_NAME=huginn - - DATABASE_USERNAME=huginn - - DATABASE_PASSWORD=${POSTGRES_PASSWORD} - - DATABASE_HOST=postgresx - postgresx: - image: postgres:14 - environment: - - POSTGRES_USER=huginn - - POSTGRES_PASSWORD - - POSTGRES_DB=huginn - ports: - - mode: host - target: 5432 - published: 5432 - networks: - - public + - DATABASE_NAME + - DATABASE_USERNAME + - DATABASE_PASSWORD + - DATABASE_HOST From 9b9b88189b37c4fa3c70b61b5fe7ba6ba735a59d Mon Sep 17 00:00:00 2001 From: commit111 Date: Tue, 26 Nov 2024 12:47:42 -0800 Subject: [PATCH 3/7] hasura changes only --- samples/hasura/README.md | 70 +++++++++++++++++++++++++-------- samples/hasura/compose.dev.yaml | 2 +- samples/hasura/compose.yaml | 20 +++++++--- 3 files changed, 70 insertions(+), 22 deletions(-) diff --git a/samples/hasura/README.md b/samples/hasura/README.md index e161cd2e..52d49415 100644 --- a/samples/hasura/README.md +++ b/samples/hasura/README.md @@ -2,34 +2,72 @@ [![1-click-deploy](https://defang.io/deploy-with-defang.png)](https://portal.defang.dev/redirect?url=https%3A%2F%2Fgithub.com%2Fnew%3Ftemplate_name%3Dsample-hasura-template%26template_owner%3DDefangSamples) -This sample project demonstrates how to deploy Hasura with Defang and connect it to a Postgres database. We also demonstrate how to run a Postgres container during development and how to switch over to a managed postgres service like RDS, Neon, or others in production. If you want to get a compatible database ready to go really quickly for free, [Neon](https://neon.tech/) is a quick and easy way to go. The sample populates the database with some sample data so you can quickly start playing with the Hasura console. It sets wide open permissions on the tables as well so you can start querying or mutating the data right away. +This sample project demonstrates how to deploy Hasura with Defang and connect it to a Postgres database. + +The sample populates the database with some sample data so you can quickly start playing with the Hasura console. It sets wide open permissions on the tables as well so you can start querying or mutating the data right away. ## Prerequisites 1. Download [Defang CLI](https://github.com/DefangLabs/defang) -2. Have a managed database service configured and have the connection string ready. -3. (Optional) If you are using [Defang BYOC](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html) authenticated with your AWS account -4. (Optional - for local development) [Docker CLI](https://docs.docker.com/engine/install/) -5. (Optional) [Install the Hasura CLI](https://hasura.io/docs/latest/hasura-cli/install-hasura-cli/) to create migrations and update metadata for your Hasura GraphQL api. +2. Have a managed database service configured and ready, such as [Neon PostgreSQL](https://neon.tech/) +3. (Optional) If you are using [Defang BYOC](https://docs.defang.io/docs/concepts/defang-byoc) authenticate with your cloud provider account +4. (Optional for local development) [Docker CLI](https://docs.docker.com/engine/install/) +5. (Optional) Install the [Hasura CLI](https://hasura.io/docs/latest/hasura-cli/install-hasura-cli/) to create migrations and update metadata for your Hasura GraphQL API ## Development -For development, we use a Postgres container. The Postgres container is defined in the `compose.dev.yaml` file. The Hasura container is defined in the `compose.yaml` file, with some overrides in the `compose.dev.yaml` file so it can correctly connect to the development database container. + To run the application locally, you can use the following command: + +```bash +docker compose -f ./compose.yaml -f ./compose.dev.yaml up --build +``` +This will start the Postgres container (from `compose.dev.yaml`) and the Hasura container (from `compose.yaml` with some overrides). The Hasura console will be available at `http://localhost:8080` with the password `password`. + +> Note: If you want to make changes to your database, permissions, etc. see [Editing Hasura Settings](#editing-hasura-settings). + +### Editing Hasura Settings + +To edit the database, permissions, or any other Hasura settings such that you can deploy them to production, you should install the [ Hasura CLI](https://hasura.io/docs/latest/hasura-cli/install-hasura-cli/). Then, after starting the development environment, you can run `hasura console` _inside the `./hasura` directory_. This will open the Hasura console in your browser. Any changes you make in the console will be saved to the `migrations` and `metadata` directories. When you run `defang compose up`, these changes will be applied to the production environment. + +## Configuration + +For this sample, you will need to provide the following [configuration](https://docs.defang.io/docs/concepts/configuration): + +> Note that if you are using the 1-click deploy option, you can set these values as secrets in your GitHub repository and the action will automatically deploy them for you. + +### `HASURA_GRAPHQL_DATABASE_URL` +A connection string of the format `postgres://username:password@host:port/dbname`. +```bash +defang config set HASURA_GRAPHQL_DATABASE_URL +``` + +### `HASURA_GRAPHQL_ADMIN_SECRET` +A password you would like to log into Hasura with. +```bash +defang config set HASURA_GRAPHQL_ADMIN_SECRET +``` + +## Deployment + +> [!NOTE] +> Download [Defang CLI](https://github.com/DefangLabs/defang) -To start the development environment, run `docker compose -f ./compose.yaml -f ./compose.dev.yaml up`. This will start the Postgres container and the Hasura container. The Hasura console will be available at `http://localhost:8080` with the password `password`. -**Note:** _If you want to make changes to your database, permissions, etc. you should use the Hasura console and the Hasura CLI to make those changes. See the next section for more information._ +### Defang Playground -### Editing the database/permissions etc. +Deploy your application to the Defang Playground by opening up your terminal and typing: +```bash +defang compose up +``` -If you want to edit the database, permissions, or any other Hasura settings such that you can deploy them to production, you should [install the Hasura CLI](https://hasura.io/docs/latest/hasura-cli/install-hasura-cli/). Then, after starting the development environment, you can run `hasura console` _inside the `./hasura` directory_. This will open the Hasura console in your browser. Any changes you make in the console will be saved to the `migrations` and `metadata` directories. When you run `defang compose up` these changes will be applied to the production environment. +### BYOC (AWS) -## Deploying +If you want to deploy to your own cloud account, you can use Defang BYOC: -1. Open the terminal and type `defang login` -2. Add your connection string as a defang config value by typing `defang config set HASURA_GRAPHQL_DATABASE_URL` and pasting your connection string (which should be in the format `postgres://username:password@host:port/dbname`) -3. Setup a password for hasura by typing `defang config set HASURA_GRAPHQL_ADMIN_SECRET` and adding a password you would like to login with. -4. Type `defang compose up` in the CLI. -5. Your app will be running within a few minutes. +1. [Authenticate your AWS account](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html), and check that you have properly set your environment variables like `AWS_PROFILE`, `AWS_REGION`, `AWS_ACCESS_KEY_ID`, and `AWS_SECRET_ACCESS_KEY`. +2. Run in a terminal that has access to your AWS environment variables: + ```bash + defang --provider=aws compose up + ``` --- diff --git a/samples/hasura/compose.dev.yaml b/samples/hasura/compose.dev.yaml index c5dba8a8..c64ca0d5 100644 --- a/samples/hasura/compose.dev.yaml +++ b/samples/hasura/compose.dev.yaml @@ -1,6 +1,6 @@ services: postgres: - image: postgres:16 + image: postgres:14 environment: - POSTGRES_USER=postgres - POSTGRES_PASSWORD=postgres diff --git a/samples/hasura/compose.yaml b/samples/hasura/compose.yaml index e7e7329a..fb8876e9 100644 --- a/samples/hasura/compose.yaml +++ b/samples/hasura/compose.yaml @@ -11,7 +11,7 @@ services: published: 8080 mode: ingress environment: - - HASURA_GRAPHQL_DATABASE_URL + - HASURA_GRAPHQL_DATABASE_URL=postgres://postgres:${POSTGRES_PASSWORD}@db:5432/postgres - HASURA_GRAPHQL_ADMIN_SECRET - HASURA_GRAPHQL_ENABLE_CONSOLE=true - HASURA_GRAPHQL_UNAUTHORIZED_ROLE=public @@ -19,7 +19,17 @@ services: - HASURA_GRAPHQL_DEFAULT_NAMING_CONVENTION=graphql-default - HASURA_GRAPHQL_MIGRATIONS_DIR=/hasura/migrations - HASURA_GRAPHQL_METADATA_DIR=/hasura/metadata - #deploy: - # resources: - # reservations: - # memory: 256M + deploy: + resources: + reservations: + memory: 256M + db: + image: postgres:14 + restart: unless-stopped + environment: + - POSTGRES_USER=postgres + - POSTGRES_PASSWORD + - POSTGRES_DB=postgres + ports: + - mode: host + target: 5432 \ No newline at end of file From ec36945dd85ccc4f4a287220470535fd0d56d17b Mon Sep 17 00:00:00 2001 From: Linda Lee Date: Thu, 5 Dec 2024 10:25:40 -0800 Subject: [PATCH 4/7] Update samples/hasura/compose.dev.yaml Co-authored-by: Jordan Stephens --- samples/hasura/compose.dev.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/samples/hasura/compose.dev.yaml b/samples/hasura/compose.dev.yaml index c64ca0d5..0f49c9f5 100644 --- a/samples/hasura/compose.dev.yaml +++ b/samples/hasura/compose.dev.yaml @@ -1,6 +1,8 @@ services: postgres: - image: postgres:14 + extends: + file: compose.yaml + service: postgres environment: - POSTGRES_USER=postgres - POSTGRES_PASSWORD=postgres From 4692853626f807073c4fba8168e4bf9ca269a13b Mon Sep 17 00:00:00 2001 From: Raphael Titsworth-Morin Date: Mon, 29 Sep 2025 12:40:03 +0200 Subject: [PATCH 5/7] feat: add database dependency to Hasura service in compose config --- samples/hasura/compose.yaml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/samples/hasura/compose.yaml b/samples/hasura/compose.yaml index 83e20246..fcd3d4d6 100644 --- a/samples/hasura/compose.yaml +++ b/samples/hasura/compose.yaml @@ -10,6 +10,9 @@ services: - target: 8080 published: 8080 mode: ingress + depends_on: + database: + condition: service_started environment: - HASURA_GRAPHQL_ADMIN_SECRET - HASURA_GRAPHQL_DATABASE_URL=postgres://postgres:${POSTGRES_PASSWORD}@database:5432/postgres From 1381d41beca1ee216ebbb053e870a7cee8ad3110 Mon Sep 17 00:00:00 2001 From: Raphael Titsworth-Morin Date: Wed, 1 Oct 2025 21:27:10 +0200 Subject: [PATCH 6/7] rm user name and db, assume defaults --- samples/hasura/README.md | 8 +++++++- samples/hasura/compose.yaml | 5 ++--- samples/hasura/hasura/.dockerignore | 27 +++++++++++++++++++++++++++ 3 files changed, 36 insertions(+), 4 deletions(-) create mode 100644 samples/hasura/hasura/.dockerignore diff --git a/samples/hasura/README.md b/samples/hasura/README.md index 16623059..16d50179 100644 --- a/samples/hasura/README.md +++ b/samples/hasura/README.md @@ -41,7 +41,13 @@ A password for your database. defang config set POSTGRES_PASSWORD ``` -### `HASURA_GRAPHQL_ADMIN_SECRET` +### `SSL_MODE` +Either `disable` if you're using the Defang Playground or `require` if you're using BYOC. +```bash +defang config set SSL_MODE +``` + +### `HASURA_GRAPHQL_ADMIN_SECRET` A password you would like to log into Hasura with. ```bash defang config set HASURA_GRAPHQL_ADMIN_SECRET diff --git a/samples/hasura/compose.yaml b/samples/hasura/compose.yaml index fcd3d4d6..74b516b3 100644 --- a/samples/hasura/compose.yaml +++ b/samples/hasura/compose.yaml @@ -15,13 +15,14 @@ services: condition: service_started environment: - HASURA_GRAPHQL_ADMIN_SECRET - - HASURA_GRAPHQL_DATABASE_URL=postgres://postgres:${POSTGRES_PASSWORD}@database:5432/postgres + - HASURA_GRAPHQL_DATABASE_URL=postgres://postgres:${POSTGRES_PASSWORD}@database:5432/postgres?sslmode=${SSL_MODE} - HASURA_GRAPHQL_ENABLE_CONSOLE=true - HASURA_GRAPHQL_UNAUTHORIZED_ROLE=public - HASURA_GRAPHQL_EXPERIMENTAL_FEATURES=naming_convention - HASURA_GRAPHQL_DEFAULT_NAMING_CONVENTION=graphql-default - HASURA_GRAPHQL_MIGRATIONS_DIR=/hasura/migrations - HASURA_GRAPHQL_METADATA_DIR=/hasura/metadata + - SSL_MODE database: image: postgres:16 @@ -30,6 +31,4 @@ services: - target: 5432 mode: host environment: - - POSTGRES_USER=postgres - - POSTGRES_DB=postgres - POSTGRES_PASSWORD diff --git a/samples/hasura/hasura/.dockerignore b/samples/hasura/hasura/.dockerignore new file mode 100644 index 00000000..74a7bf9e --- /dev/null +++ b/samples/hasura/hasura/.dockerignore @@ -0,0 +1,27 @@ +# Default .dockerignore file for Defang +**/__pycache__ +**/.direnv +**/.DS_Store +**/.envrc +**/.git +**/.github +**/.idea +**/.next +**/.vscode +**/compose.*.yaml +**/compose.*.yml +**/compose.yaml +**/compose.yml +**/docker-compose.*.yaml +**/docker-compose.*.yml +**/docker-compose.yaml +**/docker-compose.yml +**/node_modules +**/Thumbs.db +Dockerfile +*.Dockerfile +# Ignore our own binary, but only in the root to avoid ignoring subfolders +defang +defang.exe +# Ignore our project-level state +.defang \ No newline at end of file From 0ac6c74aca031ad4a9f880755cf249894155f25e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rapha=C3=ABl=20Titsworth-Morin?= Date: Tue, 16 Dec 2025 15:02:11 -0400 Subject: [PATCH 7/7] Update samples/hasura/README.md --- samples/hasura/README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/samples/hasura/README.md b/samples/hasura/README.md index 16d50179..a294af1f 100644 --- a/samples/hasura/README.md +++ b/samples/hasura/README.md @@ -9,10 +9,9 @@ The sample populates the database with some sample data so you can quickly start ## Prerequisites 1. Download [Defang CLI](https://github.com/DefangLabs/defang) -2. Have a managed database service configured and ready, such as [Neon PostgreSQL](https://neon.tech/) -3. (Optional) If you are using [Defang BYOC](https://docs.defang.io/docs/concepts/defang-byoc) authenticate with your cloud provider account -4. (Optional for local development) [Docker CLI](https://docs.docker.com/engine/install/) -5. (Optional) Install the [Hasura CLI](https://hasura.io/docs/latest/hasura-cli/install-hasura-cli/) to create migrations and update metadata for your Hasura GraphQL API +2. (Optional) If you are using [Defang BYOC](https://docs.defang.io/docs/concepts/defang-byoc) authenticate with your cloud provider account +3. (Optional for local development) [Docker CLI](https://docs.docker.com/engine/install/) +Comment view5. (Optional) Install the [Hasura CLI](https://hasura.io/docs/latest/hasura-cli/install-hasura-cli/) to create migrations and update metadata for your Hasura GraphQL API ## Development