Oliver Stark

WIP rewrite for Craft 4

1

Discussions https://github.com/ostark/upper/discussions/68 & https://github.com/ostark/upper/discussions/65 Issue https://github.com/ostark/upper/issues/67 --- So far no significant code changes, just structural. --- - [x] Prepare for tests with pest - [x] Use Handler classes instead of...

AWS CloudFront support

6

Yet another driver ;-)

Cache invalidation for scheduled Entries

16

**Problem:** Scheduled Entries do not purge the cache automatically. # Idea A console command keeps an eye on `entries.postDate` and `entries. expiryDate`. This command must be scheduled via cron to...

Implement a driver that supports URL base purging https://docs.incapsula.com/Content/API/sites-api.htm#Purge2

* Use MYSQL_* ENV vars in bin/craft-copy-import-db.php * Check for missing DB_* ENV vars

composer.json ```json "allow-plugins": { "craftcms/plugin-installer": true, "fortrabbit/craft-auto-migrate": true, "yiisoft/yii2-composer": true }, ``` vs ```json "allow-plugins": { "craftcms/plugin-installer": true, "yiisoft/yii2-composer": true, "fortrabbit/craft-auto-migrate": true }, ```

We support * `master` * `main` * `{name-of-the-app}` but craft-copy uses always `master`

The package `symplify/git-wrapper` is abandoned, we should use `gitonomy/gitlib` instead. It is the suggested alternative, which is maintained, but the interface is different.

The actual changes happen in `fortrabbit/craft-auto-migrate`. This additional check assures that the composer plugin is not blocked. Context: https://getcomposer.org/doc/06-config.md#allow-plugins Sister tickets * PR https://github.com/fortrabbit/craft-auto-migrate/pull/10 * Issue https://github.com/craftcms/cms/issues/11971

Stop spawning new processes if counting queue jobs failed.