Comments

  • Similar file path to S3 from multiple Workspaces
    Thank you. I will look into this further.
  • Similar file path to S3 from multiple Workspaces
    Precisely.
    The UNC path is being used.

    Is there a way to make the UNC paths match each other? On our local system, the root of the server or .local is used at the beginning of the UNC path. Cloudberry prevents us from using a universal location? Is there a way to change the UNC root in cloudberry?
  • Similar file path to S3 from multiple Workspaces
    I wish it were that simple. The basic use of the file explorer works as you have said.
    Unfortunately it seems that there is a difference in the actual file location based on the user. I am using the exact same access keys and secret keys. But the users are creating something strange, the root folder seems to be different, and this comes down to Cloudberry, and how it handles the mounting of the S3 drive (I think).

    More specific use:
    We are trying to sync Revit files. The Central Revit file exists on the server (s3) and then makes a local copy of each file once a user opens it. Then Revit records the file location (the file on the server), so that when a local user saves, the file syncs and updates the central model. This allows multiple users to work on the save file (but not save at the same time - a busy error is given if both access the file simultaneously).

    Anyway, here is a screenshot of the path from the Central file, when the error occurs.
    Attachment
    file system conflict (79K)