A single-fire first-come-first-serve HTTP server.
- Send and receive to and from stdin or stdout.
- Use external executables to process and respond to HTTP requests.
- Reverse proxy and redirect HTTP requests.
- Multiple methods of NAT traversal: UPnP-IGD, STUN and TURN (ICE).
- Support for cloud integration with built in discovery / signalling server to allow for self hosted instances.
- Works with any HTTP client including browsers, only one person needs to have oneshot installed.
- Support for rich, machine-readable output; easily integrate oneshot into your pipelines.
- Highly configurable HTTP responses, custom upload clients, and more.
There are multiple ways of obtaining oneshot:
curl -L https://github.com/forestnode-io/oneshot/raw/v2/v2/install.sh | sudo sh
Copy and paste any of these commands into your terminal to install oneshot. For some portion of Linux users, there are .deb and .rpm packages available in the release page.
brew tap forestnode-io/brew
brew install forestnode-io/brew/oneshot
go get -u -v github.com/forestnode-io/oneshot/v2
git clone https://github.com/forestnode-io/oneshot
cd oneshot/v2
sudo make install
Head over to the release page and download the windows .zip file.
go get -u -v github.com/forestnode-io/oneshot/v2
$ oneshot send path/to/file.txt
Then, from a browser (or any HTTP client) simply go to your computers I.P. address and the file download will be triggered.
$ oneshot send -u username -W path/to/file.txt
The -W
option will cause oneshot to prompt you for a password.
Oneshot also supports HTTPS, simply pass in the key and certificate using the --tls-key
and --tls-cert
flags.
$ oneshot receive .
The receive
subcommand is used for receiving data from the client.
A connecting browser will be prompted to upload a file which oneshot then save to the current directory.
$ oneshot receive | jq '.first_name'
If the receive subcommand is used and no directory is given, oneshot will write the received file to its standard out.
$ oneshot send -D my/web/page.html
The -D
flag tells oneshot to not trigger a download client-side.
$ sudo apt update | oneshot send -n apt-update.txt
Oneshot can transfer from its standard input; by default files are given a random name.
The optional flag -n
sets the name of the file.
$ oneshot send -u foo -P password -c my_non-cgi_script.sh
Oneshot can run your scripts and programs in a CGI flexible CGI environment.
Even non-CGI executables may be used; oneshot will provide its own default headers or you can set your own using the -H
flag.
$ oneshot exec -- 'echo "Hello $(jq -r '.name')!"'
Here, the exec
subcommand tells oneshot to run its input as a shell command in a flexible CGI environment.
In another terminal we can test our api:
$ curl -X POST -H 'Content-Type: application/json' -d '{"name": "world"}' localhost:8080
Hello World!
$ oneshot -u | gofmt | oneshot -J
The -J
flag we are using here tells oneshot to only start serving HTTP once it has received an EOF from its stdin.
This allows us to create unix pipelines without needing to specify a different port for each instance of oneshot.
In this scenario, the user would upload or type in some Go code and upon hitting the back button (refresh won't work !) or going back to the original URL, the user will receive their formatted Go code.
Please report any bugs or issues here.
I consider oneshot to be nearly feature complete; feature requests and contributions are welcome.