| <?php | |
| function adminer_object() { | |
| class AdminerSoftware extends Adminer { | |
| function login($login, $password) { | |
| return true; | |
| } | |
| } | |
| return new AdminerSoftware; | |
| } | |
| include "./adminer-4.2.5.php"; |
| <?php | |
| add_action('plugins_loaded','ao_defer_inline_init'); | |
| function ao_defer_inline_init() { | |
| if ( get_option('autoptimize_js_include_inline') != 'on' ) { | |
| add_filter('autoptimize_html_after_minify','ao_defer_inline_jquery',10,1); | |
| } | |
| } | |
| function ao_defer_inline_jquery( $in ) { |
| <?php | |
| /** | |
| * Plugin Name: Installed Plugin Details | |
| * Description: Show a "Details" link for installed plugins to view information from the WordPress.org plugin directory. | |
| * Version: 1.0.0 | |
| * Author: Blazer Six | |
| * Author URI: http://www.blazersix.com/ | |
| * License: GPL-2.0+ | |
| * License URI: http://www.gnu.org/licenses/gpl-2.0.html | |
| * |
| # Cachebust static JS and CSS assets that contain a version segment, e.g. | |
| # /css/app.purged.min.v0.1.45.css ==> /css/app.purged.min.css | |
| location ~* (.+)\.v(?:[\d\.]+)\.(js|css)$ { | |
| try_files $uri $1.$2; | |
| } |
| https://silentadmin.gsans.com/everything-else/moving-zimbra-8-6-to-zimbra-8-7-1-on-a-new-server/ | |
| Moving Zimbra 8.6 to Zimbra 8.7.1 on a new server | |
| Disclaimer: I have the NETWORK/PRO version but chose not to use the backups. This method should work with both the free and paid version as a result. I have used a variation of this for every update since version version 7. We perform offsite backups and use tar to handle the sparse 80GB ldap file. This can run hot without the need to stop zimbra for most cases. The plan is to run this often and just before final cut-over do your shutdown as an extra precaution. You should be able to minimize your disruption to the production server. If you are just testing out the update process, you may never have to shutdown the production. I don’t and haven’t had any ldap issues testing while learning what it going to take to upgrade zimbra on my testing machines. You can test the new server with these hot images and even perform an upgrade test with this method. As the bac |
For this test I decided to start with a clean MariaDB install and initialize it with a backup from a current ZCS server. In the steps that follow:
ubuntu-test-1 will be the service that has a full ZCS install.ubuntu-test-2 will be the database server.
| ##!/bin/bash | |
| ## Format Backup: | |
| FORMAT=tgz | |
| ## Lokasi Backup | |
| ZBACKUP=/srv/backup/ | |
| ## Nama Folder Backup Berdasarkan Tanggal Backup | |
| DATE=`date +"%d%m%y"` |
| #!/bin/bash | |
| if [ -z $1 ]; then | |
| echo "ERROR: Proporcionar el usuario para le reporte" | |
| exit 1 | |
| fi | |
| sender(){ | |
| echo "Sender :" | |
| /opt/zimbra/libexec/zmmsgtrace -s "^${1}$" /opt/backup/logs/zimbra.log-202* > /tmp/${1} 2> /dev/null |
| # The command below creates a tgz file with all emails for user@domain.com in .eml format: | |
| # execute as root | |
| /opt/zimbra/bin/zmmailbox -z -m user@domain.com getRestURL "//?fmt=tgz" > /tmp/account.tgz | |
| # You can do the same via a REST URL: | |
| wget http://ZIMBRA.SERVER/home/user@domain.com/?fmt=tgz | |
| # to restore email: | |
| /opt/zimbra/bin/zmmailbox -z -m user@domain.com postRestURL "//?fmt=tgz&resolve=reset" /tmp/account.tgz |
Node Version Manager (https://github.com/nvm-sh/nvm) works perfectly across native node installations as well as emulated Rosetta installations. The trick I am using here is to install one LTS version of node under Rosetta and another stable version as native binary.