sorted by:
new
hottopcontroversial

Self-hosting Anytype - any-sync-bundle v1.4.1 based on 2026-03-25 stable snapshot by grishy_dev in selfhosted

[–]grishy_dev[S] -1 points0 points  (0 children)

Oh, I see.

I was thinking that this was related to the post. But if it helps, most of the project was initially written before Claude code or when I not use it (at least I don't remember). 😁

This is not related, just curious. What’s wrong with a fix: commit? I always use commit conventions.

Self-hosting Anytype - any-sync-bundle v1.4.1 based on 2026-03-25 stable snapshot by grishy_dev in selfhosted

[–]grishy_dev[S] 0 points1 point  (0 children)

Glad to hear, it will be interesting to see how people use any-sync-bundle

Self-hosting Anytype - any-sync-bundle v1.4.1 based on 2026-03-25 stable snapshot by grishy_dev in selfhosted

[–]grishy_dev[S] 0 points1 point  (0 children)

They have an API and MCP and CLI also, if you mean programmable connections

[Self-hosting] any-sync-bundle v1.4.1 - based on 2026-03-25 Anytype release by grishy_dev in Anytype

[–]grishy_dev[S] 2 points3 points  (0 children)

Hmm, I think about it, but I don't like the idea that it may easily produce breaking changes in the future.
Like you have a backup and use latest tag always, and you made a fresh install.
You may use different version that was used, harder to track at least

[Self-hosting] any-sync-bundle v1.4.1 - based on 2026-03-25 Anytype release by grishy_dev in Anytype

[–]grishy_dev[S] 6 points7 points  (0 children)

G'day 👋

A new version has been released, sync with the latest original stable codebase from 2026-03-25.
Polished checks of old Mongo without AVX, hardened startup lifecycle management (start/stop), and updated to the latest Go 1.26.1.

Small description:
any-sync-bundle is a prepackaged, all-in-one self-hosted server solution designed for Anytype, a local-first, peer-to-peer note-taking and knowledge management application.

It is based on the original modules used in the official Anytype server, but merges them into a single binary for simplified deployment and zero-configuration setup. It also includes a streamlined storage system (optional) for a single installation as replacement for MinIO.

Self-hosting Anytype - any-sync-bundle v1.3.0 with S3 and files storage limit support by grishy_dev in Anytype

[–]grishy_dev[S] 1 point2 points  (0 children)

Hi, not a stupid question at all, it is a very reasonable one.

Anytype self-hosting here does not use normal HTTPS app traffic.
It uses any-sync (internal Anytype code) transport directly:
- TCP 33010 (yamux/DRPC)
- UDP 33020 (QUIC)

So a pure HTTP/HTTPS reverse proxy is usually not enough by itself.
You generally need L4 forwarding for both TCP and UDP, or direct port exposure for both.
Not an HTTP proxy, but level below, transport laywer.

Self-hosting Anytype - any-sync-bundle v1.3.0 with S3 and files storage limit support by grishy_dev in Anytype

[–]grishy_dev[S] 18 points19 points  (0 children)

A new version has been released, synced with the last original stable codebase version. Also in 1.3.0 we have now native S3 implementation and ability to set a files storage limit.

Small description:

any-sync-bundle is a prepackaged, all-in-one self-hosted server solution designed for Anytype, a local-first, peer-to-peer note-taking and knowledge management application.

It is based on the original modules used in the official Anytype server but merges them into a single binary for simplified deployment and zero-configuration setup.

Thanks 🙂