As a PaaS, it is important on operating Flynn to be able to know and tweak some limits of the applications so a single one can’t bring down the cluster as whole.
Flynn offers such limits with sensible defaults:
How to set those limits and what they mean will be discussed now.
The very first version of PHPProm has just been released!
PHPProm is a library to measure some performance relevant metrics and expose them for Prometheus.
Its goal is to offer a simple, drop in solution to start measuring but without limiting customization.
This first version starts with an integration for Silex. Depending on the needs, other integrations for many other frameworks are on the horizon.
As the measurements are regulary collected by Prometheus visiting a specific endpoint, they need to be stored. PHPProm offeres support for various backends like Redis or Memcached.
Check out its repository including the full documentation: https://github.com/philiplb/CRUDlex
Continuous Delivery towards Flynn (CD), the self hosted platform as a service, is easily doable via Jenkins. Whereas the Jenkins specific parts are very low and they can be easily replaced with any other CI/CD software.
This posting skips the Continuous Integration part as this isn’t Flynn related and highly depends on the single project.
Some possible implementations are shown of a few scenarios I encountered using the git push deployment strategy of Flynn.
In order to use newer regions like Frankfurt, the CRUDlex Amazon S3 FileProcessor got a small update with the requirement of a newer version of the aws/aws-sdk-php. As this required a region parameter in the constructor, the small project changed to SemVer.
- Updated the aws/aws-sdk-php to ~3.19 and so requiring the region as first parameter in the constructor
- Relaxed a bit the required CRUDlex version