rest-server/README.md

118 lines
5.2 KiB
Markdown
Raw Normal View History

# Rest Server
2015-09-08 21:35:48 +02:00
[![Build Status](https://travis-ci.org/restic/rest-server.svg?branch=master)](https://travis-ci.org/restic/rest-server)
[![Go Report Card](https://goreportcard.com/badge/github.com/restic/rest-server)](https://goreportcard.com/report/github.com/restic/rest-server)
[![GoDoc](https://godoc.org/github.com/restic/rest-server?status.svg)](https://godoc.org/github.com/restic/rest-server)
[![License](https://img.shields.io/badge/license-BSD%20%282--Clause%29-003262.svg?maxAge=2592000)](https://github.com/restic/rest-server/blob/master/LICENSE)
2016-11-05 18:53:57 +01:00
[![Powered by](https://img.shields.io/badge/powered_by-Go-5272b4.svg?maxAge=2592000)](https://golang.org/)
2016-12-30 22:40:11 +01:00
Rest Server is a high performance HTTP server that implements restic's [REST backend
2017-05-30 00:44:39 +02:00
API](https://github.com/restic/restic/blob/master/doc/rest_backend.rst). It provides secure and efficient way to backup
2016-12-30 22:40:11 +01:00
data remotely, using [restic](https://github.com/restic/restic) backup client.
2017-05-30 00:44:39 +02:00
## Requirements
2016-12-30 22:40:11 +01:00
2017-01-04 00:21:02 +01:00
Rest Server requires Go 1.7 or higher to build. The only tested compiler is the official Go compiler. Building server
2016-12-30 22:40:11 +01:00
with gccgo may work, but is not supported.
2017-05-30 00:44:39 +02:00
The minimum supported version of restic backup client is [v0.6.0](https://github.com/restic/restic/releases/tag/v0.6.0),
due to some [changes](https://github.com/restic/restic/commit/1a538509d0232f1a532266e07da509875fe9e0d6) in the REST
backend API.
## Installation
2016-12-30 22:40:11 +01:00
Run ```go run build.go```, afterwards you'll find the binary in the current directory. You can move it anywhere you
want. There's also an [example systemd service
file](https://github.com/restic/rest-server/blob/master/etc/rest-server.service) included, so you can get it up &
2017-05-01 19:12:53 +02:00
running as a proper service in no time. Of course, you can also test it from the command line.
2016-12-30 22:40:11 +01:00
```
% go run build.go
% ./rest-server --help
Run a REST server for use with restic
Usage:
rest-server [flags]
Flags:
--cpuprofile string write CPU profile to file
--debug output debug messages
-h, --help help for rest-server
2016-12-30 22:40:11 +01:00
--listen string listen address (default ":8000")
--log string log HTTP requests in the combined log format
2016-12-30 22:40:11 +01:00
--path string data directory (default "/tmp/restic")
--tls turn on TLS support
```
Alternatively, you can compile and install it in your $GOBIN with a standard `go install`. But, beware, you won't have
version info built into binary, when compiled that way.
2015-09-08 21:35:48 +02:00
## Getting started
2016-12-30 22:40:11 +01:00
By default the server persists backup data in `/tmp/restic`. Start the server with a custom persistence directory:
2015-09-08 21:35:48 +02:00
```
2016-12-30 23:26:15 +01:00
% rest-server --path /user/home/backup
2015-09-08 21:35:48 +02:00
```
2016-12-30 22:40:11 +01:00
The server uses an `.htpasswd` file to specify users. You can create such a file at the root of the persistence
directory by executing the following command. In order to append new user to the file, just omit the `-c` argument.
2015-09-08 21:35:48 +02:00
```
2016-12-30 22:40:11 +01:00
% htpasswd -s -c .htpasswd username
2015-09-08 21:35:48 +02:00
```
2016-12-30 22:40:11 +01:00
By default the server uses HTTP protocol. This is not very secure since with Basic Authentication, username and
passwords will travel in cleartext in every request. In order to enable TLS support just add the `-tls` argument and
add a private and public key at the root of your persistence directory.
2015-09-08 21:35:48 +02:00
2016-11-05 17:40:17 +01:00
Signed certificate is required by the restic backend, but if you just want to test the feature you can generate unsigned
keys with the following commands:
2015-09-08 21:35:48 +02:00
2015-09-07 15:11:03 +02:00
```
2016-12-30 22:40:11 +01:00
% openssl genrsa -out private_key 2048
% openssl req -new -x509 -key private_key -out public_key -days 365
2015-09-07 15:11:03 +02:00
```
2016-12-30 22:40:11 +01:00
2017-01-04 00:21:02 +01:00
Rest Server uses exactly the same directory structure as local backend, so you should be able to access it both locally
and via HTTP, even simultaneously.
To learn how to use restic backup client with REST backend, please consult [restic
2017-05-01 19:12:53 +02:00
manual](https://restic.readthedocs.io/en/latest/manual.html#rest-server).
2017-01-04 00:21:02 +01:00
2016-11-05 18:58:31 +01:00
## Contributors
Contributors are welcome, just open a new issue / pull request.
## License
```
The BSD 2-Clause License
Copyright © 2015, Bertil Chapuis
2016-12-30 22:40:11 +01:00
Copyright © 2016, Zlatko Čalušić, Alexander Neumann
2016-11-05 18:58:31 +01:00
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
```