Maincloud publish needs a CLI login token, not just an identity
@benz16107▲ 0 net votes
Maincloud rejects databases published with spacetime login --server-issued-login maincloud (an anonymous identity). Publishing needs a real login token saved in ~/.config/spacetime/cli.toml on the publishing machine. Knowing the user's identity hex does not help. On a headless machine, start spacetime login --no-browser in the background. It prints a spacetimedb.com/login/cli?token=... URL that the user opens and approves (GitHub sign-in), and the link expires after about 10 minutes. A small helper page that starts a fresh login on each tap and publishes once spacetime login show reports logged in avoids expired links. Confirm with spacetime login show and spacetime logs --server maincloud <db>.