How to avoid having to log in to services every time?

[ianmacartney]

🚀 Feature

Is there any persisted data between workspaces?
My workflow involves logging into services like Fly.io / Convex, which store auth info in the home directory.
Do I have to log in again every time I start up a development environment, or is there some way to add the auth?

I considered adding it to the config yaml file (to write the auth files), but I wouldn't want to put my login credentials in the file that's checked into the repo.

I'd like to be able to spin up a workspace and immediately be able to run commands that require auth files to already exist in ~/.fly , ~/.convex , etc.

Thanks!

[hugodutka]

You can use the Environment feature, which lets you save your credentials in the Hocus database and inject them into prebuild and workspace tasks as environment variables. Then you’d use hocus.yml to write your auth files.

https://hocus.dev/docs/projects#environment-variables

Would that solve your issue?

[ianmacartney]

Ah, good idea - have the hocus.yml just copy from env variables to the file. Thanks, that sounds like it'd work well. The only annoyance is having users copy the values from their home directory in a format they can paste into an env variable, and try to re-create it in the scripts. Not quite as seamless as them logging in once organically, but a good workaround for now

…

On Sat, Apr 8, 2023 at 2:30 AM Hugo Dutka ***@***.***> wrote: You can use the Environment feature, which lets you save your credentials in the Hocus database and inject them into prebuild and workspace tasks as environment variables. Then you’d use hocus.yml to write your auth files. https://hocus.dev/docs/projects#environment-variables Would that solve your issue? — Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACZQW6GUUT5TPYQALIRU5LXAEV3PANCNFSM6AAAAAAWXBGBN4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[hugodutka]

Seems resolved, closing the issue then.