From a1b8e65e37df54039c78dad618f052967f3d02ab Mon Sep 17 00:00:00 2001 From: Arseniy Kuznetsov Date: Sat, 17 Dec 2022 08:36:25 +0100 Subject: [PATCH] Update README.md --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index 228bd2b..5b6b308 100644 --- a/README.md +++ b/README.md @@ -102,8 +102,7 @@ docker run -v "$(pwd)/mktxp:/home/mktxp/mktxp/" -p 49090:49090 -it --rm ghcr.io/ #### MKTXP stack install [MKTXP Stack Getting Started](https://github.com/akpw/mktxp-stack#install--getting-started) provides similar instructions around editing the mktxp.conf file and, if needed, adding a dedicated API user to your Mikrotik RouterOS devices as mentioned below. -💡 In the case usage within a [Docker Swarm](https://docs.docker.com/engine/swarm/) is desired, please do make sure to have all settings explicitly set in both the `mktxp.conf` and `_mktxp.conf` files. -Not doing this may cause [issues](https://github.com/akpw/mktxp/issues/55#issuecomment-1346693843) regarding a `read-only` filesystem. +💡 *In the case of usage within a [Docker Swarm](https://docs.docker.com/engine/swarm/), please do make sure to have all settings explicitly set in both the `mktxp.conf` and `_mktxp.conf` files. Not doing this may cause [issues](https://github.com/akpw/mktxp/issues/55#issuecomment-1346693843) regarding a `read-only` filesystem.* ## Mikrotik Device Config For the purpose of RouterOS device monitoring, it's best to create a dedicated user with minimal required permissions. \