Links archive. For now it doesn't store data in a database, you can store your links locally piping the response to a file.
Why make GUIs when you can just use cURL
and jq
?
The docker container is not published anywhere yet. Those steps are to build and run the container. When the container is published, the steps will be:
$ docker pull b-ap/links:1.0
$ docker run -p 8000:8000 b-ap/links:1.0
For now, they are:
- Clone this repository.
$ docker build -t b-ap/links:1.0 .
$ docker images | grep links
$ docker run -p 8000:8000 b-ap/links:1.0
$ curl -X POST -H "Content-Type: application/json" -d '{"title": "b-ap website", "url": "b-ap.xyz"}' localhost:8000
- You can also use
jq
to format the response:$ curl -X POST -H "Content-Type: application/json" -d '{"title": "b-ap website", "url": "b-ap.xyz"}' localhost:8000 | jq
- To list all your links, just send a
GET
request to the page:$ curl -X GET localhost:8000 | jq
- If you want to store it locally, just pipe the response to a file:
$ curl -X GET localhost:8000 | jq > links.txt
- Clone this repository.
$ go run links.go
$ curl -X POST -H "Content-Type: application/json" -d '{"title": "b-ap website", "url": "b-ap.xyz"}' localhost:8000
- You can also use
jq
to format the response:$ curl -X POST -H "Content-Type: application/json" -d '{"title": "b-ap website", "url": "b-ap.xyz"}' localhost:8000 | jq
- To list all your links, just send a
GET
request to the page:$ curl -X GET localhost:8000 | jq
- If you want to store it locally, just pipe the response to a file:
$ curl -X GET localhost:8000 | jq > links.txt