feat: document the blueprint sources (#130)

Author: Serial-ATA

pages/developers/_meta.ts

@@ -19,6 +19,7 @@ const meta: Meta = {
   "tangle-avs": "Build a Tangle Blueprint",
   "eigenlayer-avs": "Build an Eigenlayer AVS",
   "testing-with-tangle": "Testing with Tangle",
+  deployment: "Deployment",
   troubleshooting: "Troubleshooting",
   "-- solution-developers": {
     type: "separator",

pages/developers/cli/quickstart.mdx

@@ -25,12 +25,4 @@ cargo tangle blueprint create --name <blueprint-name>
 
 ## Deploying your Blueprint
 
-Once you're ready to deploy your blueprint, simply:
-
-```shell
-export SIGNER="//Alice"
-export EVM_SIGNER="0xcb6df9de1efca7a3998a8ead4e02159d5fa99c3e0d4fd6432667390bb4726854"
-cargo tangle blueprint deploy tangle --devnet
-```
-
-See [deploy command reference](./tangle.mdx#deploying-a-blueprint) for all options.
+See [Deployment](/developers/deployment/introduction)

pages/developers/deployment/_meta.ts

@@ -0,0 +1,8 @@
+import { Meta } from "nextra";
+
+const meta: Meta = {
+  introduction: "Introduction",
+  sources: "Sources",
+};
+
+export default meta;

pages/developers/deployment/introduction.mdx

@@ -0,0 +1,26 @@
+# Deploying Blueprints
+
+In order for a blueprint to be instance-able, it'll need to be deployed and have one or more sources defined.
+
+## Defining Sources
+
+Before deploying, you must specify the sources from which to fetch the blueprint binaries.
+See [Sources](/developers/deployment/sources/introduction).
+
+## Deploying via the CLI
+
+Once you're ready to deploy your blueprint, simply:
+
+Install the [cargo-tangle] CLI, if you haven't already.
+
+For testing, you can deploy to a local devnet:
+
+```shell
+export SIGNER="//Alice"
+export EVM_SIGNER="0xcb6df9de1efca7a3998a8ead4e02159d5fa99c3e0d4fd6432667390bb4726854"
+cargo tangle blueprint deploy tangle --devnet
+```
+
+See [deploy command reference](/developers/cli/tangle#deploying-a-blueprint) for all options.
+
+[cargo-tangle]: /developers/cli/installation

pages/developers/deployment/sources/_meta.ts

@@ -0,0 +1,12 @@
+import { Meta } from "nextra";
+
+const meta: Meta = {
+  introduction: "Introduction",
+  native: "Native",
+  container: "Container",
+  tee: "Trusted Execution Environment (WIP)",
+  wasm: "WASM (WIP)",
+  testing: "Testing",
+};
+
+export default meta;

pages/developers/deployment/sources/container.mdx

@@ -0,0 +1,35 @@
+# Container Source
+
+The `Container` source is used for blueprints that are intended to be built as container images and published to image
+registries, such as `docker.io`.
+
+## Requirements
+
+The requirements for running containerized blueprints are available [here](/operators/manager/requirements#container-sources)
+
+## Format
+
+The `Container` source has the following format:
+
+```rust
+pub struct ContainerSource {
+    pub registry: String,
+    pub image: String,
+    pub tag: String,
+}
+```
+
+Where:
+
+- `registry` - The registry to pull the image from (e.g., `docker.io`)
+- `image` - The name of the image (e.g., `some-user/my-blueprint`)
+- `tag` - The release tag of the image (e.g., `latest`)
+
+And they can be specified in the manifest of your binary crate like so:
+
+```toml
+[package.metadata.blueprint]
+sources = [
+    { type = "Container", registry = "docker.io", image = "some-user/my-blueprint", tag = "latest" }
+]
+```

pages/developers/deployment/sources/introduction.mdx

@@ -0,0 +1,22 @@
+# Blueprint Sources
+
+Blueprints can be built and distributed in multiple formats (visible on the sidebar).
+
+A blueprint can define many sources of different types in the manifest of its binary crate:
+
+```toml
+[package.metadata.blueprint]
+sources = [
+    { type = "Container", registry = "docker.io", image = "some-user/my-blueprint", tag = "latest" },
+    # Fallback container source
+    { type = "Container", registry = "ghcr.io", image = "some-user/my-blueprint", tag = "latest" },
+    # Native binary source
+    { type = "Native", owner = "some-github-user", repo = "some-blueprint", tag = "0.1.0", binaries = [
+        { arch = "Amd64", os = "Linux", name = "my-blueprint-bin" },
+    ] },
+]
+```
+
+The above example has two container sources, which allows an operator to attempt a pull from different sources in the event
+that one of the registries is unreachable. Additionally, it has a native source which can act as a fallback for operators
+that either cannot or prefer not to support running containerized blueprints.

pages/developers/deployment/sources/native.mdx

@@ -0,0 +1,55 @@
+# Native Sources
+
+The `Native` source is used for blueprints that compile to a native binary and release via the [`release.yml`] GitHub workflow
+from the blueprint template.
+
+## Requirements
+
+The requirements for running native blueprints are available [here](/operators/manager/requirements#native-sources)
+
+## Format
+
+The `Native` source has the following format:
+
+```rust
+pub struct NativeSource {
+    pub owner: String,
+    pub repo: String,
+    pub tag: String,
+    pub binaries: Vec<BlueprintBinary>,
+}
+
+pub struct BlueprintBinary {
+    pub arch: Architecture,
+    pub os: OperatingSystem,
+    pub name: String,
+}
+```
+
+Where:
+
+- `owner` - The owner of the GitHub repository (e.g., `tangle-network`)
+- `repo` - The name of the repository (e.g., `some-blueprint`)
+- `tag` - The release tag of the binary (e.g., `0.1.0`)
+- `binaries` - A list of binaries (e.g., see below)
+
+And in `BlueprintBinary`:
+
+- `arch` - The architecture the blueprint was built for (see [Architecture])
+- `os` - The operating system the blueprint was built for (see [OperatingSystem])
+- `name` - The name of the binary in the GitHub release (e.g., `my-blueprint-bin`)
+
+And they can be specified in the manifest of your binary crate like so:
+
+```toml
+[package.metadata.blueprint]
+sources = [
+    { type = "Native", owner = "some-github-user", repo = "some-blueprint", tag = "0.1.0", binaries = [
+        { arch = "Amd64", os = "Linux", name = "my-blueprint-bin" },
+    ] },
+]
+```
+
+[`release.yml`]: https://github.com/tangle-network/blueprint-template/blob/main/.github/workflows/release.yml
+[Architecture]: https://docs.rs/tangle-subxt/latest/tangle_subxt/tangle_testnet_runtime/api/runtime_types/tangle_primitives/services/sources/enum.Architecture.html
+[OperatingSystem]: https://docs.rs/tangle-subxt/latest/tangle_subxt/tangle_testnet_runtime/api/runtime_types/tangle_primitives/services/sources/enum.OperatingSystem.html

pages/developers/deployment/sources/tee.mdx

@@ -0,0 +1,31 @@
+# Trusted Execution Environment Sources
+
+The `TEE` (Trusted Execution Environment) source is used for blueprints that are built as container images, and intended to
+be deployed to a [dstack] TEE.
+
+## Requirements
+
+The requirements for running TEE blueprints are available [here](/operators/manager/requirements#tee-sources)
+
+## Format
+
+The `TEE` source has the following format:
+
+```rust
+// TBD...
+```
+
+Where:
+
+- TODO
+
+And they can be specified in the manifest of your binary crate like so:
+
+```toml
+[package.metadata.blueprint]
+sources = [
+    { type = "TEE", ... },
+]
+```
+
+[dstack]: https://github.com/Dstack-TEE/dstack

pages/developers/deployment/sources/testing.mdx

@@ -0,0 +1,53 @@
+# Testing Source
+
+The `Testing` source is a special, automatically generated source that was historically used by the [Blueprint Manager]
+during integration tests. It has since been replaced with the [test harnesses](/developers/testing/introduction).
+
+## Format
+
+The `Testing` source has the following format:
+
+```rust
+pub struct TestingSource {
+    pub cargo_package: String,
+    pub cargo_bin: String,
+    pub base_path: String,
+}
+```
+
+Where:
+
+- `cargo_package` - The Cargo package name of the binary (e.g., `my-blueprint-bin`)
+- `cargo_bin` - The name of the built binary file (e.g., `my-blueprint-bin`)
+- `base_path` - The base path of the binary crate (e.g., `/home/user/my-blueprint/bin`)
+
+And they can be specified in the manifest of your binary crate like so:
+
+```toml
+[package.metadata.blueprint]
+sources = [
+    { type = "Testing", cargo_package = "some-package-name", cargo_bin = "some-binary", base_path = "/home/user/some-blueprint/bin" }
+]
+```
+
+## Output
+
+After building your blueprint, you'll notice something like the following in your `blueprint.json`:
+
+```json
+{
+  // ...
+  "sources": [
+    {
+      "type": "Testing",
+      "cargo_package": "my-blueprint-bin",
+      "cargo_bin": "my-blueprint-bin",
+      "base_path": "/home/user/my-blueprint/bin"
+    }
+  ],
+}
+```
+
+It can safely be ignored (or deleted if you prefer).
+
+[Blueprint Manager]: /operators/manager/introduction