Why did you choose Mercure.rocks for your solution?


Can you introduce yourself and your project?


What are the short term results, the first metrics seen?


Could you tell us more about the next evolutions of your project?


Can you give us the technical context of your project?


Read a new case study made with one of our partners, <a rel="noreferrer noopener" href="https://mail.tm/en/" target="_blank">mail.tm</a>. Meet their team and see the technical choices that led to the current development of this project.



<h2>Can you introduce yourself and your project?</h2>



We&rsquo;re the team behind <a href="http://mail.tm/">Mail.tm</a> &#8211; an email service that helps users to protect against spam, bots, phishing and other online abuse without exposing their real email address.



<figure class="wp-block-image size-medium is-style-rounded"><a href="https://mail.tm/en"><img loading="lazy" width="600" height="360" src="https://api.les-tilleuls.coop/wp-content/uploads/2022/02/vignette-mail-600x360.jpg" alt="" class="wp-image-4541" srcset="https://api.les-tilleuls.coop/wp-content/uploads/2022/02/vignette-mail-600x360.jpg 600w, https://api.les-tilleuls.coop/wp-content/uploads/2022/02/vignette-mail-1024x614.jpg 1024w, https://api.les-tilleuls.coop/wp-content/uploads/2022/02/vignette-mail-300x180.jpg 300w, https://api.les-tilleuls.coop/wp-content/uploads/2022/02/vignette-mail-768x460.jpg 768w, https://api.les-tilleuls.coop/wp-content/uploads/2022/02/vignette-mail.jpg 1181w" sizes="(max-width: 600px) 100vw, 600px" /></a></figure>



<h2>Can you give us the technical context of your project?</h2>



We do use different technologies, all of them are open source projects, to which we&rsquo;ve contributed for some of them:



<ul><li>API: <a rel="noreferrer noopener" href="https://api-platform.com" target="_blank">API Platform</a> (PHP, Symfony based)</li><li>Database: MongoDB (JavaScript, sharded cluster)</li><li>Notifications: <a rel="noreferrer noopener" href="https://mercure.rocks" target="_blank">Mercure</a> (Go, Caddy module)</li><li>OS: <a rel="noreferrer noopener" href="https://www.centos.org/" target="_blank">CentOS</a></li><li>SMTP: <a rel="noreferrer noopener" href="https://haraka.github.io" target="_blank">Haraka</a> (JavaScript)</li><li>Web-interface: <a rel="noreferrer noopener" href="https://nuxtjs.org" target="_blank">Nuxt.js</a> (JavaScript, Vue.js based)</li><li>Web-server: <a rel="noreferrer noopener" href="https://caddyserver.com" target="_blank">Caddy</a> (Go)</li></ul>



<h2>Why did you choose Mercure.rocks for your solution?</h2>



We needed a notification system that notifies the user of incoming emails without making an API request every 10 seconds.



First, this would help to minimize database access in terms of performance. Secondly, this would allow almost instant notification as the user will be using a single connection to listen on a channel that will inform whenever there is a message.



We started looking for open-source self-hosted software and while developing our API we were already aware of Mercure. It was coming as a default notification system with API Platform.



Needless to say, we had a tight budget and the main requirement was that the notification software could run on a budget server and handle a few thousand notifications per hour.



As Mercure is created and backed up by the same people behind API Platform, we had to try it out! There should be a reason why it came as a default notification system with API Platform.



<h2>What are the short term results, the first metrics seen?</h2>



The first results were amazing as Mercure was running fine on the Hetzner CX11* server while handling a few thousand notifications per hour.



* Hetzner CX11 server with a price of just € 2.49 (1 vCPU, 2GB RAM, 20GB Disk Space).



Currently, Mercure handles about 8 million notifications per day and it&rsquo;s increasing every day. You might be surprised but we&rsquo;ve only recently upgraded the Mercure server to a better one Hetzner&rsquo;s CPX21 at € 6.90 (3 vCPU, 4GB RAM, 80GB Disk Space).



