Notices by Lollipop Cloud (cloud@ap.lollipopcloud.solutions), page 5
-
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Thursday, 31-Jan-2019 04:20:01 UTC 
Lollipop Cloud
📣 Service Update 📣
We just did a quick migration of our Gitea instance (our source code).
It's now deployed on its own Lollipop.
We *also* enabled SSH for Gitea while we were making the changes.
We did this mainly because we're seeing "high" RAM use on a few things and wanted to separate our services a little to ensure the "important stuff" was a bit more separated server wise.
We now have a bit more headroom on our Lollipops that provide public services. This was a direct reaction to how many amazing people are poking at our infra, talking to us, contributing and more.
👍 -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Monday, 28-Jan-2019 03:46:21 UTC
Lollipop Cloud
Our 2nd registry is online as is clair static analysis of containers. We've also updated our registry browser that's located at https://docker.lollipopcloud.solutions
What does this mean?
Generally speaking: nothing for the day to day
For the data librarians: it means we have a deeper cache of ALL our mirroring, build output and more on our build lan in case something happens to our public registry. Even if such data doesn't land in the public registry.
For the security minded: it means the clair static analysis tool is being run against our builds and shows output now inside our docker registry browser. You'll see a lot of details that range from legitimate to useless. We deployed this as part of our transparency focus as well as our security minded approach to things.
Clair shows a lot of cruft that may or may not apply to an individual container and upstream projects aren't the best at updating their build dependencies. We prefer to build what the upstream projects publish officially so... some stuff may not be the most up-to-date or current.... -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Sunday, 27-Jan-2019 21:08:31 UTC
Lollipop Cloud
You may have noticed some x86_64 builds being pushed to our Docker registry.
Why?
We're deploying a secondary registry on an x86 box with some additional integrations for testing and tuning. We're also planning on keeping a second cache of all our containers locally as part of our build infrastructure.
As part of our commitment to transparency we've pushed the containers we're running locally for the 2nd registry infra. They are their for your review and we will NOT be supporting them in the docs. Hosting a Docker registry is not an easy task and well outside the scope of our documentation for the time being. -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Sunday, 27-Jan-2019 19:46:13 UTC
Lollipop Cloud
For those interested in a little technical reading, these are some good links
https://nullsweep.com/docker-static-analysis-with-clair/
https://nullsweep.com/security-patching-docker-containers/
We've read them and are going to assess viability 😉 -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Saturday, 26-Jan-2019 20:10:21 UTC
Lollipop Cloud
Our docker hub mirroring script went a little haywire with updates we made for better pi-hole mirroring.
We've cleaned up the mess and are presently uploading the latest releases as well as the one that was originally present in our registry.
Going forward we're looking at building pi-hole from their sources to avoid some of the hassles that come with their docker hub tagging convention.
Things will be back to normal in those repos soon -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Friday, 25-Jan-2019 21:31:50 UTC
Lollipop Cloud
Portainer is already up on the registry but the automagical caddy will NOT be deployed to the registry just yet.
There is a bug in portainer. It works well but not with automagical caddy.
I've submitted a patch to BOTH portainer *AND* automagical caddy.
Until the automagical caddy patch is accepted and/or portainer is bumped with the other patch... we can't publish any official stuff.
The caddy build code will be online soon with the registry push disabled. You're welcome to build it with our code but note there may be a conversion necessary depending on how upstream projects react to the submissions. Because we can't be sure our updates will be accepted as-is we won't put our users in the position of needing to shuffle later.
Automagical caddy PR: https://github.com/lucaslorentz/caddy-docker-proxy/pull/92
Portainer bug fix PR: https://github.com/portainer/portainer/pull/2655 -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Friday, 25-Jan-2019 05:28:15 UTC
Lollipop Cloud
📣 Pay it forward 📣
We recently removed our NitroKey Storage devices from rotation in favor of some other options.
Instead of letting our NitroKey Storage sit on the shelf to collect dust we found someone who would benefit greatly from having one on-hand.
It's been shipped and we are happy it's headed to a new home.
👍 -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Friday, 25-Jan-2019 05:23:14 UTC
Lollipop Cloud
Informal Poll
If you deploy a 🍭 ☁️ will it be...
⚪ Always On The Internet
⚪ Usually On The Internet
⚪ Rarely On The Internet
⚪ Never On The Internet (initial setup aside) -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Friday, 25-Jan-2019 00:59:59 UTC
Lollipop Cloud
Gitea 1.7.0 has been released.
Our Docker Registry has the latest for your use and enjoyment! -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Wednesday, 23-Jan-2019 06:19:22 UTC
Lollipop Cloud
We spent some time today to see if we could get portainer.io running and... early indications are looking good.
Portainer allows for deploying Containers more easily than the command line and it has a really nice UI for managing Docker. Our hope is this can become a nice way for our users to deploy different services without having to open up a command line and tinker.
We were able to build it and setup some basic docs as well as templates that should be able to deploy our Docker images.
Our notes are at https://kanban.lollipopcloud.solutions/project/admin-lollipop-documentation/us/43?kanban-status=39 for the curious.
We have NOT tested to any real extent. We were able to deploy it on our NAS as well as see the templates come into the setup. That's all we could get done today. We also were able to deploy ONLY the arm32v7 templates.
Attached are a few screen caps of our work thus far. -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Saturday, 19-Jan-2019 22:10:26 UTC
Lollipop Cloud
We are back!
We've successfully moved Pleroma to Docker and sunset our original deployment.
This was the *last* service we had for migration 😁
For the curious, full details on how we did this are at https://kanban.lollipopcloud.solutions/project/admin-lollipop-documentation/us/38?kanban-status=39 -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Saturday, 19-Jan-2019 18:17:02 UTC
Lollipop Cloud
Time to go mobile and see how well this works out in the real world.
Pictured is:
- a big battery pack
- Quectel EC25 in a USB adapter with big blade antennas and a chip GPS antenna
- orange pi PC2
- some WiFi adapters for the local hotspot
- adafruit ultimate GPS board with big, active antenna
- adafruit real time clock module
- spark fun USB serial adapter ) -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Saturday, 19-Jan-2019 03:05:33 UTC
Lollipop Cloud
@kemonine upgraded their lollipop GPS antenna today
😀 -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Thursday, 17-Jan-2019 22:58:01 UTC
Lollipop Cloud
Link heads to the notes we have for NextCloud updates that will be published to our documentation soon.
https://paste.lollipopcloud.solutions/?e43cc1c5d183f3bb#4PS9HjMI1asKEefEV3nL7r925IyOx8QV1g2SA3pMaPQ=
We're still poking an ipv6 LTE modem "thing" and once that's complete we'll be pushing a number of updates to our LTE modem documentation as well as our NextCloud documentation
Please note: the LTE modem configuration stuff is incredibly advanced and technical in nature. It's also very very fragile and relies upon a LOT of things to be done by hand at a command line. This is *not* something we recommend but do publish in the hope that our more advanced users would be willing to help us get some better documentation and testing done 😉 -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Wednesday, 16-Jan-2019 04:34:21 UTC
Lollipop Cloud
A GPD Pocket, LTE modem and Orange Pi 2e...
*this* is the Lollipop Cloud in action 😉 -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Wednesday, 16-Jan-2019 03:12:58 UTC
Lollipop Cloud
Looks like NextCloud notes are working.
We'll publish updates soon.
In the mean time know this: we *are* aware our NextCloud docs aren't 100%
Next on our list -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Wednesday, 16-Jan-2019 02:01:23 UTC
Lollipop Cloud
Guess how long it took us to sort this out?
https://paste.lollipopcloud.solutions/?ef68a5d096bc9129#RfAfmBmTglgaiJ38RbX69aAcBFE5bIhD42NALVk/Pa8= -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Tuesday, 15-Jan-2019 18:15:43 UTC
Lollipop Cloud
We've merged a number of documentation updates related to GPS and LTE Modems today!
These are *advanced* topics.
GPS requires adding an additional board to the expansion header of a Lollipop.
The LTE modem requires setting Debian to use the 'testing' tree for some packages.
BOTH are highly technical. Especially if you've not done this sort of thing in the past. We also do NOT support or recommend these yet. We're still fine-tuning and testing and more. In due course these will be better supported but for now they are for our advanced users.
GPS docs: https://git.lollipopcloud.solutions/lollipop-cloud/docs/src/branch/master/hardware/gps.md
LTE docs: https://git.lollipopcloud.solutions/lollipop-cloud/docs/src/branch/master/hardware/quectel_ec25.md -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Tuesday, 15-Jan-2019 03:33:38 UTC
Lollipop Cloud
Is that GPS + PPS as a chrony time source?
Why yes it is!
We used an Adafruit Ultimate GPS board to get this working... This *will* make it into the docs for those interested in really good time keeping.
This was done independent of the LTE tinkering that was posted earlier and is way easier to accomplish (aka: no messing about with apt packages/repos). -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Monday, 14-Jan-2019 05:11:05 UTC
Lollipop Cloud
The latest @pinafore release has landed in our Docker registry.
Enjoy!
All Bobinas P4G content and data are available under the