Reply to thread

Message

<blockquote data-quote="Oxan" data-source="post: 769276" data-attributes="member: 97484">Let me, as another GMA developer, jump in here. I understand both sides; and I'm not totally happy with the current situation either. I see why you need them to run on different ports (I've done it myself for a while too). The case is that most of the users are running a single seat installation, and we want to make it the easiest for them. As we're introducing another service in the next release, we definitely need to improve things here. The current plan is to introduce a universal installer, which allows the user to choose which services to install and configures them. I'm even playing around with the idea of generating a QR-code which can be scanned by aMPdroid for advanced configuration. For on the local wifi things will be pretty smooth then: run the server &amp; client installer, and you're done. For external access, the big problem is that port forwarding can't be done programatically. The user needs to this himself. We can provide some documentation on which ports to forward to which IPs, but we can't take much work out of the users hands. As for documentation, it currrently is virtually non-existent. We're all volunteers though and at least I prefer coding above writing documentation. That doesn't say that it'll never be written, just that it needs someone who's willing to do the work, or some more time.</blockquote>

[QUOTE="Oxan, post: 769276, member: 97484"] Let me, as another GMA developer, jump in here. I understand both sides; and I'm not totally happy with the current situation either. I see why you need them to run on different ports (I've done it myself for a while too). The case is that most of the users are running a single seat installation, and we want to make it the easiest for them. As we're introducing another service in the next release, we definitely need to improve things here. The current plan is to introduce a universal installer, which allows the user to choose which services to install and configures them. I'm even playing around with the idea of generating a QR-code which can be scanned by aMPdroid for advanced configuration. For on the local wifi things will be pretty smooth then: run the server & client installer, and you're done. For external access, the big problem is that port forwarding can't be done programatically. The user needs to this himself. We can provide some documentation on which ports to forward to which IPs, but we can't take much work out of the users hands. As for documentation, it currrently is virtually non-existent. We're all volunteers though and at least I prefer coding above writing documentation. That doesn't say that it'll never be written, just that it needs someone who's willing to do the work, or some more time. [/QUOTE]

Verification