Admin API Front End #25
The Admin API would benefit from an official, built-in front end. This can be one or both of the following:
- A command line utility (possibly even the telodendria server binary itself) that talks directly to the Admin API.
Development on these can start whenever, we don't have to wait for the first stable release. In fact it might be worthwhile to develop the front end as the API is developed, although I can see how this would lead to a lot of rewrites and bolted-on extensions as the Admin API evolves.
I think the web interface and the command line tool should both be their own separate projects/repositories. Telodendria should only expose admin APIs, this would focus development on the actual server itself rather than tools for an incomplete server implementation.
Yeah, that does make the most sense. And this is definitely pretty low on the priority list, I wasn't planning on starting a front end any time soon. But you are right, they probably should be entirely separate projects.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?