Filenode Default Limit does not seem to be applied

[otozyon]

Describe the bug

When using any-sync-dockercompose there's an option to set the default storage limit via an environment variable. When adding the same environment variable to the aio docker compose file the storage limit does not seem to change. It stays at 1TB.

To Reproduce

Steps to reproduce the behavior:

1. Add ANY_SYNC_FILENODE_DEFAULT_LIMIT environment variable to docker compose file
2. Restart everything
3. Check remote storage in space settings

Expected behavior

The storage limit changes.

Actual behavior

The storage limit did not change.

Environment

• Deployment: AIO container
• Version/tag: 1.2.1-2025-12-10
• OS/Arch: Debian 6.1.106-3 (2024-08-26) x86_64 GNU/Linux

[grishy]

Hi, this is because I don't support ANY_SYNC_FILENODE_DEFAULT_LIMIT, only environment variables described in the README file. So this is not a bug, but is currently expected.
Check that we have only ANY_SYNC_BUNDLE_.* vars.

Can you describe your case, why do you use it?

[otozyon]

Thanks for your reply and sorry I filed it as a bug.

I'm part of a non-profit organisation and we're currently evaluating Anytype as a replacemtent for our wiki, chat and file hosting tools and to give us some low level team management capabilities (tasks, projects etc.). There's probably going be about 30-40 people using it. We're looking into selfhosting Anytype because we can't afford to pay for Anytype memberships. The same goes for block storage. We can't afford loads of it because we wouldn't be able to pay for it. That's why we would like to limit the amount of storage each user can occupy.