just run my shit ffs
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
j3s 312b5c57a2 Incomplete shrapnl kill draft 2 months ago
api Incomplete shrapnl kill draft 2 months ago
command Incomplete shrapnl kill draft 2 months ago
test Update lots, implement daemonize 2 months ago
util Update lots, implement daemonize 2 months ago
.gitignore ignore test/default 7 months ago
LICENSE in the beginning there was darkness 8 months ago
NOTES.md Standardize run command, implement list, TWOCHAINZ 8 months ago
README.md Format everything, write descriptive errors 5 months ago
TODO more TODO stuff 2 months ago
build.sh Many fixes, add run, gofmt 4 months ago
go.mod Update lots, implement daemonize 2 months ago
go.sum remove etcd dep 8 months ago
main.go Incomplete shrapnl kill draft 2 months ago

README.md

shrapnl

shrapnl is a service that allows users to run binaries or scripts on-demand, or persistently.

site:

Matrix: https://matrix.to/#/#shrapnl:cyberia.club

Mailing List: https://lists.cyberia.club/~cyberia/ops

Docs: https://godocs.io/giit.cyberia.club/~j3s/shrapnl

shrapnl is:

  • fast: simple shrapnls must execute nearly instantly (within 200ms end to end)
  • simple: use sane defaults and do not provide unnecessary flags, the cli must be intuitive
  • secure: shrapnl must use best practices for isolation - contained in cgroups, permissions limited

our runtimes include:

  • python3
  • ruby
  • crystal
  • golang
  • c
  • POSIX sh
  • bash
  • lua (what version?)
  • javascript/typescript (via deno)

a shrapnl may be a long-running service, or it may run once and die.

dat test dir?

the test dir is layed out like so:

test
├── default <-- our symlinks to binaries storage area
|
├── binaries <-- our actual binaries go here
|
├── container <-- our minimal container image
|
└── test-binaries <-- small test binaries we upload to shrapnl for testing