Devenv 1.x

[schneider-felix]

1. Why is this change necessary?

These changes ensure compatibility with devenv 1.x

2. What does this change do, exactly?

I disabled automatic ca installation for caddy as this prevented the server from starting up when using tls. Furthermore I removed the usage of currentSystem because it was removed in devenv version 1.0

3. Describe each step to reproduce the issue or behaviour.

4. Please link to the relevant issues (if any).

Fixes #94

5. Checklist

• I have rebased my changes to remove merge conflicts
• I have written or adjusted the documentation according to my changes

[M-arcus]

Please add process.implementation = "honcho";, the new process manager blocks the port 9999 if not configured otherwise

[schneider-felix]

@M-arcus is this strictly necessary for compatibility reasons or is this a general recommendation for 1.x?

[M-arcus]

Yes, without further configuration this does not allow starting 2 devenvs of this setup at the same time. Alternatively there needs to be a configuration added to be able to access the process -compose port.

[schneider-felix]

@M-arcus whats does process manager use Port 9999 for? Are there any downsides to changing this config?

[M-arcus]

It's the port of the rest client of process-compose: https://f1bonacc1.github.io/process-compose/client/?h=port#rest-api

Honcho does not have one by default, therefore no port conflicts

Devenv .6 had honcho, devenv 1 has honcho, process-compose, overmind and hivemend as process manager

[lx-wnk]

Thanks for the explanation @M-arcus.

Thank you for your contribution @schneider-felix!

Personally, I'd say that we should go with the default values, especially since with our configuration it is not possible to start two projects without adjusting the ports anyway.

However, this should be explicitly mentioned in the README and the update instructions.

What do you think?

[M-arcus]

Adhering to the defaults is important, I agree 👍

In case this PR gets merged in the current state, I will add a PR with an (optional) port configuration for process-compose, since it's probably only affecting a few users.

[kleinmann]

Thank you for your contribution @schneider-felix ! 🙂

@M-arcus Please feel free to add the info for process-compose ports 🙂