View Articles

Vos emails et vos réunions concentrent l'essentiel de vos données sensibles : contrats, devis, échanges stratégiques, fichiers clients. C'est aussi là que se niche votre plus grande exposition, et paradoxalement le chantier le plus rentable à reprendre en main. Dans ce nouveau volet de notre série sur la souveraineté numérique, nous passons de la théorie à la pratique.

Car le constat est sans appel. Chaque courriel, chaque réunion qui transite par un service américain ou tenue sur une plateforme étrangère relève d'une juridiction qui n'est pas la vôtre. Pourtant, reprendre la main n'a rien d'un chantier insurmontable. Voici, étape par étape, comment retrouver la maîtrise de votre communication, du geste simple à la portée de tous jusqu'aux solutions qui gardent réellement vos données sous contrôle.

Since our first update in February, the shift toward European digital sovereignty has accelerated faster than in the previous five years. While EU powers are migrating millions of workstations to Linux and Brussels targets opaque recommendation algorithms, the push for sovereign tools is no longer a theory—it is a massive public sector transition to assume European digital sovereignty. Yet, as governments pivot, data vulnerabilities are peaking: three accounts are compromised every second, and major national hacks are exposing tens of millions, making Europe a primary target for global cyber-threats. Governments are moving, which is progress. But where does that leave those without a ministerial budget?

This fourth article explores the rapid evolution of the European regulatory landscape during the past four months and maps out the escalating threats of 2026. Most importantly, it provides a concrete action checklist—categorized by time and effort—designed for professionals who need to protect their data and their clients’ trust without a dedicated IT department. These are simple, scalable measures you can implement right now, within your means and at your own scale.

This guide explains how to set up a Debian 13 server with the Virtualmin hosting control panel and deploy a Tiki Wiki CMS solution using exclusively open-source software.

Built with security and digital sovereignty in mind, you will learn how to configure essential server components (ports, MariaDB, PHP versions), install Webmin and Virtualmin, secure your server with SSL certificates, and publish your Tiki Wiki site efficiently.
This tutorial is designed for intermediate system administrators and full-stack developers seeking a reliable, scalable, and sovereignty-friendly approach to deploying modern web applications.

What do you actually depend on? Which devices, servers and cloud services are outside your control, and under which jurisdiction do they operate? Do you know what your staff use beyond the officially approved tools? This third article in our series on digital sovereignty provides a practical method to audit your dependencies, assess your exposure and identify the first building blocks to reclaim.

Independent alternatives exist, they are mature and the first steps are within reach without disrupting your operations. From network hardware to servers, from hosting to cybersecurity, we detail how to lay a solid infrastructure foundation, step by step, without paralysing your activity. After storming the Bastille, you need to lay the foundations of your citadel.

The Tiki 27+ Build System marks a significant evolution in the way Tiki Wiki CMS Groupware handles its development and deployment processes. This article aims to guide you through the essential steps and provide solutions, even as the process continues to stabilize.

Introduced in Tiki 27 and refined in subsequent versions, this build system brings numerous enhancements aimed at improving efficiency, consistency, and ease of maintenance for developers and users alike. However, it requires power users and administrators to familiarize themselves with the new installation method from Gitlab (Version Control System). This guide details the updated Tiki system build and setup procedure leveraging nvm for Node version management and npm for dependency handling, including troubleshooting for frequent installation and runtime issues.

Europe has the laws, the labels, and the rhetoric for digital sovereignty. What it lacks is consistency. Between legislation passed and contracts signed, a stubborn gap undermines the credibility of the whole project. From government procurement to school IT, tangible progress coexists with concessions that are hard to defend. Most troubling: it is in classrooms, year after year, that an addiction to closed ecosystems is being quietly built on the taxpayer's dime.

We examine what works, what doesn't, and why coherence remains the weakest link in an otherwise ambitious strategy. Sovereign alternatives exist and are proven. The only missing ingredient is the political will to scale them, from the classroom to the data-center.

If you're installing Tiki Wiki 27, Tiki Wiki 29, or any version above from the git repository, you'll need to use the Tiki Build System that was recently introduced. When running setup.sh option "b" (build), you may encounter build failures due to memory allocation issues. This is a common problem that occurs when Node.js runs out of allocated memory while compiling JavaScript assets. Here’s the troubleshooting process we use, and how you can apply it yourself.