KevinMidboe/mktxp-no-cli
1
0
Fork 0
mirror of https://github.com/KevinMidboe/mktxp-no-cli.git synced 2025-10-29 17:50:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #57 from FinlayDaG33k/add-note-docker-swarm

Browse Source 
Add note regarding usage in Docker Swarm
This commit is contained in:
Arseniy Kuznetsov
2022-12-17 08:33:31 +01:00
committed by GitHub
parent 01d14b11be b2d96b6eef
commit 35075d262d
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -102,6 +102,8 @@ docker run -v "$(pwd)/mktxp:/home/mktxp/mktxp/" -p 49090:49090 -it --rm ghcr.io/
#### MKTXP stack install #### 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. [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.
## Mikrotik Device Config ## Mikrotik Device Config
For the purpose of RouterOS device monitoring, it's best to create a dedicated user with minimal required permissions. \ For the purpose of RouterOS device monitoring, it's best to create a dedicated user with minimal required permissions. \