12.23.0 now available

Aliysa_Enhance

It is very important for this release that all servers are updated to the same version to avoid undefined behaviour. As root on each server in your cluster run ‘apt update && apt upgrade’.

Added

Node.js websocket proxy support.
Inode resource limit per website. This is a package setting and can be overriden on a per website basis. (https://enhance.com/docs/resource-usage/set-per-website-resource-limits.html)

Enhanced

PostGIS and PGVector now enabled by default on new PostgreSQL installations.
Automatically recalculate subscription on cloning failure.
Default post_max_size and upload_max_filesize now 1000M if no specific limit is configured.
Explicitly set WordPress site url and home when using search replace to mitigate object cache issue on cloning.
Copy button added to domains table.
Improved Hebrew and Portugese translations.
Increased timeout for email role migration again.
Primary domain now always listed first on domains table.
wp-admin button on the website dashboard now defaults to the installation in public_html ahead of any addon domains.

Fixed

Application installations now adhere to package database resource limits.

rdbf

Aliysa_Enhance Default post_max_size and upload_max_filesize now 1000M if no specific limit is configured.

Looks like the Nginx client_max_body_size still defaults to 200m;

mth

Aliysa_Enhance PostGIS and PGVector now enabled by default on new PostgreSQL installations.

What do we do for existing installations? Can we enable?

ecomlabs

Congratulations team, I have a surprise for the community that I will reveal soon 🙂

DracoBlue

I’m eagerly waiting for the Email Features functionality.

marowi

DracoBlue Yeah, me too. Enhance really needs better spam detection, such as learning spam filters.

JohnBee

DracoBlue

Same here!
So looking forward to this so I can get off Mailcow lol

opsec

Bulk migration plesse

mike

we need blacklist/whitelist domains not only emails..

pratik_asabe

@Aliysa_Enhance How will inode limit behave when addon domains are in picture? for example, we have a client using 40 adon domains and at pkg level 1 website is assigned + 40 addon domain, so, will it take all files and folders including the addon domain's root folders and its files into consideration? like this doesn't care addon domain or not, website or not it has set to 150000 inode limit at pkg level it it stop writing files for that pkg?! can you please bring some light on this to better clarify. Thank you..

Adam

pratik_asabe

It's applied per-website like the block limit. It includes all addon/parked domains - the disk quota is applied by the Linux kernel and is not aware of domains.

Adam

mth

As root, run:

apt install postgresql-postgis postgresql-16-pgvector
psql -U postgres -c "CREATE EXTENSION IF NOT EXISTS vector; CREATE EXTENSION IF NOT EXISTS postgis;"

mmhospedagem

@Adam
It's been 3 years since we've been waiting for a decent Plesk to Enhance migrator. You said it was ready 2 years ago and it was never released. Any estimate?