Keep this shared space open
Looking after the website also means looking after what people have entrusted to it. A simple routine of backups and checks helps us improve it with confidence.
Before a significant change
Back up the code, SQLite database, uploaded images and configuration. Stop the application during a move so new entries are not saved halfway through the copy. Keep backups outside public folders.
Where a maintainer can find things
- src contains templates and base logic. public contains styles, images and browser scripts.
- deployment contains startup, accounts, translations, applications and guides. The roscaille-v3 folder keeps its name for compatibility and remains part of Alpha.
- dist is the distribution ready to run. npm run build recreates it from source files without replacing data.
- data, or the location in ROSCAILLE_DATA_DIR, holds the database and installation files. html contains exported references and does not replace the server.
A check that looks after everyone
After updating, visit Home, a blog entry and an initiative. Check images, the three languages, links and mobile layout. Sign in, check permissions and confirm earlier applications remain available. You can submit a clearly labelled test application to check the whole journey.
When something looks different
First check the installation folder and whether Node.js restarted. Refreshing the browser can help rule out an old cache. For missing content, check the data path before touching the database. For translation problems, check the original language and Google configuration.
Recovery should keep recent work too
Identify which code version and data backup you have before restoring. Publications and applications received after the backup should not be lost just to restore older code. If everything must move, keep the current state too and ask the maintainer for a consistent copy.
Alpha 1.5.3 · Building on the September 2026 baseline