add buildx module

[buildx] update README

.github/workflows/buildx.yml

@@ -0,0 +1,35 @@
+name: ci
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - .github/workflows/buildx.yml
+      - "buildx/**"
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - name: Setup Fluent CI
+        uses: fluentci-io/setup-fluentci@v4
+      - name: Run Dagger Pipelines
+        run: |
+          deno run -A src/dagger/list_jobs.ts
+          dagger functions
+          dagger call build --src . --path example --tag demo:latest --platform linux/amd64,linux/arm64
+        working-directory: buildx
+  publish:
+    needs: test
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+      - uses: denoland/setup-deno@v1
+        with:
+          deno-version: v1.41
+      - name: Publish package
+        run: deno publish --allow-slow-types
+        working-directory: buildx

README.md

@@ -28,6 +28,7 @@ See [documentation](https://docs.dagger.io/zenith/) for more information about d
 | [ansible](./ansible/)       | Multiple versions and flavours of [ansible](https://github.com/ansible/ansible) |
 | [awesome-ci](./awesome-ci/) | Lot's of tools for git, file and static source code analysis. |
 | [black](./black/)           | The uncompromising Python code formatter [black](https://github.com/psf/black) |
+| [buildx](./buildx/)         | Build an OCI image of your project using [buildx](https://github.com/docker/buildx) |
 | [checkmake](./checkmake/)   | Lint Makefiles with [checkmake](https://github.com/mrtazz/checkmake) |
 | [conftest](./conftest/)     | Test your configuration files using [Conftest](https://conftest.dev/) |
 | [devbox](./devbox/)         | Instant, easy, and predictable development environments |

buildx/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[GitHub Issues](https://github.com/tsirysndr/daggerverse/issues).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

buildx/CONTRIBUTING.md

@@ -0,0 +1,53 @@
+# Contributing Guidelines
+
+Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional
+documentation, we greatly value feedback and contributions from our community.
+
+Please read through this document before submitting any issues or pull requests to ensure we have all the necessary
+information to effectively respond to your bug report or contribution.
+
+
+## Reporting Bugs/Feature Requests
+
+We welcome you to use the GitHub issue tracker to report bugs or suggest features.
+
+When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already
+reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
+
+* A reproducible test case or series of steps
+* The version of our code being used
+* Any modifications you've made relevant to the bug
+* Anything unusual about your environment or deployment
+
+
+## Contributing via Pull Requests
+Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
+
+1. You are working against the latest source on the *master* branch.
+2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
+3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
+
+To send us a pull request, please:
+
+1. Fork the repository.
+2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
+3. Ensure local tests pass.
+4. Commit to your fork using clear commit messages.
+5. Send us a pull request, answering any default questions in the pull request interface.
+6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
+
+GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
+
+
+## Finding contributions to work on
+Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
+
+
+## Code of Conduct
+This project has adopted the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+
+## Licensing
+
+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.

buildx/LICENSE

@@ -0,0 +1,19 @@
+Copyright (c) 2023 Tsiry Sandratraina <tsiry.sndr@fluentci.io>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

buildx/README.md

@@ -0,0 +1,44 @@
+# Module: Buildx
+
+![dagger-min-version](https://img.shields.io/badge/dagger-v0.10.0-blue?color=3D66FF)
+![deno compatibility](https://shield.deno.dev/deno/^1.41)
+[![](https://jsr.io/badges/@daggerverse/buildx)](https://jsr.io/@daggerverse/buildx)
+[![ci](https://github.com/tsirysndr/daggerverse/actions/workflows/ci.yml/badge.svg)](https://github.com/tsirysndr/daggerverse/actions/workflows/buildx.yml)
+
+This is a [Dagger](https://dagger.io) module for building an OCI image of your project using [buildx](https://github.com/docker/buildx).
+
+## 🚀 Usage
+
+```sh
+dagger -m github.com/tsirysndr/daggerverse/buildx call \
+  dev --src <source> terminal
+```
+
+## 🧑‍🔬 Example
+
+```sh
+dagger -m github.com/tsirysndr/daggerverse/buildx call \
+  dev --src . terminal
+
+dagger -m github.com/tsirysndr/daggerverse/buildx call \
+  build --src . \
+  --tag my-app \
+  --platform linux/amd64,linux/arm64
+```
+
+## ✨ Jobs
+
+| Name      | Description                         |
+| --------- | ----------------------------------- |
+| `dev`     | Start a development environment     |
+| `build`   | Build an OCI image of the project   |
+| `publish` | Publish the OCI image to a registry |
+
+## 🧑‍💻 Programmatic usage
+
+```typescript
+import { build } from 'jsr:@daggerverse/buildx';
+
+await plan(".");
+await build(".", "my-app", "linux/amd64,linux/arm64");
+```

buildx/dagger.json

@@ -0,0 +1,4 @@
+{
+  "name": "buildx",
+  "sdk": "github.com/fluentci-io/daggerverse/deno-sdk@main"
+}

buildx/deno.json

@@ -0,0 +1,33 @@
+{
+  "name": "@daggerverse/buildx",
+  "version": "0.1.0",
+  "exports": "./mod.ts",
+  "importMap": "import_map.json",
+  "tasks": {
+    "esm:add": "deno run -A https://esm.sh/v128 add",
+    "esm:update": "deno run -A https://esm.sh/v128 update",
+    "esm:remove": "deno run -A https://esm.sh/v128 remove",
+    "clean": "rm -rf gen schema.graphql"
+  },
+  "fmt": {
+    "exclude": [
+      "example/",
+      ".fluentci/",
+      "gen/"
+    ]
+  },
+  "lint": {
+    "exclude": [
+      "example/",
+      ".fluentci/",
+      "gen/"
+    ]
+  },
+  "test": {
+    "exclude": [
+      "example/",
+      ".fluentci/",
+      "gen/"
+    ]
+  }
+}