![]() Apparently only the changed files are copied locally, while all the others are open RO on the server. When another client wants to fetch the changes they "sync" as well and those files are reloaded. Several persons can work on the same project on different sections, when someone "syncs" their changes to the server the file they worked on are copied to the server share. Revit collaboration uses a client/server approach: a project, which is composed by many files, is opened RO on the server and cloned locally on the client to be worked on. nextcloud_admin_user.txt services: db: image: mariadb:10.5 command: -transaction-isolation=READ-COMMITTED -binlog-format=ROW restart: always volumes: - db:/var/lib/mysql environment: - MARIADB_AUTO_UPGRADE=1 - MARIADB_DISABLE_UPGRADE_BACKUP=1 - MYSQL_DATABASE=nextcloud - MYSQL_ROOT_PASSWORD_FILE=/run/secrets/mysql_root_password - MYSQL_USER=nextcloud - MYSQL_PASSWORD_FILE=/run/secrets/mysql_password healthcheck: test: "mysqladmin ping -h localhost -u$$)" interval: 10s timeout: 5s retries: 100 start_period: 40s secrets: - mysql_root_password - mysql_password redis: image: redis:alpine restart: always app: image: nextcloud:apache restart: always volumes: - nextcloud:/var/- LETSENCRYPT_HOST= - MYSQL_HOST=db - REDIS_HOST=redis - MYSQL_DATABASE=nextcloud - MYSQL_PASSWORD_FILE=/run/secrets/mysql_password - MYSQL_USER=nextcloud - NEXTCLOUD_ADMIN_USER_FILE=/run/secrets/nextcloud_admin_user - NEXTCLOUD_ADMIN_PASSWORD_FILE=/run/secrets/nextcloud_admin_password secrets: - mysql_root_password - mysql_password - nextcloud_admin_user - nextcloud_admin_password depends_on: db: condition: service_healthy redis: condition: service_started networks: - proxy-tier - default cron: image: nextcloud:apache restart: always volumes: - nextcloud:/var/restart: always ports: - 80:80 - 443:443 labels: _nginx_proxy_companion.nginx_proxy: "true" volumes: - certs:/etc/nginx/certs:ro - vhost.d:/etc/nginx/vhost.d - html:/usr/share/nginx/html # - /var/run/docker.sock:/tmp/docker.sock:ro - /run/user/1000/podman/podman.sock:/tmp/docker.sock:ro networks: - proxy-tier letsencrypt-companion: image: nginxproxy/acme-companion restart: always volumes: - certs:/etc/nginx/certs - acme:/etc/acme.sh - vhost.d:/etc/nginx/vhost.d - html:/usr/share/nginx/html # - /var/run/docker.sock:/var/run/docker.sock:ro - /run/user/1000/podman/podman.sock:/var/run/docker.sock:ro networks: - proxy-tier depends_on: - proxy volumes: db: nextcloud: certs: acme: vhost.We need a customization to the Nextcloud desktop client to make it work with Autodesk Revit. nextcloud_admin_password.txt nextcloud_admin_user: file. mysql_password.txt nextcloud_admin_password: file. mysql_root_password.txt mysql_password: file. Version: '3' secrets: mysql_root_password: file. I don't know if it's properly configured. On the server, edit config.php to add the line 'bulkupload.enabled' => false, On the client, disable any upload speed limits Last Nextcloud client logs say: 15:09:44:424 : Transaction commit "post stale entry removal" and starting new transaction My question: Is there any good advice/ good practice to follow when trying to sync local folders (~60GB) to the server for the first time? But since my last HDD crash, I had to rebuild everything and install this new Nextcloud client AppImage (didn't use the AppImage before). It is really annoying seems it used to work perfectly in the past. it detects some conflicts between the local and remote files, while this is the first synchronization (with nothing on the server at the beginning) it gets stuck in the step "Checking for changes in local " I am trying to sync my local files to the server but there's ALWAYS a problem with the client: ![]() Everything seems to work fine except the client on Linux (Linux Mint). I installed Nextcloud on my home server in Docker containers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |