Provide .deb package rather than current A2SERVER/A2CLOUD installers?

[IvanExpert]

My inclination has always been against, so that I have more control over when what gets updated and also so that I don't have to muck about with the .deb format, but I can see both sides of it and I'm just putting it here for consideration.

[knghtbrd]

I'm in favor. Predepends the ability for the scripts to be downloaded and live on your system rather than in the cloud. Which is easily enough done, and in fact already has been done for A2SERVER, but it changes a lot and before I do that I want the baseline.

[knghtbrd]

Status update: Yes, it's still a good idea and it's still planned. May not be complete by 2.0.0, but the road to doing it should be clear by then.

[knghtbrd]

The update that will probably become 1.6.0 for A2SERVER has the beginnings of what will become this, though it doesn't seem like it. As of today's pushes, we no longer use $scriptURL to download anything if we detect scripts are being run from inside a source tree (git repository or otherwise). That's important because Debian packages will have to operate only on files they come with.

I haven't removed the $scriptURL interface, and for the foreseeable future I do not intend to. That will only be a consideration when/if the setup/update scripts begin operating by downloading and verifying an archive containing everything that you'd acquire through $scriptURL. Right now, if the scripts are being run from a web setup/update, you need to download things a piece at a time. The mechanism that allows you to configure where those separate pieces come from is the one that sets $scriptURL.