I've been looking everywhere for a way to get the server installed on Ubuntu Arm for PI3.
Do you have any suggestions on this?
the only one supported version for Pu is Debian Jessie(8) https://wmspanel.com/nimble/install#os_raspbian
Thank you for the reply. I have tried it and I have it up and running.
In production we use Ubuntu on the Pi3. I was looking to migrate from Nginx RTMP module in order to gain some additional features needed for the business.
I was hoping that I can get the Jessie build installed on Xenial. There are the libzip2 dependencies that are not matching on Ubuntu. So the install bumped there.
Are you guys planning for it?
I know that micro-sites is just a small part of the business. We use them as the Origin feeds.
If you know of any workaround, I'd be happy to try it.
Thank you so much.
I guess the only way to run it on Xenial is copying all required dependencies and nimble binary to Xenial and run Nimble with LD_LIBRARY_PATH pointing to the directory with binaries (it should work but I'm not sure as I have not tried it).
We actually did not have plans to build/release packages for Ubuntu 16.04 for Pi, but we're planning to release packages for Raspbian Stretch.
Thank you for the suggestion. I was thinking about it too. I've not looked yet at the folders that the server uses.
I'll give it a shot. I'll let you guys know in the next few days how that works out.
We do have a controller server handling the micro-sites, we may just use the control API to handle instances. It would be interesting to see how the testing will come out, since some of the WMSPanel functionality requires all servers to have incoming internet access.
BTW, please try to install Nimble for Raspbian to Ubuntu Xenial adding not only Nimble's repository to sources.list, but also Raspbian Jessie repo to get libzip2 and other dependencies, i.e. repo lines will be the following:
Will NImble be installed in this case?
It is so funny that you suggested this. I had tried this at the beginning, and it gives a few repo errors. The repo update marks the package as ignored and it generates errors like this.
W: GPG error: http;//mirrordirector.raspbian,org/raspbian jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9165xxxxxxxDD2E
W: The repository 'http://mirrordirector.raspbian.org/raspbian jessie InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Originally I stopped here, because it gave me the impression that it will not work and it will not have a clean install.
Now that you mentioned the same thing, I did try it again, and I've continued the install regardless..
It accepted the install package with the warning on zipLib2 version... which was expected.
I got the server up and running successfully and have it registered with WMSPanel. No other tricks required.
I hope that this is going to help others that are looking for options.
Thank you for the suggestion. Top job!
OK, thank you for checking it out.
It should be also possible to import Raspbian repo's GPG key to get rid of GPG error, though it is not mandatory, of course, as this repo will be used only once during initial installation of Nimble to get required dependencies.
and required to achieve the purposes illustrated in the
If you want to know more or withdraw your consent to all or some of the cookies, please
refer to the