-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to generate config #11
Comments
Lovely thanks I was able to generate .yml and use to join selfhosted netowrk and create a new user for loggin in though it still shows 1 gb space in remote storage Shoudnt it be the size of my disk in vps where I am running the any-sync ? Thanks |
Hey @bolavefasfas, the file limit for identities should be defined in the coordinator-node config. It's 1GB by default, and there is no automatic logic like "get the whole disk size as a limit." We will update our images to provide larger file limits for self-hosters by default. |
can we make it as a env variable in docker-compose.yml |
@fb929 your link is broken, because of new file structure. Did you mean that lines that could be changed in order to increase the limit? https://github.com/anyproto/any-sync-dockercompose/blob/ddf4f9b9cc6d3759babad34fda47f0724e834f9d/.env.common#L45C1-L47C61 |
this is "spaces" limits the files limit is here: any-sync-dockercompose/.env.common Line 54 in ddf4f9b
|
Have you read a contributing guide?
Current Behavior
Output
Expected Behavior
It should be able to generate config right ?
All container started
https://github.com/anyproto/any-sync-dockercompose?tab=readme-ov-file#usage
Storage and etc folder were also created
Steps To Reproduce
git clone https://github.com/anyproto/any-sync-dockercompose
make start
docker compose exec mongo-1 mongosh coordinator
db.nodeConf.find().sort( { _id: -1 } ).limit(1)
Environment
Anything else?
I tried to host it in multiple diffrent x86 devices
A photo guide will be helpful.
The text was updated successfully, but these errors were encountered: