vieter-v/vieter

Archived

Make Git repo API properly REST #113

New issue

Closed

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

Jef Roosens commented

2022-03-28 09:12:11 +02:00

Owner

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

label 2022-03-28 09:12:11 +02:00

Jef Roosens commented

2022-04-07 16:14:51 +02:00

Author

Owner

Closed by #114

Closed by #114

Jef Roosens closed this issue

2022-04-07 16:14:57 +02:00

This repository is archived. You cannot comment on issues.

No labels

good first issue

No milestone

No project

No assignees

1 participant

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

No description provided.