janit

<?php

// This is the namespace you want to use
use EzSystems\EzPlatformRichText\eZ\FieldType\RichText\Type as RichTextFieldType;

// this would be a method in your class (you'll need to inject RichTextFieldType)
// It has some extra wrangling of input not required, but makes it moarrr robust
private function prepareRichText($inputText){
    
    if($inputText === ''){

janit

#!/bin/bash

# for use with cron, eg:
# 0 3 * * * postgres /var/db/db_backup.sh foo_db

if [[ -z "$1" ]]; then
    echo "Usage: $0 <db_name> [pg_dump args]"
    exit 1
fi

janit

Keybase proof

I hereby claim:

• I am janit on github.
• I am janit (https://keybase.io/janit) on keybase.
• I have a public key ASAVpmR_PpgT0putmX8REETDu2wYOegUUqL5Mq_pWcmb4wo

To claim this, I am signing this object:

janit

## Configure db connections ##
doctrine:
    dbal:
        connections:
            repo_one_connection:
                driver: pdo_mysql
                host: localhost
                user: repo_one
                password: foo
                dbname: repo_one

janit

// https://www.npmjs.com/package/node-unifi
var unifi = require('node-unifi');

var controller = new unifi.Controller("CONTROLLER_IP_HERE", 8443);

// LOGIN
controller.login("YOUR_USER_HERE", "YOUR_PASSWORD_HERE", function(err) {

  if(err) {
    console.log('ERROR: ' + err);

janit

Recently I did a round of benchmark on the performance and memory implications for an install of Ibexa Experience. You can find this article with some analysis of results here: Benchmarks of Composer 2.0 vs 1.10 with Ibexa DXP

Björn Köster was interested in if I had did any tests for eZ Platform EE 2.5. I had not, but have now. Similar to with Ibexa DXP, the improvements are significant on 2.0. Scripts used for this (single) benchmark are in other files. See raw results below.

------8<------------------8<------------------8<------------------8<------------------8<------------

Composer 1.10:

janit

composer selfupdate --2
sleep 10

./benchmark.sh
cp results.txt 2_0-1.txt 
sleep 60

./benchmark.sh
cp results.txt 2_0-2.txt 

janit

// YAML config for sending emails on eZ Platform Cloud / Platform.sh on eZ Platform v3.0 and higher

swiftmailer:
    url: 'smtp://%env(PLATFORM_SMTP_HOST)%'
    spool: { type: 'memory' }

janit

eZ Platform v3.0.0 used ezplatform-kernel 1.0.0 package which had an issue with
storing images in the wrong directory: https://jira.ez.no/browse/EZP-31546

The issue was fixed in ezplatform-kernel 1.0.1 (shipped in eZ Platform v3.0.1),
but misplaced files and corrupt database entries for image binaries remain in
the wrong location. This will make your installation not work consistently.

This is a set of commands that can be used to remedy the issue and bring your 
file structure and database up-to-date if you have been running version 3.0.0

janit

self.addEventListener('install', function (event) {
    event.waitUntil(preLoad());
});

var preLoad = function () {
    //    console.log('[PWA Builder] Install Event processing');
    return caches.open('pwabuilder-offline').then(function (cache) {
        //        console.log('[PWA Builder] Cached index and offline page during Install');
        return cache.addAll(['/offline.html', '/']);
    });