You do not need an account to run Recued. The server, the clients, browsing the marketplace, and installing all work without one. An account adds the public parts. It gives you a free publisher handle for the marketplace. A publisher handle is your name in the marketplace. An account can also hold the Pro extras, if you want them. The dashboard is where you manage all of this.
#What an account is for
- Publishing. A free account saves your publisher handle for you. That means you own the name. It does not mean you pay. Everything you publish shows up under that name.
- Recued Pro. Pro is a paid extra. It costs $5.99 USD/mo. It gives your
server a
<handle>.recued.netname plus a certificate that renews by itself. A certificate is proof that a web address really belongs to your server. Pro attaches to your account. That is where you manage the subscription.
#The dashboard
The dashboard lives at dashboard.recued.com. It is the one cloud page you
sign in to. It shows your publisher handle and the things you have published:
recipes, ingredients, versions, and submissions with their review state. It
shows install and rating numbers. It shows your plan. It shows whether a
server is bound to your account. It is also where you manage billing.
The dashboard shows and points. It does not write. If you edit a recipe from the dashboard, it opens the Kitchen on your own setup. The Kitchen is the place where you make and test recipes. Recipe content is never edited in the cloud.
#Binding your server
Pro extras apply to a server. So the account and the server must be linked on purpose. This is called binding. Your webclient gives the server a small binding key. That key does one job only. The server shows the key to the account to attach itself. The order does not matter. You can subscribe first or bind first. You can undo a binding and do it again when you move to a new server.
#What the account cannot do
The account holds no warehouse data. It holds no secret keys. It has no way to control your server. It cannot read your server's data. It cannot run recipes. It cannot reach into your machine. Publishing is the only thing that makes content public. And that is content you chose to publish.
#Related
- Reachability: what the Pro name and certificate really do.
- Recipes and packs: how published content is browsed and installed.