vikarti.anatra/proxmox-nag-buster
1
0
Fork 0
mirror of https://github.com/andrewpayne68/proxmox-nag-buster.git synced 2025-01-18 16:37:51 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated README

Browse source
This commit is contained in:
Scott B 2020-01-22 04:45:46 -08:00
parent 7ace374dfe
commit dd02dc0e59
1 changed files with 30 additions and 23 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

53
README.md
View file

@ -1,4 +1,4 @@
# pve-nag-buster ## pve-nag-buster
https://github.com/foundObjects/pve-nag-buster https://github.com/foundObjects/pve-nag-buster
This is a dpkg post install hook script that persistently removes license nags This is a dpkg post install hook script that persistently removes license nags
@ -15,50 +15,46 @@ gui and disables the pve-enterprise repository list. This script is called
every time a package updates the web gui or the pve-enterprise source list and every time a package updates the web gui or the pve-enterprise source list and
will only run if packages containing those files are changed. The installer will only run if packages containing those files are changed. The installer
drops the hook script and creates dpkg hooks to call it then adds the drops the hook script and creates dpkg hooks to call it then adds the
pve-no-subscription repo list. There are no external dependencies beyond the pve-no-subscription repo list and calls the hook script once. There are no
base packages installed with PVE by default (awk, sed, grep, wget). external dependencies beyond the base packages installed with PVE by default
(awk, sed, grep, wget).
### Installation ### Installation
``` ```sh
wget https://raw.githubusercontent.com/foundObjects/pve-nag-buster/master/install.sh wget https://raw.githubusercontent.com/foundObjects/pve-nag-buster/master/install.sh
# Always read scripts downloaded from the internet before running them with sudo # Always read scripts downloaded from the internet before running them with sudo
sudo bash install.sh
# or ..
chmod +x install.sh && sudo ./install.sh chmod +x install.sh && sudo ./install.sh
``` ```
With Git: With Git:
``` ```sh
git clone https://github.com/foundObjects/pve-nag-buster.git git clone https://github.com/foundObjects/pve-nag-buster.git
# Always read scripts downloaded from the internet before running them with sudo # Always read scripts downloaded from the internet before running them with sudo
cd pve-nag-buster && sudo ./install.sh cd pve-nag-buster && sudo ./install.sh
``` ```
### Uninstall: ### Uninstall:
``` ```sh
./install.sh --uninstall sudo ./install.sh --uninstall
# remove /etc/apt/sources.list.d/pve-no-subscription.list if desired # remove /etc/apt/sources.list.d/pve-no-subscription.list if desired
``` ```
### Notes: ### Notes:
#### Why is there base64 in my peanut-butter? #### Updating an old copy of the repo
For convenience the install script also contains a base64 encoded copy of the Sorry to those of you who forked the repo before about 2020-01-20; I rewrote
hook script, this makes installation possible without access to github or a
full clone of the project directory.
To inspect the base64 encoded script run `./install.sh --emit`; this dumps the
encoded copy to stdout and quits. To install using the stored copy just run
`sudo ./install.sh --offline`, no internet required.
#### Git repo history
Sorry to all 5 of you who forked the repo before about 2020-01-20; I rewrote
git history to cleanup the commit noise from adding files through GitHub's web git history to cleanup the commit noise from adding files through GitHub's web
UI. UI originally.
If you need to sync a cloned repo with the new history and haven't made any If you need to sync a cloned repo with the new history and haven't made any
changes: changes:
``` ```sh
git fetch --all -p -P git fetch --all -p -P
git push -f . origin/master:master git push -f . origin/master:master
``` ```
@ -69,7 +65,7 @@ Migrating to the new master branch should be fairly straightforward, the v02
tag repo state in the new commit history is identical to the repo state before tag repo state in the new commit history is identical to the repo state before
the rebase. the rebase.
``` ```sh
# save and commit your work # save and commit your work
git commit -a -m "WIP" git commit -a -m "WIP"
@ -77,8 +73,9 @@ git commit -a -m "WIP"
git checkout -b backup git checkout -b backup
git checkout - git checkout -
# from your branch
git fetch --all git fetch --all
git rebase -f --onto v02 origin/old-master <your branch here> git rebase -f --onto v02 origin/old-master
``` ```
I highly recommend picking at least the following bugfix commits if you don't I highly recommend picking at least the following bugfix commits if you don't
@ -87,6 +84,16 @@ want to track new work in master, they fix a couple of potential problems.
* a260891 hook script: fixed grep test issue * a260891 hook script: fixed grep test issue
* 427b23b more reliable hook trigger removal * 427b23b more reliable hook trigger removal
#### Why is there base64 in my peanut-butter?
For convenience the install script also contains a base64 encoded copy of the
hook script, this makes installation possible without access to github or a
full clone of the project directory.
To inspect the base64 encoded script run `./install.sh --emit`; this dumps the
encoded copy to stdout and quits. To install using the stored copy just run
`sudo ./install.sh --offline`, no internet required.
### Credits: ### Credits:
Thanks to John McLaren for his [blog post](https://www.reddit.com/user/seaqueue) documenting the web gui patch: Thanks to John McLaren for his [blog post](https://www.reddit.com/user/seaqueue) documenting the web gui patch: