Self-hosters wanted: try the Registry Bridge (beta)

[jagduvi1]

If you run your own Cellarion, your install can now search the shared wine registry on cellarion.app and copy the single wines you add, tasting profile and drink windows included. We call it the Registry Bridge, and it is in beta. We are looking for a handful of self-hosters to run it for real and tell us what happened.

What it is

• A key tied to your cellarion.app account that your own backend presents to the registry.
• One wine at a time: search gives identities, picking one copies that wine into your database. No bulk access, no snapshot, ever.
• Free. The cost is an account and accepting the Registry Data Terms.

What you need

1. Your install on the current release (the client is part of the backend from this month's releases).
2. A cellarion.app account. In Settings, "Connect a self-hosted Cellarion" issues the key.
3. Two lines in your .env, then restart the backend:

   REGISTRY_BRIDGE_URL=https://cellarion.app
   REGISTRY_BRIDGE_KEY=cbr_…
   

   Settings on your install then shows the connection and today's quota use.

What we want to hear

• Search results that were wrong, missing or oddly ordered.
• A copied wine whose country, region, appellation or grapes did not land in your taxonomy as expected.
• Profiles or drink windows that differ from cellarion.app.
• Anything in Settings, the .env step or an error message that made you stop.
• How the quotas felt during an import (the monthly import window multiplies them by five for a day).

How to join
Reply here with roughly how big your cellar is and what you run the install on, then just use it. Bugs go to the issue tracker; everything else fits in this thread. There is nothing extra for testers except that your feedback shapes what ships next, and a thank-you in the blog if you want one.

Docs: how the bridge works · what happens if a key misbehaves. The announcement post: We locked the wine registry down. Now you can have it.