the ability to assemble the main application into a snap package and install the daemon (separately)?

Our company is developing a vpn client that we want to place in the Snap store has a microservice architecture and consists of 2 parts, this is an application with a graphical interface and a service (daemon) as a separate application that connects to the main application and establishes a connection using different protocols, such as wg, ikev2 OpenVPN, etc. Tell me if the ability to assemble the main application into a snap package and install the daemon (separately) is not isolated to the user’s system? If so, how to do it right?

1 Like

Would only the graphical application be a snap (and the daemon would be packaged/deployed in a different way), or would both components be packaged as separate snaps? What do you mean exactly by “not isolated to the user’s system”?

Dear cmatsuoka, big thank’s for your reply, appreciated. The daemon will be separate, and the user interface will be in a snap. Not in isolation, it means that it should not work in a container, but physically on the user’s OS as a service. What do you think?

I don’t see major problems in the design, and writing a proof of concept should be easy.

Thank you very much)