<h2>Could you tell us more about the next evolutions of your project?</h2>



We&rsquo;re currently working on our next project. The project idea is a simple email testing service for developers with IMAP/POP3/SMTP/API access. We’re planning to use all the technology that we&rsquo;ve used for <a rel="noreferrer noopener" href="http://mail.tm/" target="_blank">Mail.tm</a> as we&rsquo;re quite happy as it runs smoothly and fast as light!

Mail.tm: using Mercure.rocks and API Platform for an email service

Read a new case study made with one of our partners, mail.tm. Meet their team and see the technical choices that led to the current development of this project. Can you introduce yourself and your project? We&rsquo;re the team behind Mail.tm &#8211; an email service that helps users to protect against spam, bots, phishing and [&hellip;]

Mail.tm: using Mercure.rocks and API Platform for an email service | Les-Tilleuls.coop

Les-Tilleuls.coop

https://api.les-tilleuls.coop/wp-content/uploads/2022/02/vignette-mail.jpg

Accueil

https://secure.gravatar.com/avatar/54fb8ea2a1a36c3b9ef44f25bf976b48?s=96&d=mm&r=g

Cécile Hamerel

API Platform in a few words:



<ul><li style="text-align: justify;" role="presentation">more than 500 contributors.</li><li style="text-align: justify;" role="presentation">3.8&nbsp;million <a href="https://packagist.org/packages/api-platform/core" target="_blank" rel="noopener">downloads on Packagist</a>;</li><li style="text-align: justify;" role="presentation">A core team growing day by day;</li><li style="text-align: justify;" role="presentation">6,000 stars on Github;</li><li style="text-align: justify;" role="presentation">More than 3000 members on the #api-platform channel of Symfony’s Slack;</li><li style="text-align: justify;" role="presentation">A recognized technological reference used by big names on the web around the world: Orange, Decathlon, Arte or even France Télévisions are using API Platform.</li></ul>



A couple of weeks ago, we updated the <a href="https://api-platform.com/" target="_blank" rel="noopener">API Platform</a> website by developing the community sections. Let&rsquo;s have a look together:&nbsp;



<blockquote class="twitter-tweet">The <a href="https://twitter.com/ApiPlatform?ref_src=twsrc%5Etfw">@ApiPlatform</a> website now has a community section with a dedicated page for each contributor, the upcoming events and awesome wallpapers featuring Webby! Thanks <a href="https://twitter.com/ginifizz?ref_src=twsrc%5Etfw">@ginifizz</a> for your amazing work! <a href="https://t.co/oq8K35rnXG">https://t.co/oq8K35rnXG</a>— Kévin Dunglas (@dunglas) <a href="https://twitter.com/dunglas/status/1234887739675414528?ref_src=twsrc%5Etfw">March 3, 2020</a></blockquote>
<script async="" src="//platform.twitter.com/widgets.js" charset="utf-8"></script>



<h3>Top contributors</h3>



Because we believe that every community project should value the people who contribute to it, we now display the list of all API Platform contributors on <a href="http://api-platform.com/community/contributors/" target="_blank" rel="noopener">a dedicated page</a>! Not surprisingly, the core team are at the top of the ranking but if you have contributed to the framework, you should see yourself too 🙂



<figure class="wp-block-image"><a href="https://api-platform.com/community/contributors/v" target="_blank" rel="noopener"><img src="https://api.les-tilleuls.coop/wp-content/uploads/2021/08/353.gif" alt="giphy" title="giphy"/></a></figure>



In addition to this improvement, if you click on a profile, you will have the details of all the repositories on which the contributor has worked:&nbsp;



<figure class="wp-block-image"><a href="https://api-platform.com/community/contributors/Deuchnord" target="_blank" rel="noopener"><img src="https://api.les-tilleuls.coop/wp-content/uploads/2021/08/355.png" alt="deuchnord" title="deuchnord"/></a></figure>



