docs: Floci as the default emulator, with a seeded Docker Compose example - #161
Merged
DaviReisVieira merged 3 commits intoSep 14, 2026
Merged
Conversation
Floci serves its whole AWS surface on port 4566, so StackPort works against it with AWS_ENDPOINT_URL alone. - examples/docker-compose.floci.yml runs Floci, StackPort, and a one-shot seed container creating S3, SQS, SNS, DynamoDB, Secrets Manager, IAM, Logs and Step Functions resources, so the dashboard is populated on the first load - README gains a "Docker Compose (Floci + StackPort)" section and names Floci in Quick Start and the feature list
Compose example: - seed is idempotent (skips when the demo bucket exists) so a second `docker compose up` no longer fails on ResourceInUseException - persist hybrid storage in a named volume instead of an anonymous one - Docker socket is opt-in; drop `user: root` (the image's entrypoint already starts as root and drops to the floci user via gosu) - capture queue, topic and role ARNs from the CLI instead of hardcoding the account id; drop FLOCI_BASE_URL, FLOCI_HOSTNAME is sufficient Default emulator: - root docker-compose.yml runs Floci - README Quick Start uses `docker run -d` for Floci; MiniStack moves to the alternatives list and keeps its own compose example - CLAUDE.md, CONTRIBUTING, bug report template, Docker Hub description, VS Code extension README and pyproject keywords mention Floci
- write a `.seeded` marker last and key the skip on it, so a run that failed halfway is retried instead of skipped forever - `create` helper treats "already exists" as success and fails on anything else, which lets a retry get past completed steps - drop `-x` so the demo secret is not echoed into the seed logs - take the queue URL from create-queue instead of a second lookup - point the usage hint at `logs seed` when the dashboard is empty - README: the MiniStack compose file is a minimal variant, not "the same setup"; link the canonical ministackorg repo in both READMEs - VS Code extension marketplace description mentions Floci
This was referenced Sep 20, 2026
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Floci serves its whole AWS surface on port 4566, so StackPort works against it with AWS_ENDPOINT_URL alone. This PR makes Floci the default emulator and adds a seeded Compose example for it.
Compose example (
examples/docker-compose.floci.yml).seededmarker last and skips when it is present, and acreatehelper treats "already exists" as success so a run that failed halfway is retried rather than skippedfloci-datavolumeuser: rootis not needed, the image entrypoint already drops to theflociuserDefault emulator
docker-compose.ymlruns Floci instead of MiniStack and relies on the image's built-in healthcheckdocker run -d. MiniStack keeps its own Compose example and moves to the alternatives listVerified locally: fresh
up, a secondup(seed skips),downthenup(state survives in the volume), and a retry after a simulated partial seed. All 35 services probe with no errors.