This repository has been archived on 2026-03-13. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
greywall/docs/README.md
Mathieu Virbel da3a2ac3a4 rename Fence to Greywall as GreyHaven sandboxing component
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.
2026-02-10 16:00:24 -06:00

1.9 KiB

Greywall Documentation

Greywall is a sandboxing tool that restricts network and filesystem access for arbitrary commands. It's most useful for running semi-trusted code (package installs, build scripts, CI jobs, unfamiliar repos) with controlled side effects.

Getting Started

  • Quickstart - Install greywall and run your first sandboxed command in 5 minutes
  • Why Greywall - What problem it solves (and what it doesn't)

Guides

Reference

Examples

See examples/ for runnable demos.

Quick Reference

Common commands

# Block all network (default)
greywall <command>

# Use custom config
greywall --settings ./greywall.json <command>

# Debug mode (verbose output)
greywall -d <command>

# Monitor mode (show blocked requests)
greywall -m <command>

# Expose port for servers
greywall -p 3000 <command>

# Run shell command
greywall -c "echo hello && ls"