Sync server initial setup

[conradludgate]

If I understand correctly, if you intend to host your own sync server for just your single user you have to

1. Deploy the sync server with registrations enabled
2. Register to the server
3. Redeploy the sync server with registrations disabled

It would be nice if it could work with just the 1 deployment.

I'm not 100% of what the exact flow would look, but I suspect that the deployment would need to log some token on first launch which the user could use the register for the first time

[ellie]

Ahh yeah very true, it is kinda annoying.

I think a "single user mode" would make sense, which could probably just auto generate a user at startup + provide a nice UX wrapper on the client 🤔

something like

atuin login --single THE_TOKEN

where the token is actually just the password we've generated, and --single just autofills the username as singleuser or something

Could coincide with a single_user_mode = true option on the server side, which does the normal server start except also automatically registers the user for you, with a rando generated password, which it then prints. That way nothing else in the backend would need changing + the flow for the end user would be nice as they wouldn't even need to register

[DerRockWolf]

Maybe my usecase is a bit strange but I am selfhosting atuin for me and have two users (one private and one work users), as I don't want to mix my shell histories.
So for my particular case the "single" user mode idea does not work. I think a better idea would be to provide some kind of admin api that has authentication and allows registering new accounts regardless of the open_registration setting. This would also make it easier for shared servers with closed registrations.