When ownCloud removed the ability to share a calendar publicly, I had no other choice than forcing my acquaintances to register to my ownCloud.
I didn't want that, so I implemented my own solution.
samedi 30 juillet 2016
Par Mathieu le samedi 30 juillet 2016, 08:09 - Hacks
When ownCloud removed the ability to share a calendar publicly, I had no other choice than forcing my acquaintances to register to my ownCloud.
I didn't want that, so I implemented my own solution.
mercredi 27 juillet 2016
Par Mathieu le mercredi 27 juillet 2016, 10:56 - Hacks
Warning : the Rule plugin for Drupal 8 was not considered stable when I wrote this post.
Drupal 8 modules structure changed, and many modules are now using the new API.
No more plain old functions name like hook_something, no more obscurous PHP for menu entries. Instead, Object Oriented programming, YAML configuration files, magic comments, and Symfony routing.
Let's give it a try, let's make our first simplest module.
If you already know how to do this, jumb to next section.
Create a directory for your module, for instance mymodule.
Create an info file in YAML format : mymodule/mymodule.info.yaml:
name: 'My Module' type: module core: 8.x package: Custom
You don't need more! You don't need routing as you will plug into Rules.
Create the RulesAction directory and its parents: mymodule/src/Plugin/RulesAction/
Create a PHP file for your class: MyAction.php. The class will be loaded with the autoload system.
Edit the file you just created, and specify the namespace at the beginning of the file:
/** * @file * Contains \Drupal\mymodule\Plugin\RulesAction\MyAction. */ namespace Drupal\mymodule\Plugin\RulesAction; use Drupal\rules\Core\RulesActionBase;
The namespace must correspond to your module name and class name!
Comments are very important as they are also specifications. You will define your Action id, description, and parameters. For instance, here is a copied sample from the predefined action DataSet:
/** * Provides a 'My action' action. * * @RulesAction( * id = "rules_myaction", * label = @Translation("Set a data value"), * category = @Translation("Data"), * context = { * "data" = @ContextDefinition("any", * label = @Translation("Data"), * description = @Translation("Specifies the data to be modified using a data selector, e.g. 'node:author:name'."), * allow_null = TRUE, * assignment_restriction = "selector" * ), * "value" = @ContextDefinition("any", * label = @Translation("Value"), * description = @Translation("The new value to set for the specified data."), * default_value = NULL, * required = FALSE * ) * } * ) */
The Rule id is rules_myaction.
The category of the action in the dropdown menu is Data and it will be labeled Set a data value.
The current action will have two parameters : the data that will be changed, and the corresponding value.
Again, no more plain callback, the function doExecute will be called to execute your Action:
class MyAction extends RulesActionBase { /** * Executes the Plugin. * * @param mixed $data * Original value of an element which is being updated. * @param mixed $value * A new value which is being set to an element identified by data selector. */ protected function doExecute($data, $value) { $typed_data = $this->getContext('data')->getContextData(); $typed_data->setValue($value); } /** * {@inheritdoc} */ public function autoSaveContext() { // Saving is done at the root of the typed data tree, for example on the // entity level. $typed_data = $this->getContext('data')->getContextData(); $root = $typed_data->getRoot(); $value = $root->getValue(); // Only save things that are objects and have a save() method. if (is_object($value) && method_exists($value, 'save')) { return ['data']; } return []; } }
The class name has to correspond to your file name.
In this sample, the parameter $value will be set to $data.
Uncaught PHP Exception Drupal\\Component\\Plugin\\Exception\\PluginException: "Plugin (rules_myaction) instance class "Drupal\\tbh_system\\Plugin\\RulesAction\\MyAction" does not exist."
Your namespace/classname/filename/directoryname is probably wrong.
mercredi 22 juin 2016
Par Mathieu le mercredi 22 juin 2016, 21:16 - Hacks
The Puppet master comes by default with a basic WEBrick server. It allow a quick start for those that are not familiar with Puppet, but when the number of Puppet nodes grows, the performances of the default WEBrick server are going down quickly.
The Puppet documentation show how to configure Apache and Passenger to replace the default WEBrick server, but what if you have a lot of nodes ? What if you want to apply your configuration within minutes, instead of the default half-hour threshold before the agent asks the master if something changed ?
Or you may just want a fancy Nginx instead of your plain-old-reliable Apache.
Here is how.
lundi 20 juin 2016
Par Mathieu le lundi 20 juin 2016, 09:53 - My Life
Ou « ce que je n'ai pas dit à l'oraison funèbre, parce que c'est pas mon truc de parler devant des gens tristes pour les faire pleurer ».
lundi 13 juin 2016
Par Mathieu le lundi 13 juin 2016, 17:03 - Informatique
Cet article est une traduction libre de https://www.fastmail.com/help/technical/ssltlsstarttls.html
J'ai réalisé cette traduction pour fournir à mes clients une explication simple mais complète sur le pourquoi du comment de SSL/TLS/STARTTLS lors de la configuration de leur client mail.
Attention, l'article original date de 2012.
Protocole : un protocole de communication est un format de données, un "langage" permettant à deux machine de communiquer entre elles. Les deux machines doivent être en capacité de parler le même protocole pour pouvoir échanger des données. SSL est un protocole de communication sécurisé ("chiffrés"), popularisé par le célèbre "cadenas" visible sur les pages web.
Port : un port est un numéro de service sur lequel les logiciels vous pouvoir communiquer entre eux. La plupart des numéros de port sont associés à des protocoles précis.
« billets précédents - page 4 de 32 - billets suivants »