roscailleFOUNDATION
EN
EspañolEnglishPortuguês

Website guide

A website we can
keep building.

This guide keeps track of what we have learned while shaping our website. We want anyone who joins us to be able to understand it, care for it and keep building with us. You do not need a technical background: underlined terms lead to our dictionary.

Make room for improvements, keep what matters

An update should bring improvements without losing the publications, images and access that already belong to roscaille. First, check whether you are updating the current installation or setting up a new one.

Before replacing a file

The application root is the folder containing app.cjs and package.json. Confirm that Spaceship uses that folder and make a private backup of its code and data. Keep the cPanel configuration too. The LEEME included with this release provides installation steps for whoever is helping you.

When our website is already running

  1. Temporarily stop the application in cPanel and run the included backup utility. Wait for confirmation that the backup is complete.
  2. Keep data, .env, .htaccess and the environment variables. If ROSCAILLE_DATA_DIR points elsewhere, keep that data folder.
  3. When updating from Alpha 1.0.0, use the update ZIP to replace only changed files. Use the full ZIP to consolidate the application or prepare another installation. Extract either package at the application root, without an extra folder in between.
  4. Keep Node.js 24, app.cjs as the startup file and the correct HTTPS domain in PUBLIC_ORIGIN. This release is already built: installation does not need npm install or a build step.
  5. Restart the application. Check that entries, images and accounts are still there, then open Applications and the Website guide.

When moving to a different server

Set up Node.js 24 and a persistent folder for data. Upload the full package, set PUBLIC_ORIGIN and start app.cjs. To move the website exactly as it is today, you also need the hosting backup. The code package does not contain current private accounts or volunteer applications.

What the package contains

The full package includes code, assets and an initial public snapshot from September 11, 2026. That snapshot is only used when no database exists. Keep the current data instead of replacing it with the initial snapshot. Changes made directly to uploaded images or hosting data stay intact when their data folder is kept.

If we need another look

We can restore the previous code from the backup. Before restoring data, check for applications or publications received since that copy was made. They deserve to be kept too. Correcting an installation does not have to mean starting over.

Alpha 1.5.3 · Building on the September 2026 baseline