php occ maintenance:update:htaccess` should be sufficient.
### OnlyOffice file size issues
OnlyOffice restricts the maximum size of files that can be edited live by the server. It can be increased in the server's configuration (`default.json` in the `onlyoffice_config` docker volume, full path is `/var/lib/docker/volumes/onlyoffice_config/_data/default.json`), through the `FileConverter.converter.maxDownloadBytes` and `FileConverter.inputLimits.[type=your_file_type].uncompressed` fields.
We have increased the maximum size for PPTX and related files to 512MB, as well as XSLX and related to 300MB.
# SSO - KeyCLIC
The [SSO](https://en.wikipedia.org/wiki/Single_sign-on) (or Single-Sign On) is handled by a [Keycloak](https://www.keycloak.org/) instance hosted on the server. The admin panel is available at [https://clic.epfl.ch/keyclic](https://clic.epfl.ch/keyclic) and users can manage their profile at [https://clic.epfl.ch/me](https://clic.epfl.ch/me).
For now, each user has a `nextcloud_id` attribute, to remain compatible with accounts that were created directly on Nextcloud. New users should have their username as `nextcloud_id`, with the format `{name}.{surname}`. When there will be no remaining users with the `nextcloud_id` different than their `username`, you can update Nextcloud to use the username (`preferred_username`) and get rid of the `nextcloud_id` field.
## Adding new users
Go to the KeyCLIC admin console here: [KeyCLIC Users](https://clic.epfl.ch/keyclic/admin/master/console/#/master/users)
[](https://clic.epfl.ch/wiclic/uploads/images/gallery/2025-04/image-1745950979355.png)
Click add user and fill in the following information:
- **Required user actions**: Update Password, Verify Email
- **Email verified**: leave this OFF
- **Username**: `name.surname`
- **Email**: EPFL email address if available (may be non EPFL user address for a user who is not at EPFL)
- **First Name** & **Last Name**: you can fill in the user's name, or leave it for them to fill in later
- **Nextcloud ID**: `name.surname`, same as username
- **Groups**: select only the relevant groups for the user, for example members of a commission should only be in their commission group.
Optionally, once the user is created, you can set their password to a temporary value (such as their email address). Leave the "Temporary" option on when creating the password, and ensure the options requiring them to verify their email and update their password are active.
Otherwise, they can set their password by selecting the "Forgot password" option on the KeyCLIC login page.
# Clicketing
Clicketing registration management system, created by CLIC, for CLIC.
It is available on [https://clic.epfl.ch/clicketing](https://clic.epfl.ch/clicketing), and its codebase on the [GitHub repository](https://github.com/clicepfl/clicketing).
TODO
Possible improvments:
- [Camipro](https://clic.epfl.ch/wiclic/books/it/page/camipro-api)
# Utility
Various small services and projects for CLIC that are not crucial, but come in handy.
## QR Bill Generator
A handy QR Bill Generator that can be used to generate personnalized bills for event particiapnts. For example, this is used for the [Faculty Diner](https://clic.epfl.ch/wiclic/books/evenementiel/page/souper-de-faculte) and [IC Boost Day](https://clic.epfl.ch/wiclic/books/evenementiel/page/ic-boost-day).
It is hosted at [http://clic.epfl.ch/qrbill-generator](http://clic.epfl.ch/qrbill-generator) and the source code can be found on the [repository](https://github.com/clicepfl/qrbill-generator).
## Mail Sender
A simple mail sender that supports Liquid templates and ICS attachements. It was mainly created to use from Directus flows (that do not support ICS attachements easily). The source code can be found on the [repository](https://github.com/clicepfl/mail-sender).
## Crab CLIC
A self hosted and themed instance of crab.fit. The source code can be found on the [repository](https://github.com/clicepfl/crab.fit).
## KeyCLIC Theme
A simple theming for our self hosted instance of Keycloak. The source code can be found on the [repository](https://github.com/clicepfl/keyclic-theme).
# Roboclic
Roboclic is CLIC's Telegram bot. It is written in Rust and hosted on server.
More information on the [repository](https://github.com/clicepfl/roboclic-v2/#readme).
# IC Plays Pokemon
A collaborative game derived from the concept of [Twitch Plays Pokemon](https://en.wikipedia.org/wiki/Twitch_Plays_Pok%C3%A9mon) (but without the Twitch part). It comes with an interface for players to select a command, then the backend plays the majority command each cycle in the actual Pokemon game. The source code can be found here [IC Plays Pokemon](https://github.com/clicepfl/ic-plays-pokemon).
# Overclicked
Overclicked is a web application created by CLIC, used for tracking and managing orders at student-organized events. It provides simple interfaces for event staff in various roles (at the register, in the preparation area, etc) to monitor incoming orders and update their status in real time.
It was mainly used for Subsonic, to manage Croque-Monsieur orders in real time.
The source code can be found here: [Overclicked](https://github.com/clicepfl/overclicked)
# Clicketing V1 (outdated)
Clicketing registration management system, created by CLIC, for CLIC.
> Important Note
>
> This page is about the first version of Clicketing, which was last used in Spring 2024 and has now been replaced by an entirely new version. You can find the codebase for this older version on the [GitHub repository](https://github.com/clicepfl/clicketing-archived).
>
> See more about the newest version of Clicketing here : [Clicketing](https://clic.epfl.ch/wiclic/books/it/page/clicketing).
[](https://clic.epfl.ch/bookstack/uploads/images/gallery/2023-11/image-1700494660754.png)
#### How it works
Before an event, Clicketing sends an e-mail to each participant containing a QR Code to facilitate entry. At the start of the event, everyone presents themselves at reception with their QR Code, which staff can scan to confirm registration and attendance.
#### Login
The admin password is stored on the [Vaultwarden](https://clic.epfl.ch/armoire).
#### Utilisation
The service allows you to manage registrations by event. On the [main page](https://clic.epfl.ch/clicketing), you can create and edit events. Each event is assigned a name, a date and an e-mail template.
The mail can be sent to all participants exactly once, using the `Send mail` button. To check the email, you can send it to a specific person, by entering their address in the `Preview email recipient` field and pressing `Send preview email`. This email will contain a random QR Code, and is only to be used to view the visual rendering of the template.
To add participants, you need to use the HTTP API. The ideal way is to create a script on the registration sheet, in order to generate a JSON. For more information, see dev's documentation on the [repository](https://github.com/clicepfl/clicketing).
### Possible improvements
- Use camipro readers instead of QR Code (see [Camipro API](https://clic.epfl.ch/bookstack/books/it/page/camipro-api)).
- Security: Sessions with expiry date.
- Additional data to be inserted in e-mail (name, date, menu, etc.).
- Automatic insertion of participants when registering on form.
- Insert/edit/archive participants (indicate payment, etc.).
- Automatic sending of email upon registration/payment.
# Save the Date
todo update ça
# GA Voting system
To vote at the general assembly of the association, we use Telegram polls.
## Setup
1. Create the GA group. This group should initially only contain the clic-admin user.
2. Create the polls group. Same as above, except that no one else should be added afterwards.
3. On the polls group, prepare all the polls for the GA.
4. Generate the QR Code for the GA group, and place it at the beginning of the GA slides and on each slide where a vote will occur.
## During the GA
The scrutators needs to count the number of voters, and update that number whenever one enters/exits the room.
When a vote starts, the corresponding poll should be forwarded from the polls group to the GA group, and closed when the timer stops. The members holding a procuration will raise their hands to count this second voice. Scrutators must count the number of procurations, sum it up with the poll result and check that it matches the number of voters.
# Rust Workshop
The Rust Workshop is an event organized by the CLIC IT Team to introduce participants to the [Rust Programming Language](https://www.rust-lang.org/). It consist of an overview of the basic syntax of Rust, as well as an explanation of lifetimes, the borrow checker, and various concepts unique to Rust. It is designed to be accessible to any individual who has experience programming in another language, such as Scala or C. No prior experience in Rust is required.
## Resources
The workshop resources include the [slides](https://clic.epfl.ch/nextcloud/s/doFPoPbaPkXnNY3), the [code examples](https://github.com/clicepfl/rust-workshop) that were shown with live explanations, and the [exercises](https://github.com/clicepfl/rust-workshop-exercises), which can ideally be put in individual [playgrounds](https://play.rust-lang.org/) to be more conveniently shared with participants.
## Organisation
### Content
The content of the workshop must be considered and created ahead of time. This includes slides, examples and exercises, as well as any extra material like a cheatsheet. Make sure to think about the time the workshop might take and what sections could be cut if you are running over on time.
### Mediacom
An RITM must be created with Mediacom ahead of time to request a room for the event to take place (make sure to ask for enough spots for the target number of participants, as well as request a projector). The keys for the room lights and the guest camipro to open doors after hours can be picked up on the day.
### Communication
Create a registration form and send out communication (social media, posters) at least a week before the day.
### Setup
- Print cheatsheets
- Bring CLIC glasses
- Buy snacks
- Setup the tables
## Past Editions
### 2025
The workshop was given for the first time to a group of CLIC comittee & commission members and friends, as a first test. There were under 10 participants, so the workshop was given at the CLIC Office from about 13h to 18h, with the projector and tables moved to make space. Depending on the budget, snacks or pizzas could be purchased for the event.
### 2026
For the second edition there were about 35 participants and was given in in CO 016. It lasted around 4h30.
# EPFL Network
On the EPFL network, you are assigned a static IPv6 and a domain accessible for the other user of the network. It changes each time you reconnect. You can get those value [here](https://network.epfl.ch/epnet/dyndns.pl).
This is quite useful to setup temporary servers (e.g. for events) like it was done for the first version of [Overclicked](https://clic.epfl.ch/wiclic/books/it/page/overclicked), where the server was setup on one of the computer used as a register.
# Camipro API
CLIC has obtained access to the API used to identify the owner of a camipro. The API is only available from the EPFL network (either directly or via VPN) and thus not accessible from the server. It may be added to Clicketing's workflow if and only if the key was to be exposed to the client scanning the participants.
Route documentation is available [here](https://mycamipro.epfl.ch/ws/v2/#/Card/get_card__cardid__user). Note: authentication fails from the page or using the displayed command; instead of the header `Authorization`, pass the argument `-u clic` and enter the key.
**For legal reasons**, use of the API is limited to obtaining temporary information. This data **must not be stored** in a database, or any other form of persistent storage. It may only be used to search for a match in a pre-existing database, such as an event registration list.