Lot of work to be done

[Szymon Scholz]

• #61
  Yeah, i know that relying on external tool in just bash script is a bad idea. Any change in it's source code can lead to unworkable nixos-infect. But it seems to do good work. Just try it
• I've experienced connection issues, which are probably firewall related. By default firewall seems blocking all incoming connections.
• add support for external configuration. If specified path in option, copy file or folder content to /etc/nixos/specified

In such scenario we have files generated by nixos-generate-config, files that enable networking on port 22 and pointing to custom configuration if path specified in option.

First of all i want to ask you if you agree with me. This project have a lot potential, but sometimes feels like glueing some parts. If nixos-generate-config is not enough to fulfill some providers (like digital ocean) then maybe we can create clean default script which usually would work out of the box on most providers/devices. If custom provider is specified use another method or (better) script to handle it?

What are your experiences in that topic? Are maintainers open to accept such contribution even in different branch (as we lose current compatibility progress)? It would be nice to easily support additional hosting providers without mess in the code.