Admin API Front End #25
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Telodendria/Telodendria#25
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
The Admin API would benefit from an official, built-in front end. This can be one or both of the following:
Not sure which one to prioritize. In an ideal world, I'd eventually want to ship both. A case could be made for making the web interface either a separate binary, or just a bundle of static HTML/CSS/JavaScript files to be served by a normal web server. Likewise, a case could be made for building a different binary for the command line tool.
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.