Tags: morfredus/ComponentHub
Tags
Add morfUpdate agent components for update management - Introduced AgentConfig for managing agent configuration settings. - Implemented LocalApiServer to handle local API requests for update operations. - Created OperationStore to maintain the state of update operations. - Developed ReleaseValidator to validate release manifests and assets. - Added UpdateEngine to execute update operations based on the agent configuration. - Defined UpdateOperation structure to represent individual update tasks. - Implemented JSON handling for configuration and operation states. - Added error handling and state transitions for update processes. - Included platform-specific installation logic for Windows and Linux.
feat(attachments): 1.8.0 - pieces jointes fichier synchronisees via m… …orfSync Un document peut desormais etre un FICHIER importe (bouton "Importer un fichier") en plus d'un lien externe. Le fichier est copie dans un magasin local adresse par contenu (<data>/attachments/<sha256>) et son binaire voyage entre postes via le magasin de blobs de morfSync : au PUSH, les blobs absents du hub sont televerses ; au PULL, les blobs references mais absents localement sont telecharges et verifies (SHA-256 recalcule a la reception). Liens externes inchanges ; documents anterieurs = liens (retrocompatible). Necessite morfSync 0.6.0 pour les endpoints blob (hub plus ancien : metadonnees synchronisees, binaires simplement ignores). - SHA-256 autonome Qt-free (src/util/sha256.h, verifie contre vecteurs standards) - magasin local (src/domain/attachment_store.h, import + adressage par contenu) - Document enrichi (fichier vs lien), serialisation, referencedBlobs() - HttpClient : PUT/HEAD binaires ; SyncService : passe blob best-effort apres la sync des metadonnees (un accroc blob ne fait jamais echouer la sync) - UI : import de fichier, ouverture d'une copie temporaire nommee, mention "contenu non encore synchronise"
feat(sync): Implement synchronization with HomeServerHub - Added SyncService for managing synchronization between ComponentHub and HomeServerHub. - Introduced SyncConfig and SyncOutcome structures for configuration and results handling. - Implemented HTTP client for making requests to the HomeServerHub API. - Added synchronization metadata structures (SyncMeta, SyncRecord) for tracking entity states. - Created UI components for synchronization settings, including options for local-only mode and auto-start. - Added documentation for synchronization features and configuration. - Implemented persistent storage of synchronization preferences using QSettings. - Enhanced error handling and user feedback during synchronization processes.
PreviousNext