Ctrl K
ComunidadGuías…

Ayuda y problemas de any-sync-dockercompose

Pregunta a la comunidad o invita a KiBot con contexto del repositorio.

Publicar un problema

No publiques contraseñas, tokens ni claves privadas. HostingByte aplica una redacción básica de secretos evidentes antes de guardar el texto.

Problemas en HostingByte

Todavía no hay problemas publicados.

Issues abiertas upstream

#203 Speed issue when Using "mnt" storage to keep all data · 1 comentarios#202 Treat configuration as version controlled contract. · 0 comentarios#197 Provider-agonostic S3 store config · 0 comentarios#194 Add Any-Sync Node to the official TrueNAS SCALE App Catalog · 0 comentarios#181 Simplify self-host deployment to improve adoption in UI-based Docker environments · 5 comentarios#151 Instructions to run in rootless containers · 13 comentarios#166 [NoCredentialProviders: no valid providers in chain] when using custom AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY · 4 comentarios#177 Provide a "bundled" image for easier setup · 2 comentarios#175 Maybe a reason why your self-hosted sync is deadly slow · 0 comentarios#152 I accidentally uploaded a large file, approximately 1.5 GB in size, and now my cloud storage space is insufficient. How can I delete it in Selfhost Server · 5 comentarios#171 Ambiguous Configuration Parameters May Cause Synchronization Failure · 2 comentarios#173 Would you consider switching redis to valkey, or staying with redis <= 7.2? · 1 comentarios#172 Problem when bringing up v6.4.0 · 5 comentarios#148 Images stuck at Syncing · 4 comentarios#164 Instructions for Portainer · 10 comentarios#153 When the code block's language type is synchronized to another device during the synchronization process, it will be displayed as plain text. · 1 comentarios#146 Pull access denied for anytype/* images despite successful login · 10 comentarios