From Pirate Party Belgium
Revision as of 08:13, 11 June 2022 by Ilja (talk | contribs) (Spam)
Jump to: navigation, search
ITSquad Toicon-icon-avocado-build.svg
Topics Pirate Party
Start date Sun 20 May 2012
Contact it +@+
or meet us at our Pirate Lab
Status In progress


The ITSquad takes care of the IT-infrastructure of the pirate party. Contact if you want to do an IT-project, need an email address, have requests for a Crew, would like to add a feature to the site, etc.

We can also help with finding, and sometimes providing, tools and services whose values are in line with the values of the Pirateparty. Take a look on our Pirates Selection page for more information.


Networking4All (registrar) 54,75€ Yearly 10,95€ Yearly 10,95€ Yearly Yearly 10,95€ Yearly Yearly 10,95€ Yearly 10,95€ Yearly
Infomaniak (hosting provider)
Mailboxes and old mailing lists 120,00€ Yearly
Hetzner (hosting provider) 431,64€ Yearly
Mediawiki webserver since October 2019 3,01€ Monthly
Wordpress websites (en,fr,nl) since March 2020 3,01€ Monthly
Mastodon server (with 125Go volume) since October 2019 11,98€ Monthly
Mumble server since March 2020 3,01€ Monthly
Liège yunohost server since September 2018 3,01€ Monthly
parley yunohost server since November 2018 3,01€ Monthly
Monitoring server since January 2020 3,01€ Monthly
Storage box (500Go) since September 2019 5,93€ Monthly
TOTAL (if nothing changes) 606,39€ Yearly


Administration Docs


To manage our servers in an automated way:


To maintain a decentralized and libre social-network

See the Mastodon page


Parley is a place where we provide simple services open for everyone. All are free software.


Upgrading can be done from the admin interface or from the cli over ssh. Before updating applications, make a backup. Backups will be created automatically during upgrade, but if you do them manually, you can check that they haven't failed. When doing risky upgrades, please take a snapshot from the Hetzner admin console. An example of a risky upgrade is for migrations like Debian Stretch to Debian Buster.

Landing page

The landing page is a simple HTML page with css and javascript (but has graceful degradation for those who want to disable javascript). The files can be found on our git repo. Updates should be pushed to there. More information can be found in the

The files for the webapp-application are stored on the Parley server in /var/www/my_webapp__2/. You can find a systemlink to the nginx configuration and to a daily cronjob file. The files of the site themselves are stored in the www folder. It uses git, so updating is cd /var/www/my_webapp__2/www; git pull.

