just run my shit ffs
Go to file
j3s 312b5c57a2 Incomplete shrapnl kill draft 2021-10-21 21:28:54 -05:00
api Incomplete shrapnl kill draft 2021-10-21 21:28:54 -05:00
command Incomplete shrapnl kill draft 2021-10-21 21:28:54 -05:00
test Update lots, implement daemonize 2021-10-21 20:57:59 -05:00
util Update lots, implement daemonize 2021-10-21 20:57:59 -05:00
.gitignore ignore test/default 2021-05-24 06:12:33 +00:00
LICENSE in the beginning there was darkness 2021-03-30 21:48:04 -05:00
NOTES.md Standardize run command, implement list, TWOCHAINZ 2021-04-07 00:25:21 +00:00
README.md Format everything, write descriptive errors 2021-07-23 18:24:58 -05:00
TODO more TODO stuff 2021-10-21 21:17:40 -05:00
build.sh Many fixes, add run, gofmt 2021-07-26 08:16:49 -05:00
go.mod Update lots, implement daemonize 2021-10-21 20:57:59 -05:00
go.sum remove etcd dep 2021-04-14 00:06:33 +00:00
main.go Incomplete shrapnl kill draft 2021-10-21 21:28:54 -05:00

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