All of lore.kernel.org
 help / color / mirror / Atom feed
From: Angelo Compagnucci <angelo@amarulasolutions.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 5/5] package/mender: adding a readme file
Date: Tue,  5 Feb 2019 11:23:48 +0100	[thread overview]
Message-ID: <1549362228-5731-6-git-send-email-angelo@amarulasolutions.com> (raw)
In-Reply-To: <1549362228-5731-1-git-send-email-angelo@amarulasolutions.com>

This patch adds a readme file with basic instructions to get mender up
and running on a production system.

Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
---
 package/mender/readme.txt | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 package/mender/readme.txt

diff --git a/package/mender/readme.txt b/package/mender/readme.txt
new file mode 100644
index 0000000..329b2a4
--- /dev/null
+++ b/package/mender/readme.txt
@@ -0,0 +1,18 @@
+=== Notes on using Mender on Buildroot
+======================================
+Default configurations files
+----------------------------
+
+Buildroot comes with a default artifact_info and device_type configuration files
+in /etc/mender. They contain default values, and thus they should be overridden
+on a production system.
+
+The simplest way to do it is to change these files in an overlay or in a post
+build script.
+
+Configuring mender with certificates
+------------------------------------
+
+Mender uses TLS to communicate with the management server and, if you use a
+CA-signed certificate on the server, you should select the ca-certificates
+package otherwise it doesn't work.
-- 
2.7.4

  parent reply	other threads:[~2019-02-05 10:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 10:23 [Buildroot] [PATCH v2 0/5] Latest fixings to Mender Angelo Compagnucci
2019-02-05 10:23 ` [Buildroot] [PATCH v2 1/5] package/mender: adding a writable location Angelo Compagnucci
2019-02-05 10:30   ` Adam Duskett
2019-02-05 10:23 ` [Buildroot] [PATCH v2 2/5] package/mender: adding systemv init file Angelo Compagnucci
2019-02-05 10:29   ` Adam Duskett
2019-02-05 10:40     ` Titouan Christophe
2019-02-05 10:23 ` [Buildroot] [PATCH v2 3/5] package/mender: adding artifact_info file Angelo Compagnucci
2019-02-05 10:30   ` Adam Duskett
2019-02-05 10:23 ` [Buildroot] [PATCH v2 4/5] package/mender: adding device_type file Angelo Compagnucci
2019-02-05 10:29   ` Adam Duskett
2019-02-05 10:23 ` Angelo Compagnucci [this message]
2019-02-05 10:28   ` [Buildroot] [PATCH v2 5/5] package/mender: adding a readme file Adam Duskett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1549362228-5731-6-git-send-email-angelo@amarulasolutions.com \
    --to=angelo@amarulasolutions.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.