Samples

Starting points for running Binacle.Net. Each one is a folder of files to download and edit.

🐳 Docker

Five setups, from nothing switched on to everything.

• Minimal: the smallest configuration that still answers requests.
• Quickstart: trying Binacle.Net out, with the docs and the web UI.
• Prod: the API behind your own backend. Most deployments want this one.
• Service: Binacle.Net offered to callers you do not control.
• Full: everything on at once, for a machine nobody else can reach.

The Docker page explains the choice between prod and service.

☸️ Kubernetes

• Minimal: a minimal deployment on an existing cluster.

📖 Two things that apply to all of them

Presets.json is your bin set. Every sample ships an example one. Replacing it with your own boxes, lockers or pallets is the first thing to do; until then the answers describe someone else’s packaging.

These shapes are tested. Each Docker sample has a matching smoke profile of the same name, run against the image on every release.

🏷️ About the image tag

Every sample pins binacle/binacle-net:3.0 - the minor tag, which picks up fixes within the 3.0 line and never a breaking change. A copied sample should not jump to a new major on the next pull, which is what latest would do.

📄 Copying these files

Every file on these pages is under the MIT License, not the licence covering the API code. Copy one into your own project and nothing follows it. The NOTICE file in the repository is the full map of which licence covers which part.