From 90fefedb136230bbdb28617f1a29a35f77e03b93 Mon Sep 17 00:00:00 2001 From: Diego Vieira Date: Mon, 25 Jun 2018 12:10:42 +0100 Subject: [PATCH 1/3] Update README.md --- README.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 0b6ff78..6abf5a8 100644 --- a/README.md +++ b/README.md @@ -40,6 +40,7 @@ See [BackupPC documentation](http://backuppc.sourceforge.net/BackupPC-4.1.1.html ## Basic usage 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 docker run \ @@ -48,9 +49,16 @@ docker run \ 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 is +- **username:** backuppc +- **password:** password + +You can then 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 From 025a7459bdff6bf8fce30c1ae62fb623b2382e1b Mon Sep 17 00:00:00 2001 From: Adrien Ferrand Date: Tue, 26 Jun 2018 17:22:30 +0200 Subject: [PATCH 2/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6abf5a8..f24fc46 100644 --- a/README.md +++ b/README.md @@ -52,7 +52,7 @@ docker run \ 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. -The default credentials is +The default credentials are: - **username:** backuppc - **password:** password From 56bf3e27de5109cb80dda609a12c023fef2a9546 Mon Sep 17 00:00:00 2001 From: Adrien Ferrand Date: Tue, 26 Jun 2018 17:23:01 +0200 Subject: [PATCH 3/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f24fc46..5672772 100644 --- a/README.md +++ b/README.md @@ -56,7 +56,7 @@ The default credentials are: - **username:** backuppc - **password:** password -You can then test your BackupPC instance. +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)).