<h3>Events</h3>



From now on, you can see the upcomings API Platform meetups on <a rel="noreferrer noopener" href="https://api-platform.com/community/events/" target="_blank">a special page</a>. Stay tuned, more events should be coming soon. For the moment only events hosted by Meetup are added (via their API), we are currently looking to add events from other platforms as well.&nbsp;



<figure class="wp-block-image"><a href="https://api-platform.com/community/events/" target="_blank" rel="noreferrer noopener"><img src="https://api.les-tilleuls.coop/wp-content/uploads/2021/08/356.png" alt="Events" title="Events"/></a></figure>



<h3>Resources</h3>



From the Resources section, you can now&nbsp;access to different contents:&nbsp;



<ul><li>News: on this part of the website, you have <a href="https://twitter.com/ApiPlatform" target="_blank" rel="noreferrer noopener">API Platform’s Twitter</a> displayed. If you still have not followed this account, this is the moment to do so 🙂&nbsp;</li><li>Logos: you have now access to a page where you can find different logos and typos in SVG or PNG. These creations are protected by a <a href="https://api-platform.com/trademark-policy" target="_blank" rel="noreferrer noopener">trademark policy</a>, don’t hesitate to contact us if you have any questions.</li><li>Wallpapers: now, you can also download API Platform wallpapers ( 2880 x 1800px; 1920 x 1080px or 1920 x 1200px): <a href="https://api-platform.com/resources/wallpapers/" target="_blank" rel="noreferrer noopener">https://api-platform.com/resources/wallpapers/</a></li><li>Coloring Webby: during the lockdown, we created the possibility to <a href="https://api-platform.com/resources/colouring-webby/" target="_blank" rel="noreferrer noopener">download our coloring pages</a>. As you can see below, some little artists shared their masterpieces with us &lt;3</li></ul>



<blockquote class="twitter-tweet"><a href="https://twitter.com/coopTilleuls?ref_src=twsrc%5Etfw">@coopTilleuls</a> voilà un chef-d&rsquo;œuvre de mon fils de cinq ans, ravi d&rsquo;avoir colorié « des trucs de l&rsquo;espace »! <a href="https://t.co/MWQmQqrqSf">pic.twitter.com/MWQmQqrqSf</a>— Christophe Dujarric (@Chris_Dujarric) <a href="https://twitter.com/Chris_Dujarric/status/1248252567437692930?ref_src=twsrc%5Etfw">April 9, 2020</a></blockquote>



We are currently working on new evolutions for the website, stay tuned! Help us to continuously improve this project by <a rel="noreferrer noopener" href="http://github.com/api-platform/" target="_blank">contributing to it.</a> You can also give it a star on Github or follow us on <a rel="noreferrer noopener" href="https://twitter.com/ApiPlatform" target="_blank">Twitter</a>!&nbsp;

API Platform: community & ressources

API Platform in a few words: more than 500 contributors. 3.8&nbsp;million downloads on Packagist; A core team growing day by day; 6,000 stars on Github; More than 3000 members on the #api-platform channel of Symfony’s Slack; A recognized technological reference used by big names on the web around the world: Orange, Decathlon, Arte or even [&hellip;]

API Platform: community & ressources | Les-Tilleuls.coop

https://api.les-tilleuls.coop/wp-content/uploads/2021/08/358.png

API Platform: community &#038; ressources

For some time now, we have been implementing a new routine in our SCOP: every two months, the whole team meets up for a whole day dedicated to contributing to the Free tools we use, we develop&#8230; or not!



This new initiative comes in addition to what was already allocated to some of our cooperators to maintain some of the projects that allow our structure (like so many others) to prosper. The problem of the sustainability and maintenance of Free Software &#8211; Although they are the foundation of the information society &#8211; is a complex and publicly useful subject to which few effective answers have yet been found.



