systemd: start unit after multi-user.target

[gmodena]

Start the flatpak-managed-install service after multi-user.target. This should ensure that network interfaces are up, and connectivity has been established.

Fixes #30

[ReedClanton]

This has been working for me for the last few days. Having said that, I haven't tried adding to removing flatpaks, so the testing is limited.

[gmodena]

Thanks for the ack @ReedClanton . I've been daily driving the change for a while and encountered no obvious regression. I suspect this behavior is system dependent (e.g. I manage the network stack differently on my laptops vs vms), so I might need to revisit the systemd units at some point.

[ReedClanton]

Setup

wpa_supplicant manages wireless connections and NetworkManager manages wired.

Testing

• Turned off wpa_supplicant so NetworkManager handled wireless and rebooted:
  • :heavy_check_mark:
• Removed Ethernet connection so now connected via wireless with NetworkManager and rebooted:
  • :heavy_check_mark:
• Removed source of wireless connection (not connected to the internet at all) and rebooted:
  • :heavy_check_mark:
• Re-enabled wpa_supplicant but still no source of internet (wired or wireless) and rebooted:
  • :heavy_check_mark:
• Created wireless source but still didn't plug Ethernet back in (connected via wpa_supplicant) and rebooted:
  • :heavy_check_mark:
• Plugged Ethernet back in (back to normal setup) and rebooted:
  • :heavy_check_mark:

TL;DR

Did a little testing of different network management setups and connection methods/status and didn't see any issue. Not rigerus testing (took longer to write this up), but it was something.