Zarial

~I think you can do this passing a `Headers map[string][]string` to `func NewOnlineJob(... , headers map[string][]string, ...)`.~ Edit : My bad this is not the purpose of this parameter.

An `example/` folder with various ways to use the CLI and the package would be great. On the webapp side, what's the purpose of the `/api` documentation endpoint ? Since...

> About `api.jinja` it's currently not used nor served, we can scrap it or replace it with an updated version I have removed the /api endpoint and his related jinja...

Thanks @hazrpg mentioning this ! And i think you're right. I'll fix this asap, also, a PR can be open even for small changes like this one !

I'll take this and see what can be done quickly. We need to make this compatible for package and cli usage first, then we can add it to the frontend...

I'm currently working on a refactor of the backend and make the frontend works with the changes. After talking about it with @cyclotruc , we need a REST api and...

The WIP is available on #346 I'm not familiar with the github workflow, so I'm a bit surprised that the PR was created even without any action on my part.

I don't think there's a problem here, as long as you don't have a POC, I don't see any way to exploit that. In fact, we **should** use a safe...

The frontend was rendered for each call and then the entire dom was replaced. This is not the case anymore, we do perform real API calls and then populate the...

I'll test it out in few hours. I see that both logic and routing are defined and implemented within the entrypoint of the server, maybe move this to the "routers/"...