By dedicating time to our developers to work on these projects, our cooperative is trying to improve the situation and to contribute in return to the public interest infrastructures created and maintained for free by developers from all over the world. It&rsquo;s also a good opportunity for our teams to learn new skills, to discover new technologies and to face advanced problems.



Despite the calm of August, we have again taken up this challenge: a few days ago, about twenty cooperators gathered to fix security issues, resolve bugs, review patches proposed by the community and add new features on various free projects that we like.



The day started with the constitution of the working groups:&nbsp;



The API Platform working group was busy releasing API Platform 2.4.6 and preparing the imminent release of API Platform 2.5 beta ;



The team working on React Admin focused on finalizing a brand new version of the integration with API Platform (done in collaboration with Marmelab) which will greatly improve its ease of use and customization;



The team working on Symfony focused on fixing bugs affecting the tool.



Discover our contributions:



The team finalized the addition of a major new feature that will arrive in API Platform 2.5: the support of generated API formats (such as Hydra) in the auto-generated OpenAPI documentation, and the possibility to generate JSON Schema corresponding to a resource;



Using this new infrastructure, Jacques Lefebvre added a command to export a JSON Schema from a ressource;



Quentin Barloy solved a bug affecting API Platform when a data provider returns a generator, he also improved the documentation concerning this feature. Moreover he added unit tests covering the brand new JSON Schema generator;



Kévin Van Der Stracten did his first bug fix on API Platform, with the help of Antoine Bluchet;



Grégory Copin adapted the NextJS application generator provided with API Platform to use the new version of the popular JavaScript framework;



Mathieu Dewet, in collaboration with Robin Chalas, fixed the implementation of the refreshUser method of the LdapProvider, and fixed some other issues in Symfony ;



Vincent Chalamon drastically improved the security and usability of the access control mechanism provided with API Platform;



Grégoire Hébert added a new feature to API Platform allowing to choose which OpenAPI versions to activate;



Jean-François Thuillier and Morgan Auchedé finalized the new version of API Platform Admin and started writing documentation.



The outcome of this working day: 13 PRs have been merged, 2 issues are open and other topics are under consideration.&nbsp;



At Les-Tilleuls.coop, we encourage and support our cooperators, even the beginners or the most shy, to contribute to the software they use. The Free Software community is based on knowledge sharing, collaboration and exchange. Every contribution, no matter how small, is beneficial and has a lasting effect on the ecosystem. Some reticence may arise, linked to the fear of not feeling legitimate to contribute, but we must keep in mind that we are lucky to have access to a large community of contributors acting for the continuous improvement and reliability of the software we use. Supporting them like this is the best way to thank them for all the time they have already undertaken in this process.

A day at Les-Tilleuls.coop: collective contribution to Free Software

For some time now, we have been implementing a new routine in our SCOP: every two months, the whole team meets up for a whole day dedicated to contributing to the Free tools we use, we develop&#8230; or not! This new initiative comes in addition to what was already allocated to some of our cooperators [&hellip;]

A day at Les-Tilleuls.coop: collective contribution to Free Software | Les-Tilleuls.coop

https://api.les-tilleuls.coop/wp-content/uploads/2021/08/285.jpg

https://secure.gravatar.com/avatar/40dfc350a09c1b2f7391856a676253c3?s=96&d=mm&r=g

tilleuls

What do we do at a General Meeting?

Hello everyone! I&rsquo;m <meta charset="utf-8"><a rel="noopener" href="https://twitter.com/Pandora_angora" target="_blank">Caroline</a>, back-end developer freshly arrived at Les-Tilleuls.coop! Today was my first general assembly (GA) and the first of the year 2019. Here is my feedback on this special day.



<h3>What do we do at a General Meeting?</h3>



Les-Tilleuls.coop being a SCOP (go here to learn more), we make decisions together in a democratic way. Each employee can make proposals or give his or her opinion on different areas. Once a month, all the cooperators meet at the office in Lille to make various decisions related to legal news, the budget or recruitment. Each cooperator has one vote representing one vote, it is not a dictatorship here.



