View Articles

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.

In this video I’ll talk about:

• Tiki installations options
• How to install Git on your computer
• How to pull a Tiki branch from Git without all the history
• How to Upgrade, how to check status, etc.
• Git Workflow for developers
• What is changing for SVN Tiki contributors
• How to create your fork and setup your branch
• How to commit and submit your changes
• How to create a merge request and submit it for approval
• How to keep your branch up-to-date with the rest of the code
• Cherry-Picking (backport)
• Edit your commit message before push

In May 2025, the International Criminal Court lost access to its email system. Not because of a cyberattack or technical failure, but because Microsoft suspended the email account of ICC Chief Prosecutor Karim Khan after the U.S. President imposed sanctions on him. With a single executive order from Washington, an American corporation reached into a European institution based in The Hague and flipped the switch. This isn't a hypothetical scenario. This digital dependency touches everyone – even Europe's most sensitive institutions, designed to protect citizens and uphold justice, operate on American infrastructure that can be shut down instantly.

Review the events of your daily life and you'll feel dizzy. You turn on your computer, check your smartwatch, ask Siri or Alexa to play music, start your car, make a phone call, send an email, calculate a route... Each time, you go through a service, a server, a technology made in the USA. From hardware (Intel, AMD, NVIDIA) to systems (Windows, iOS, Android) to applications (Microsoft 365, Google Workspace, Zoom), the dependency is systemic. And your habits, your life, your information, your photos... everything that goes online is no longer yours or your company's... How did we get here?