Karol Zadora-Przylecki

The spec says (https://github.com/compose-spec/compose-spec/blob/master/spec.md#the-compose-application-model, last paragraph): > A **Project** is an individual deployment of an application specification on a platform IMO this is quite unfortunate choice of the word. Almost...

I wonder what are the pros and cons of having ingress as a top-level entity in the Compose file. For example: ```yaml ingress: rules: - protocol: http path: /A port:...

@ndeloof good point about profiles. The "bring your own ingress config" approach also meshes well with some types of ingress services like `traefik` that use pod labels for ingress configuration...

Overall I think it is a great idea! 👍 With regards to minimal API vs controller-style: ideally we should have at least one example of each kind. The reason is...

I would love to see this fixed too. Here are more detailed repro steps--hope this helps 1. Configure an SSH host with a non-DNS-resolvable name (Host field in./ssh/config, e.g. `mydevbox`)...

@phuctm97 that would be awesome, let me know if I can be of help!

Another approach is to leverage https://github.com/nodejs/node/pull/9296 to retrieve TTL information about DNS records and not repeat the resolution until the record has expired.

The original Unix/C semantics is that `stdout` is for program output and `stderr` is for diagnostic, human-consumption messages. We should NOT assume that presence of data in `stderr` implies error...

https://github.com/getporter/porter/issues/1507 here we go again ☺️

https://github.com/getporter/porter/issues/1507 was not with WSL2, and the error was different, but it is in the same ballpark: essentially Porter installation script is trying to download some bits from the CDN...