Mathieu Virbel
da3a2ac3a4
Rebrand the project from Fence to Greywall, the sandboxing layer of the GreyHaven platform. This updates: - Go module path to gitea.app.monadical.io/monadical/greywall - Binary name, CLI help text, and all usage examples - Config paths (~/.config/greywall/greywall.json), env vars (GREYWALL_*) - Log prefixes ([greywall:*]), temp file prefixes (greywall-*) - All documentation, scripts, CI workflows, and example files - README rewritten with GreyHaven branding and Fence attribution Directory/file renames: cmd/fence → cmd/greywall, pkg/fence → pkg/greywall, docs/why-fence.md → docs/why-greywall.md, example JSON files, and banner.
16 lines
873 B
Markdown
16 lines
873 B
Markdown
# Greywall Examples
|
|
|
|
Runnable examples demonstrating `greywall` capabilities.
|
|
|
|
If you're looking for copy/paste configs and "cookbook" workflows, also see:
|
|
|
|
- Config templates: [`docs/templates/`](../docs/templates/)
|
|
- Recipes for common workflows: [`docs/recipes/`](../docs/recipes/)
|
|
|
|
## Examples
|
|
|
|
| Example | What it demonstrates | How to run |
|
|
|--------|-----------------------|------------|
|
|
| **[01-dev-server](01-dev-server/README.md)** | Running a dev server in the sandbox, controlling external domains vs localhost outbound (Redis), and exposing an inbound port (`-p`) | `cd examples/01-dev-server && greywall -p 3000 --settings greywall-external-blocked.json npm start` |
|
|
| **[02-filesystem](02-filesystem/README.md)** | Filesystem controls: `allowWrite`, `denyWrite`, `denyRead` | `cd examples/02-filesystem && greywall --settings greywall.json python demo.py` |
|