PHPackages phz/ric-wordpress - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [File & Storage](/categories/file-storage) 4. / 5. phz/ric-wordpress ActiveWordpress-plugin[File & Storage](/categories/file-storage) phz/ric-wordpress ================= A Wordpress plugin for high-performance Responsive Image Cache (RIC) 124PHP Since Jun 19Pushed 2y ago31 watchersCompare [ Source](https://github.com/phzfi/ric-wordpress)[ Packagist](https://packagist.org/packages/phz/ric-wordpress)[ RSS](/packages/phz-ric-wordpress/feed)WikiDiscussions master Synced 1mo ago READMEChangelogDependenciesVersions (1)Used By (0) RIC Wordpress -plugin 1. Project Description ---------------------- [](#1-project-description) Wordpress plugin for Responsive Image Cache (RIC) ### 1.1. Business Vision [](#11-business-vision) Resize and cache images exactly to the view port to increase performance, in comparison to traditional caches that might provide 3 image sizes, non being optimal, and having the client to resize the image. ### 1.2. Task Management [](#12-task-management) ### 1.3. Personas [](#13-personas) ### 1.4. Use Cases [](#14-use-cases) ### 1.5. Non-Functional Requirements [](#15-non-functional-requirements) PHZ-PERF-1 Load the page in less than 1000ms. 2. Architecture --------------- [](#2-architecture) ### 2.1. Technologies [](#21-technologies) Dev - TODO CI - PHZ internal Jenkins Staging - PHZ.fi staging (internal) Production - Published on - Used by and other sites ### 2.2. Naming, Terms and Key Concepts [](#22-naming-terms-and-key-concepts) Environments and the configs should be named as - dev: docker-compose.yml (i.e. use the default names for dev env), but .env.dev - (ci): use the dev -env on CI - stg: docker-compose.stg.yml, .env.stg - prod: docker-compose.prod.yml, .env.prod ### 2.3. Coding Convention [](#23-coding-convention) Directory structure - doc/ for UML documents - etc/ for nginx, ssh etc configs. Can be cp -pr etc/ /etc to the virtual machine during provisioning and matches the os directory structure - results/ test results - reports/ for e.g. code coverage reports - src/ for source code \*\* Note! Source code should be placed under a single folder (src) that can be mounted over Docker -volume or Vagrant -shared folder inside the virtual machine so that node\_modules or vendor directory are not on the shared folder. See and for further details how to circumvent the problems. - tests/ for tests ### 2.4. Development Guide [](#24-development-guide) Add here examples and hints of good ways how to code the project. Convert the silent knowledge as tacit knowledge here. - See [https://en.wikipedia.org/wiki/Knowledge\_management](https://en.wikipedia.org/wiki/Knowledge_management) 3. Development Environment -------------------------- [](#3-development-environment) Note! PHZ Coding Convention: name this environment as dev. Note! However, please use the default files for dev env, such as docker-compose.yml (instead of docker-compose.dev.yml). ### 3.1. Prerequisites [](#31-prerequisites) ### 3.2. Start the Application [](#32-start-the-application) ### 3.3. Access the Application [](#33-access-the-application) ### 3.4. Run Tests [](#34-run-tests) ### 3.5. IDE Setup and Debugging [](#35-ide-setup-and-debugging) ### 3.6. Version Control [](#36-version-control) ### 3.7. Databases and Migrations [](#37-databases-and-migrations) ### 3.8. Continuous Integration [](#38-continuous-integration) 4. Staging Environment ---------------------- [](#4-staging-environment) Note! PHZ Coding Convention: name this environment as stg. ### 4.1. Access [](#41-access) ### 4.2. Deployment [](#42-deployment) ### 4.3. Smoke Tests [](#43-smoke-tests) #### 4.3.1. Automated Test Cases [](#431-automated-test-cases) #### 4.3.2. Manual Test Cases [](#432-manual-test-cases) ### 4.4. Rollback [](#44-rollback) ### 4.5. Logs [](#45-logs) ### 4.6. Monitoring [](#46-monitoring) 5. Production Environment ------------------------- [](#5-production-environment) Note! PHZ Coding Convention: name this environment as prod. ### 5.1. Access [](#51-access) ### 5.2. Deployment [](#52-deployment) ### 5.3. Smoke Tests [](#53-smoke-tests) #### 5.3.1. Automated Test Cases [](#531-automated-test-cases) #### 5.3.2. Manual Test Cases [](#532-manual-test-cases) ### 5.4. Rollback [](#54-rollback) ### 5.5. Logs [](#55-logs) ### 5.6. Monitoring [](#56-monitoring) 6. Operating Manual ------------------- [](#6-operating-manual) ### 6.1. Scheduled Jobs [](#61-scheduled-jobs) ### 6.2. Manual Processes [](#62-manual-processes) 7. Problems ----------- [](#7-problems) ### 7.1. Environments [](#71-environments) ### 7.2. Coding [](#72-coding) ### 7.3. Dependencies [](#73-dependencies) Add here TODO and blockers that you have found related to upgrading to newer versions. List the library/framework/service, version, and then the error message. ### Health Score 16 — LowBetter than 5% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity8 Limited adoption so far Community15 Small or concentrated contributor base Maturity22 Early-stage or recently created project Bus Factor2 2 contributors hold 50%+ of commits How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Community Maintainers ![](https://www.gravatar.com/avatar/3259510501f9aaf1f0b3097e8341eef88f8fa293f87ab21ba90acac029ddc189?d=identicon)[phz](/maintainers/phz) --- Top Contributors [![fubla](https://avatars.githubusercontent.com/u/10085991?v=4)](https://github.com/fubla "fubla (1 commits)")[![LKeronen](https://avatars.githubusercontent.com/u/15157973?v=4)](https://github.com/LKeronen "LKeronen (1 commits)")[![pharazon](https://avatars.githubusercontent.com/u/1275167?v=4)](https://github.com/pharazon "pharazon (1 commits)") ### Embed Badge ![Health badge](/badges/phz-ric-wordpress/health.svg) ``` [![Health](https://phpackages.com/badges/phz-ric-wordpress/health.svg)](https://phpackages.com/packages/phz-ric-wordpress) ``` ### Alternatives [knplabs/gaufrette PHP library that provides a filesystem abstraction layer 2.5k39.8M123](/packages/knplabs-gaufrette)[superbalist/flysystem-google-storage Flysystem adapter for Google Cloud Storage 26320.6M30](/packages/superbalist-flysystem-google-storage)[illuminate/filesystem The Illuminate Filesystem package. 15161.6M2.6k](/packages/illuminate-filesystem)[creocoder/yii2-flysystem The flysystem extension for the Yii framework 2931.7M62](/packages/creocoder-yii2-flysystem)[flowjs/flow-php-server PHP library for handling chunk uploads. Works with flow.js html5 file uploads. 2451.6M15](/packages/flowjs-flow-php-server)[madnest/madzipper Easier zip file handling for Laravel applications. 1382.3M6](/packages/madnest-madzipper) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)