Gero Müller

Hi! Thanks for picking this up so quickly. I have no opinion on the implementation. I just would like to see a solution and best practice provided for the problem....

Also, for multiple child resources there would be a need for such a config anyway...

I am just looking for an easy to use CRUD resource, which includes permissions and child management. Currently one would need to add a custom resource for every entity with...

Some ideas on the topic: https://www.moesif.com/blog/technical/api-design/REST-API-Design-Best-Practices-for-Sub-and-Nested-Resources/

It would look like /projetct/{project_id}/issues/{issued_id} I think this would be a nice way for the representation. Top-level children would be okay too, if there was a filter in the PanacheEntityResource,...

Oh, sorry. I guess this depends on your API style?! I currently use @JsonIdentityReference(alwaysAsId = true) to return a list of ids: ``` { "name": "myproject", "issues": [1, 2] }...

This feature would be really useful. Why not use the docker compose syntax: ``` pipeline: deps: build: context: ./docker/build dockerfile: Dockerfile target: wp commands: npm install go mod download ```

This is just a workaround, not a solution: ``` Volumes are only available to trusted repositories and for security reasons should only be used in private environments. See [project settings]...

Hi! Since woodpecker is already using containers for everything, why not simply use containers for autoscaling too? Call the autoscaling container for every pending and finished job and provide some...

Hi! Sorry for the quiet time, was busy with other projects. @FroMage was aking for a use case earlier. One I encountered a couple of times now is "give me...