Headless Dokploy?

[ahmedabdou14]

Is there a way to run a headless version of Dokploy without the UI to use it only as an API?

[Siumauricio]

It would be interesting to have something like that. In the end, the API does all the work, so perhaps we could eliminate the UI and just keep the API (which is a TRPC api), although connecting things like GitHub providers could be a bit complicated. But it's something that could work; we would just have to look into it and investigate how to adapt it.

[ahmedabdou14]

Yes many features like github auth would be obsolete when working with just the APIs.

I am starting a startup that will utilize dokploy heavily. I am writing an sdk for it in Golang and found that the best way to authenticate is username and password. Or provide an api key for a specific organization if the dokploy instance was accessed via Ui beforehand.

I even had to reverse engineer my way to create the admin user on dokploy using the API called by the UI.

I can opensource some of the work soon, including the docker compose i made to avoid using the installation script.

If you need any help in any of those, would be happy to help. Thanks

[samthomson]

How did you solve installing to first get an api key? I am trying to make a layer on top of dokploy where a user does very simple plug/play creation of services. But I don't want them to have to first sign in to the underlying dokploy and generate an api key (even this may be too complicated for them). Ideally I could just call an endpoint on first install that creates a user and api key, then I store the api key for my app/layer.