Make Git repo API properly REST #113

Closed
opened 2022-03-28 09:12:11 +02:00 by Jef Roosens · 1 comment

The API's a bit lacking at the moment, and doesn't allow for a lot of expansion. I'd like to start working with actual IDs for each entry (just a number that counts up), so that we can properly implement RESTful operations. This will be accompagnied by an improved CLI tool, which knows how to properly use this new system.

Finishing this issue will open up improvements to the build system, as the plan to allow multi repositories with multiple architectures requires more data to be stored in the API.

The API's a bit lacking at the moment, and doesn't allow for a lot of expansion. I'd like to start working with actual IDs for each entry (just a number that counts up), so that we can properly implement RESTful operations. This will be accompagnied by an improved CLI tool, which knows how to properly use this new system. Finishing this issue will open up improvements to the build system, as the plan to allow multi repositories with multiple architectures requires more data to be stored in the API.
Jef Roosens added this to the 0.2.0 milestone 2022-03-28 09:12:11 +02:00
Jef Roosens added the
enhancement
label 2022-03-28 09:12:11 +02:00

Closed by #114

Closed by #114
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vieter-v/vieter#113
There is no content yet.