There is also an sftp connection (but can probably be removed since updating happens using git and the nginx and cronjob files can't be changed through sftp).

You can update the website on the server and then git add <changed-files>; git commit; git push, or you can make the changes to the repo and then wait for the daily job to do it's work.


When updating Jirafeau the config file gets overwritten. There's an issue, but it doesn't seem like something that will be fixed soon . Make sure you test before and after the upgrade if everything is still as it should be.

  • Settings are stored in /var/www/jirafeau/lib/config.local.php. The settings from before the upgrade are stored in /var/www/jirafeau/lib/config.original.php.
    • organisation: 'Parley'
    • preview: false
    • admin_http_auth_user: <your-account?>
      • If you're the one who mostly maintains this, you can add yourself. It's the username for the ynh user-interface. Another option is to use a shared password and set that in admin_password
    • availabilities:
      • the maximum is a month
    • availability_default: 'week'
    • maximal_upload_size: 2000
    • store_uploader_ip: false

Also note that we've added a file /home/ as a filesystem so we can limit the total uploads (to 2.7 GiB). See this blog post and/or comment on the Jirafeau issue tracker on how it's set up.

When removing Jirafeau the filesystem should be removed manually, but don't forget to also change /etc/fstab otherwise the server may not boot anymore! (See the blogpost to know what was done so you can remove safely, best is to make a take a snapshot from the Hetzner admin console beforehand so it can be put back if something fails.)


If we get too much spam from a specific domain or address, it's possible to block it in config files. Note that we'll be overwriting files with this approach, which means Yunohost wont provide updates or otherwise manage this file any more (I made an issue for it ). It may be still be interesting to use this approach as a temporary solution.

First create or change the access file, nano /etc/postfix/access, with the following content (replace "" with the address to block). REJECT

Only using a domain should also work to block a whole domain. To block multiple addresses/domains, add multiple lines.

Then we change nano /etc/postfix/ Look for smtpd_sender_restrictions and add the line hash:/etc/postfix/access,, so it looks like

smtpd_sender_restrictions =

Then run the following commands

postmap hash:/etc/postfix/access
systemctl restart postfix

Check that postfix is running via the ynh admin webinterface or via the following command

systemctl status postfix

The ynh diagnostics will see the file /etc/postfix/ has changed. Run the diagnostics, see that this is indeed a problem and ignore it. You can do it from the ynh admin webinterface, or via command line

yunohost diagnosis run
yunohost diagnosis show --issues
yunohost diagnosis ignore --filter regenconf

To roll this change back, you can unignore the diagnostic, run it, run the command to fix the file (diagnostic will tell you this), restart postfix and rm /etc/postfix/access.


We try to promote and use yunohost because it's a good server OS for self hosting. Crews who want to administer their own services can get a ynh server. We can provide the service to set everything up, teach some basics and provide support in case of trouble. An explanation on how and why can be found on this blogpost.

Setting up an instance

If a crewmember is interested in running their server from home, an option is an internet cube, but typically we'll use a vps. To set up a vps:

  • See for an example
  • At least one person of the crew will be admin and contact for us. Make sure we know who that is.
  • Log in to Hetzner > cloud > Default > make a new server > install Debian and run the yunohost installer for Debian
  • Run the post-install and add a subdomain to ynh and set up the DNS records. The easiest is to set A and AAAA records for the and a CNAME for * Make sure to set up the other DNS records as well (CAA, TXT...)
  • Add reverse DNS: Log in to hetzner > cloud > Default > Choose correct server > Networking > Under Primary IPS you can see the reverse DNS. Set it for both ipv4 and ipv6
  • Run the diagnostics from the admin interface and set everything up correctly

Things to know for the admin(s)

  • Please keep the server updatet
  • If there are problems, contact us via chat or mail. We're here to help, make use of it
  • Keep an eye on resources
  • There's a good chance that mails will be blacklisted by default by MS and Google. What you can do is "warm up" your domain. Send mails to people who use outlook and gmail accounts and make sure they reply. Or have them send to you. Basically, you want MS and Google to see 'healthy' traffic form your domain/ip.
  • Total cost to ppbe is €X/month and ppbe pays for this. If people want to give some monetary support for it, they can donate to ppbe whatever amount they see fit (pay-what-you-want). It's also possible to donate to the yunohost project.
  • Try to give a short tour of the admin and user interface, so they know what they can do and how



Meeting Date Venue
Toicon-icon-avocado-discuss.svg Mastodon migration to Glitch-soc Sun 1 September 2019, 10:00am Fred's place
1348 Louvain-la-Neuve
Toicon-icon-avocado-discuss.svg Yunohost : Let's decentralise the crews! Sun 24 June 2018, 10:00am tierce's place – 30 rue Achille Bauduin
1300 Limal
Toicon-icon-avocado-discuss.svg Make the PPBe GDPR-compliant Sun 27 May 2018, 10:00am tierce's place – 30 rue Achille Bauduin
1300 Limal
Toicon-icon-avocado-discuss.svg New website online meeting Wed 25 April 2018, 9:00pm Online
Toicon-icon-avocado-discuss.svg New website Sat 21 April 2018, 2:00pm Expression – Koning Albertplein 14
2800 Mechelen
Toicon-icon-avocado-discuss.svg Updating the web site/slogan: let us tell a story Sat 9 December 2017, 2:00pm Expression – Koning Albertplein 14
2800 Mechelen
Toicon-icon-avocado-discuss.svg Mastodon upgrade and Mails structure Wed 1 November 2017, 10:00am tierce's place – 30 rue Achille Bauduin
1300 Limal
Toicon-icon-avocado-discuss.svg IT Squad Meeting Sun 13 August 2017, 12:00pm tierce's place – 30 rue Achille Bauduin
1300 Limal
Toicon-icon-avocado-discuss.svg Mails Follow up Sun 2 July 2017, 10:00am tierce's place – 30 rue Achille Bauduin
1300 Limal
Toicon-icon-avocado-discuss.svg Setting up our Mail Infrastructure Sun 4 June 2017, 10:00am tierce's place – 30 rue Achille Bauduin
1300 Limal

Show moarr meetings!Add a new meeting
Export for iCalendar