Chat messages can now be rewritten by their author only, at any time, with a
"(edited)" marker whose tooltip carries the full date and time down to the
second. The edit is enforced by the SQL filter on user_id, so a message of
someone else answers 404, exactly like a message that does not exist.
Several messages can be pinned at once in the same chat room. Pinning is open
to every member of the room: it is a reading convenience, not a way to take
over someone else's content. A dedicated GET on /chat/pins is required because
the id cursor only reports recent messages, and pinning an old one would
otherwise stay invisible.
The message list is synchronised with two cursors: the id one for new
messages, a timestamp one for rewrites. The server computes that timestamp
before running the query and returns it as-is, in the very frame used by
edited_at, so the client never converts it and cannot drift by a timezone
offset.
Files can now be dropped on the current folder or on any sub-folder card. The
drop zone only reacts to file drags, and the pointer moving from a child
element to another no longer makes the overlay flicker.
A deleted message leaves the pinned list, and its physical file is removed
from the disk as before.
Browsers applied heuristic caching to JSON API responses because no
Cache-Control header was set, serving stale file lists after delete or
upload even with a hard refresh. Force no-store on all /api/cloud/*
responses.
---------
Co-authored-by: xEsiah <[email protected]>
Reviewed-on: #14
Reviewed-by: Esiah <[email protected]>
Co-authored-by: Gitea Actions <-[email protected]>
The unread count compared message ids against COALESCE over a scalar
subquery with no fallback. When a user had never opened a discussion
there was no chat_reads row, so the subquery returned NULL and
`m.id > NULL` was never true: the folder never got a badge even though
messages from others were unread.
Give COALESCE an explicit 0 default so discussions that were never
opened count all of the others' messages as unread.
---------
Co-authored-by: xEsiah <[email protected]>
Reviewed-on: #10
Reviewed-by: Esiah <[email protected]>
Co-authored-by: Gitea Actions <-[email protected]>
- dump the database to ./backups before applying migrations
- run the one-shot migrate service on every deploy instead of relying only on
the api depends_on, so a migration is never skipped
- translate the workflow comments to English
---------
Co-authored-by: xEsiah <[email protected]>
Reviewed-on: #9
Reviewed-by: Esiah <[email protected]>
Co-authored-by: Gitea Actions <-[email protected]>
- chat: salon attache a un dossier, membres = comptes ayant acces au dossier
- securite: suppression du passage automatique admin sur fichiers/dossiers/
corbeille/recherche/galerie/chat ; l'admin n'accede qu'a ses partages
- favoris: tri en tete dans l'explorateur + page dediee (GET /favorites)
- ui: retrait des pastilles Systeme/Public sur la carte dossier
- migration 007_chat : table chat_messages
---------
Co-authored-by: xEsiah <[email protected]>
Reviewed-on: #8
Reviewed-by: Esiah <[email protected]>
Co-authored-by: Gitea Actions <-[email protected]>
/auth/me renvoie desormais has_avatar et avatar_updated_at (LEFT JOIN
user_avatars). Le header affiche l'avatar avec un cache-buster sur
updated_at, et retombe sur les initiales en cas d'absence ou d'echec.
Le profil rafraichit la session apres ajout/retrait de l'avatar pour que
le header se mette a jour immediatement.
---------
Co-authored-by: xEsiah <[email protected]>
Reviewed-on: #6
Reviewed-by: Esiah <[email protected]>
Co-authored-by: Gitea Actions <-[email protected]>
Le refactor a range cli.ts dans src/lib, donc tsc produisait
dist/lib/cli.js alors que Compose, le bin du package et la doc lancent
dist/cli.js : MODULE_NOT_FOUND, le service migrate sortait en 1 et l'API
(depends_on migrate) ne demarrait plus.
cli.ts revient a src/cli.ts, aux cotes de index.ts et admin.ts :
dist/cli.js est de nouveau produit. Imports ajustes en ./lib/...
---------
Co-authored-by: xEsiah <[email protected]>
Reviewed-on: #5
Reviewed-by: Esiah <[email protected]>
Co-authored-by: Gitea Actions <-[email protected]>
- logo embarque dans les e-mails (CID) et gabarit repense en mode sombre
- favicon multi-tailles + icone PNG, logo a gauche du titre (app et auth)
- modale de confirmation animee a la place de window.confirm
- bouton retour et fil d'ariane dans l'explorateur
---------
Co-authored-by: xEsiah <[email protected]>
Reviewed-on: #4
Reviewed-by: Esiah <[email protected]>
Co-authored-by: Gitea Actions <-[email protected]>
- nginx rejoint le reseau externe shared-network pour que le tunnel
Cloudflare le resolue par son nom (cohaise-cloud-nginx).
- real_ip_header CF-Connecting-IP : devient l'IP reelle du
client, sinon limit_req et l'audit comptent l'IP du tunnel.
- X-Forwarded-Proto reprend le schema vu par Cloudflare (https) au lieu de
$scheme (http) : le cookie de session repasse en Secure.
- docs/deployment.md : tunnel Docker via shared-network, deploy.yml sans make check.
Store MariaDB and media data on the host disk via CLOUD_DB_DIR and CLOUD_MEDIA_DIR (default ../db, ../media) instead of Docker named volumes, so they live on the big disk and survive 'down -v'. Drop the host 'make check' from the deploy job: the image builds already run tsc for every workspace, so no Node toolchain is needed on the runner.
Move MariaDB and media data out of /var/lib/docker onto the host disk via CLOUD_DB_DIR and CLOUD_MEDIA_DIR (default ../db, ../media). Only the frontend build output remains a named volume.