Mention transfer.sh in README and add screenshots to README.
This commit is contained in:
parent
697bf21eda
commit
d6e0d21e89
12
README.md
12
README.md
@ -10,6 +10,12 @@ Why create RUFF when WOOF exists? WOOF is no longer in the debian repos and
|
||||
it's easier to `go get` a tool than it is to hunt down Simon's website for
|
||||
the latest copy.
|
||||
|
||||
Why use RUFF over something like Transfer.sh? Transfer.sh is fantastic for
|
||||
sharing files over the net, but you have to upload, wait for that, then wait
|
||||
on it to download on the destination. If you're sharing a WiFi network with
|
||||
your target device, it's a lot simpler and potentially MUCH faster to skip
|
||||
the middle man and chuck your file straight to its new home.
|
||||
|
||||
## Installation
|
||||
|
||||
`go get git.tilde.town/diff/ruff`
|
||||
@ -23,3 +29,9 @@ Assuming $GOPATH is in $PATH:
|
||||
and
|
||||
|
||||
`ruff -u # to receive a cool file`
|
||||
|
||||
## Screenshots
|
||||
|
||||

|
||||
|
||||

|
6
main.go
6
main.go
@ -9,6 +9,12 @@
|
||||
// Why create RUFF when WOOF exists? WOOF is no longer in the debian repos and
|
||||
// it's easier to `go get` a tool than it is to hunt down Simon's website for
|
||||
// the latest copy.
|
||||
//
|
||||
// Why use RUFF over something like Transfer.sh? Transfer.sh is fantastic for
|
||||
// sharing files over the net, but you have to upload, wait for that, then wait
|
||||
// on it to download on the destination. If you're sharing a WiFi network with
|
||||
// your target device, it's a lot simpler and potentially MUCH faster to skip
|
||||
// the middle man and chuck your file straight to its new home.
|
||||
package main
|
||||
|
||||
import (
|
||||
|
Loading…
x
Reference in New Issue
Block a user