An open API service indexing awesome lists of open source software.

https://github.com/floci-io/floci-labs

Show me what you did today, not just screenshot of the landing page
https://github.com/floci-io/floci-labs

aws azure gcp labs

Last synced: 28 days ago
JSON representation

Show me what you did today, not just screenshot of the landing page

Awesome Lists containing this project

README

          

# Floci Labs

> Stop screenshotting the landing page. **Build something.**

Floci Labs is a community-driven collection of things people have actually built with [Floci](https://floci.io) — the free, MIT-licensed local AWS emulator. Snippets, mini-projects, tutorials, weird experiments, anything goes.

If you've spun up Floci and made something cool with it — even something silly — this is where it lives.

---

## What counts as a lab?

Anything that runs against Floci. Some examples to get the gears turning:

- **Snippets** — a 50-line script showing how to wire S3 + Lambda + SQS locally
- **Mini-projects** — a working URL shortener, a local-only photo gallery, a chat backend
- **Tutorials** — a walkthrough of testing your Terraform against Floci before applying to real AWS
- **Integrations** — Floci + Testcontainers, Floci + your favorite framework, Floci in CI
- **Weird stuff** — a multiplayer game using DynamoDB as the state store, ASCII art generated by Bedrock and stored in S3, whatever you want
- **Benchmarks & comparisons** — "I migrated from X to Floci, here's what broke and what didn't"

There is no quality bar except "it runs." Half-baked is fine. Hacky is fine. Educational, weird, useful — all welcome.

## How to contribute a lab

1. **Fork this repo.**
2. **Copy `labs/_template/` to `labs/your-lab-name/`.** Use kebab-case (`labs/sqs-fanout-demo`, not `labs/SQS Fanout!`).
3. **Build your lab.** Whatever language, whatever stack. Just make sure it runs against a stock `floci/floci:latest` container.
4. **Fill in the lab's `README.md`** — what it does, how to run it, why someone might care.
5. **Open a PR.** A maintainer will skim it, maybe leave a comment, and merge.

That's it. No CLA, no template police, no "please rewrite this section." If it works and isn't harmful, it goes in.

## How to use a lab

Every lab is self-contained in its own folder. Clone the repo, `cd` into the lab you want, follow its README.

```bash
git clone https://github.com/floci-io/floci-labs.git
cd floci-labs/labs/example-s3-photo-gallery
# follow the lab's README
```

Most labs assume you have Floci running on `localhost:4566`. If you don't:

```bash
docker run -d --name floci -p 4566:4566 \
-v /var/run/docker.sock:/var/run/docker.sock \
floci/floci:latest
```

## Lab index

| Lab | What it does | Stack |
|-----|--------------|-------|
| [example-s3-photo-gallery](labs/example-s3-photo-gallery) | A tiny photo gallery backed by local S3 | Node.js, S3 |
| [eks-hello-cluster](labs/eks-hello-cluster) | Full EKS control-plane lifecycle on Floci, plus a kubectl workload bonus | Bash, AWS CLI, EKS/k3s |

> _Your lab here. Open a PR._

## Ground rules

- **It has to run against vanilla Floci** — no paid services, no special builds.
- **Be kind in reviews and discussions.** Some labs will be a contributor's first open-source PR. Treat them that way.
- **No secrets, no real credentials.** Floci accepts any dummy key; use `test`/`test`.
- **MIT licensed**, same as Floci itself. By submitting, you agree your lab is shared under MIT.

## Community

- **Slack:** [floci.slack.com](https://floci.slack.com)
- **Discussions:** [floci-io/floci · Discussions](https://github.com/floci-io/floci/discussions)
- **Main repo:** [github.com/floci-io/floci](https://github.com/floci-io/floci)

---

Floci Labs is maintained alongside [Floci](https://github.com/floci-io/floci). Light, fluffy, and always free.