tacticalrmm
tacticalrmm copied to clipboard
Improvements to the installation script
This first PR is part of a series of changes to refactor the installation script. It maintains its original functionality and does not break or go against the current method of installing TRMM.
Some of the changes in this PR include:
- Standardize variable names and abstract them as much as possible.
- Modularize script logic & flow by creating functions to eliminate duplicate code.
- Apply a consistent formatting style.
- Log installation to a file for troubleshooting purposes. ✅
- Eliminate the requirement of adding the
tacticalrmm
user tosudo
. ✅
The long-term goals for modernizing the script are as follows:
- Improve code readability and allow some customization by the sysadmin.
- Allow automated installs for quick deployments (e.g. ./install.sh -args).
- Eliminate useless third-party dependencies, such as
lsb-release
. - Branch out configuration files into separate files.
- Make the scripts portable so TRMM can be used on other operating systems besides Linux (and avoid bashism).
Codecov Report
Merging #1176 (06d9fa2) into develop (7ac9af1) will not change coverage. The diff coverage is
n/a
.
:exclamation: Current head 06d9fa2 differs from pull request most recent head 091aedc. Consider uploading reports for the commit 091aedc to get more accurate results
@@ Coverage Diff @@
## develop #1176 +/- ##
========================================
Coverage 82.26% 82.26%
========================================
Files 113 113
Lines 7487 7487
========================================
Hits 6159 6159
Misses 1328 1328
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more
There's already a previous PR in the works for major modifications to the install script.
Working on the same install.sh in different directions is going to have one path have to re-write/fix. Might want to see about collaboration working together on this...or the devs will have to pick a winner in the end
I'm aware of the previous contribution and open to collaborate, although our long-term goals are conflicting from the looks of it. I'm working to slim down the installer and make it portable without having to rely on additional components or dependencies. This means avoiding dialogs and keeping it simple. In my opinion, the installer is a one-time script to deploy TRMM, not a Swiss Army knife to manage the instance.
I prefer the project's lead developers choose what matters to them. It's also understandable if they do not wish to accept any contributions to the installer or related scripts at this time.
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.