The office is busier than usual. We are from a dozen people to about thirty in some minutes. We take a breakfast together, we discuss then we make a Tetris with the armchairs so that everyone can return in the meeting room.



<figure class="wp-block-image"><img src="https://api.les-tilleuls.coop/wp-content/uploads/2021/08/286.jpg" alt="AG" title="AG"/></figure>



Tetris with chairs.



 



The agenda is established a few days before and sent to each cooperator who can contribute directly. If someone has a proposal for a tool, an idea, you shouldn&rsquo;t hesitate to add it and to present it to everyone during the GM. We discuss the different points, give our opinion and then we vote by a show of hands (for, against, abstention).  



Olivier (our CFO) started this first GM of the year with the balance sheet of the turnover of 2018. It was an opportunity to talk about customer relations, the strong and weak points, to get advice on processes to improve.



An important aspect in the life of our cooperative concerns recruitment. We discuss candidates&rsquo; profiles by email or on Slack, we vote on hiring them together at the GM. During a GM, we can also suggest a candidate and then vote to decide if we dig the lead or not, and what offer we can make. We also review current hires and the marketing strategy for future hires (we&rsquo;re hiring, come on! &lt;3 ).



Then, we present the different prospects, the current demands of the client, what his needs are and we plan which cooperator will be available and the most suitable for each mission. We then vote on all the other proposals concerning the life of the scop, such as the budget for an event or the implementation of a new reform.



It is 12:30, we end the GM with the presentation of the different workshops planned for the afternoon. We take the opportunity to work together on internal projects, on Open Source contributions or to train for conferences. 



At the end of the day, a report of the GM is sent to all and we fix a date for the next monthly GM. We celebrate the end of the GM with a good meal in a nice brewery. A convivial moment to share with the cooperators of the different offices 🙂



<figure class="wp-block-image"><img src="https://api.les-tilleuls.coop/wp-content/uploads/2021/08/287.jpg" alt="TEAM 3B" title="TEAM 3B"/></figure>



We eat a very balanced diet to survive the cold. weather.



<h3>Workshops</h3>



Several groups were formed in the afternoon to work on different internal projects, Open Source projects, preparations for training or upcoming meetups. This afternoon I followed a video-conference training on <meta charset="utf-8"><a rel="noopener" href="https://blackfire.io/" target="_blank">Blackfire</a> given by Christophe Dujarric.



<blockquote class="twitter-tweet" data-lang="fr">Cet après-midi, c’est formation <a href="https://twitter.com/blackfireio?ref_src=twsrc%5Etfw">@blackfireio</a> avec <a href="https://twitter.com/Chris_Dujarric?ref_src=twsrc%5Etfw">@Chris_Dujarric</a> en attendant le meetup <a href="https://twitter.com/afup_hdf?ref_src=twsrc%5Etfw">@afup_hdf</a> de demain <a href="https://twitter.com/hashtag/Masterclass?src=hash&amp;ref_src=twsrc%5Etfw">#Masterclass</a> <a href="https://t.co/N32J6bTQHp">pic.twitter.com/N32J6bTQHp</a>— Les-Tilleuls.coop (@coopTilleuls) <a href="https://twitter.com/coopTilleuls/status/1087362605465985027?ref_src=twsrc%5Etfw">21 janvier 2019</a></blockquote>
<script async="" src="//platform.twitter.com/widgets.js" charset="utf-8"></script>



I then finished my day on the writing workshop for the blog. Another busy day at the cooperative. See you soon!

A day at Les-Tilleuls.coop

Hello everyone! I&rsquo;m Caroline, back-end developer freshly arrived at Les-Tilleuls.coop! Today was my first general assembly (GA) and the first of the year 2019. Here is my feedback on this special day. What do we do at a General Meeting? Les-Tilleuls.coop being a SCOP (go here to learn more), we make decisions together in a [&hellip;]

What's new at Les-Tilleuls.coop ?