antipode.info/docker-backuppc
3
0
Fork 0
mirror of https://github.com/adferrand/docker-backuppc.git synced 2023-11-05 04:40:26 +01:00
Code Issues Releases Wiki Activity

Merge pull request #3 from diego-vieira/patch-1

Browse Source 
Update README.md
This commit is contained in:
Adrien Ferrand 2018-06-26 17:23:22 +02:00 committed by GitHub
commit c84003f5e9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -40,6 +40,7 @@ See [BackupPC documentation](http://backuppc.sourceforge.net/BackupPC-4.1.1.html
## Basic usage ## Basic usage
For testing purpose, you can create a new BackupPC instance with following command. For testing purpose, you can create a new BackupPC instance with following command.
**Please note that the basic usage is not suitable for production use.**
```bash ```bash
docker run \ docker run \
@ -48,9 +49,16 @@ docker run \
adferrand/backuppc adferrand/backuppc
``` ```
Latest BackupPC 4.x docker image will be downloaded if needed, and started. After starting, browse http://YOUR_SERVER_IP:8080 to access the BackupPC web Admin UI. A user/password will be asked: they are backuppc/password. You can then test your BackupPC instance. Latest BackupPC 4.x docker image will be downloaded if needed, and started.
After starting, browse http://YOUR_SERVER_IP:8080 to access the BackupPC web Admin UI.
Please note that the basic usage is not suitable for production use. BackupPC configuration and pool are persisted as anonymous data containers (see [Data persistency](#data-persistency)) with a weak control over it. Moreover BackupPC Admin Web UI is accessed from the unsecured HTTP protocol, exposing your user/password and data you could retrieve from the UI (see [UI SSL encryption](#ui-ssl-encryption)). The default credentials are:
- **username:** backuppc
- **password:** password
Then you can test your BackupPC instance.
BackupPC configuration and pool are persisted as anonymous data containers (see [Data persistency](#data-persistency)) with a weak control over it. Moreover BackupPC Admin Web UI is accessed from the unsecured HTTP protocol, exposing your user/password and data you could retrieve from the UI (see [UI SSL encryption](#ui-ssl-encryption)).
## Data persistency ## Data persistency