Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
E
eScriptorium
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 88
    • Issues 88
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • scripta
  • eScriptorium
  • Issues
  • #11

Closed
Open
Opened Jan 24, 2019 by Robin Tissot@rtissotMaintainer

Document locking

If a user opens a document already opened by someone else there is a danger that some data might be erased.

This is harder to define than it sounds because some of the document states are updated through the websocket live, we might be able to improve on that to have some form collaborative editing, but it's also possible it would be too much work for too little reward.

Weirdly enough no existing django package use a regular file lock, but I have a module ready from another project if we go that way.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: scripta/escriptorium#11