[PR #1213] [MERGED] Updating meshcentral's config casing to match upstreams json schema. #1839

New issue

Closed

opened 2026-03-02 02:24:58 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 02:24:58 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/amidaware/tacticalrmm/pull/1213
Author: @stavros-k
Created: 7/18/2022
Status: ✅ Merged
Merged: 10/6/2022
Merged by: @wh1te909

Base: develop ← Head: json

📝 Commits (2)

babf636 chore(install script): use same casing as the json schema
87d0522 apply json fix to docker aswell

📊 Changes

2 files changed (+43 additions, -43 deletions)

View changed files

📝 docker/containers/tactical-meshcentral/entrypoint.sh (+20 -20)
📝 install.sh (+23 -23)

📄 Description

I have also applied formatting with prettier.
I have it on a separate commit, I can easily drop it if you like so.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/amidaware/tacticalrmm/pull/1213 **Author:** [@stavros-k](https://github.com/stavros-k) **Created:** 7/18/2022 **Status:** ✅ Merged **Merged:** 10/6/2022 **Merged by:** [@wh1te909](https://github.com/wh1te909) **Base:** `develop` ← **Head:** `json` --- ### 📝 Commits (2) - [`babf636`](https://github.com/amidaware/tacticalrmm/commit/babf6366e898570b1b3b84232f805d22557bc97e) chore(install script): use same casing as the json schema - [`87d0522`](https://github.com/amidaware/tacticalrmm/commit/87d05223af4643ec1f2fc18a0994c9846d8ce691) apply json fix to docker aswell ### 📊 Changes **2 files changed** (+43 additions, -43 deletions) <details> <summary>View changed files</summary> 📝 `docker/containers/tactical-meshcentral/entrypoint.sh` (+20 -20) 📝 `install.sh` (+23 -23) </details> ### 📄 Description I have also applied formatting with prettier. I have it on a separate commit, I can easily drop it if you like so. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>