Jeremy Gardais
2add0a1412
It will link the last tar file to a better name. |
||
---|---|---|
proxmox | ||
CHANGELOG | ||
README.md | ||
TODO.md | ||
block_list.sh | ||
copy_to_usb.sh | ||
grav_cron | ||
ldap1_connection.sh | ||
mail2sesame | ||
sesame2mail | ||
snapsend.sh | ||
update_iso.sh | ||
wordpress_cron | ||
zfSnap.sh |
README.md
ipr_scripts
Table of Contents
Overview
Some usefull scripts for admin or users.
Scripts
Proxmox
vzdump-hook-lxc-template.pl
This script must be used as a vzdump's hook (the backup utility for CT and VMs for Proxmox).
- The script will :
- Remove the templates oldest than 2 days (by default).
- Copy the current dump as a template in /mnt/zfsbkp/template/cache (by default).
- How-to use :
- Define a backup as usual (in the Proxmox's webgui) and prefer to select only one container.
- In command on the hypervisor, open /etc/pve/vzdump.cron and edit the line of the new dump to add : --script /usr/local/bin/vzdump-hook-lxc-template.pl.
- Customization :
- If you don't store template in the default path (/mnt/zfsbkp/template/cache), please edit the variable $TEMPLATE_DIR in the script.
Grav
grav_cron
A daily cron to check if Grav got available updates.
- It need to work from the Grav's root directory.
- If an update is available, it will create a empty file (${GRAV_ROOT}/logs/update), else it will ensure the "update" file is removed.
- Be sure to monitore if ${GRAV_ROOT}/logs/update exist.
Sesame2mail
Give a user's mail address from it's user ID (sesame).
The first argument can be :
- A file with a list of user ID (sesame), one per line.
- A user ID (sesame), only one.
WordPress
wordpress_cron
A daily cron to check WordPress's Core and plugins updates.
- It need [wp-cli][wp-cli website] tool.
- If an update is available, it will create a empty file (
{WP_ROOT}/.update_core or
{WP_ROOT}/.update_plugin), else it will ensure the "update" files are absents.- So, be sure to monitore if the files ${WP_ROOT}/.update_* exists !