Notices by Lollipop Cloud (cloud@ap.lollipopcloud.solutions), page 4
-
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Saturday, 09-Feb-2019 02:46:51 UTC Lollipop Cloud We found an existing, no changes necessary way to get auto config of caddy for containers. Many thanks to the caddy-docker-proxy dev for the trick.
The latest firefly iii release builds on arm32 and arm64
We are steadily making progress on how much command line magic is necessary to get services off the ground. As well as services that enhance the options available for self hosting a cloud.
We still arent 100% sure how to handle some services which require initial config prior to first launch. However, services which don't need config prior to first launch are looking fantastic.
The combo of portainer and caddy-docker-proxy greatly reduces the amount of configuration at the command line and allows us to self document deployments via templates. -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Friday, 08-Feb-2019 05:32:43 UTC Lollipop Cloud We just published an updated Pleroma build that plays nice with our Plume blog links.
If you're running our Pleroma Docker images you'll want to update to the latest builds and restart your instance. -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Friday, 08-Feb-2019 05:28:42 UTC Lollipop Cloud There are reports rich media in pleroma is fixed with this link....
https://ap.blog.lollipopcloud.solutions/~/News/works-on-arm-sponsorship -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Wednesday, 06-Feb-2019 03:30:19 UTC Lollipop Cloud We've begun work on our Portainer setup.
It's a really nice UI that helps simplify deploying Docker containers.
MOST of our Docker images will slip nicely into the template system and if we get some upstream patches accepted... should help with auto-config of caddy rules too!
We can't wait to get further and start the alpha and beta tests! -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Tuesday, 05-Feb-2019 17:23:38 UTC Lollipop Cloud We just checked and our PiHole builds are current for the release that happened on 2019/02/03.
H/T @luricaun for the reminder. -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Tuesday, 05-Feb-2019 15:36:11 UTC Lollipop Cloud 📣 Apologies 📣
The version of Pleroma we're using has a bug in the URL parsing and we were getting a LOT of errors trying to post a link to our Plume blog.
It seems the posts were going through despite errors showing in our UI.
We did NOT mean to spam everyone 10+ times...
🤗 -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Tuesday, 05-Feb-2019 05:06:48 UTC Lollipop Cloud Apparently we can't post links?
Where is this moth in the tubes?!? -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Tuesday, 05-Feb-2019 05:06:06 UTC Lollipop Cloud Our latest blog post is live
We'd like to thank Ed in particular for working with us to be approved as part of the Works on Arm program!
https://ap.blog.lollipopcloud.solutions/~/News/works-on-arm-sponsorship -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Monday, 04-Feb-2019 21:52:21 UTC Lollipop Cloud 🤔 -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Monday, 04-Feb-2019 21:38:09 UTC Lollipop Cloud We understand that "nuking all notifications prior to XXXX time" is kind of a scorched earth approach but we *were* able to see all the wonderful boosts and fav's that came through in the database.
We're back to normal now and look forward to seeing our notifications again! -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Monday, 04-Feb-2019 21:32:13 UTC Lollipop Cloud Confirmed!
All of our notifications prior to "just now" were some how broken...
Clearing them all from the database seems to have fixed things...
We have a backup. Will work with Pleroma devs on a secondary server / instance to see if we can sort out the how and why of things. -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Monday, 04-Feb-2019 04:03:02 UTC Lollipop Cloud We're still seeing errors with notifications at this time.
We will respond once things are back to normal.
In the meantime we can still post, just not see all your awesome replies! -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Monday, 04-Feb-2019 03:48:37 UTC Lollipop Cloud Paging @kemonine -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Monday, 04-Feb-2019 00:28:37 UTC Lollipop Cloud Request: GET /api/qvitter/statuses/notifications.json?count=20
** (exit) an exception was raised:
** (ArgumentError) argument error
:erlang.bit_size(nil)
(pleroma) lib/pleroma/web/mastodon_api/views/status_view.ex:192: Pleroma.Web.MastodonAPI.StatusView.render/2
(pleroma) lib/pleroma/web/twitter_api/views/activity_view.ex:279: Pleroma.Web.TwitterAPI.ActivityView.render/2
(pleroma) lib/pleroma/web/twitter_api/views/activity_view.ex:176: Pleroma.Web.TwitterAPI.ActivityView.render/2
(pleroma) lib/pleroma/web/twitter_api/views/notification_view.ex:62: Pleroma.Web.TwitterAPI.NotificationView.render/2
(elixir) lib/enum.ex:1314: Enum."-map/2-lists^map/1-0-"/2
(elixir) lib/enum.ex:1314: Enum."-map/2-lists^map/1-0-"/2
(phoenix) lib/phoenix/view.ex:399: Phoenix.View.render_to_iodata/3 -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Sunday, 03-Feb-2019 23:36:48 UTC Lollipop Cloud 📣 Updated Transparency Report 📣
TLDR
- We have REMOVED Amazon AWS from our build infrastructure. We no longer use Amazon services.
- We have one a spot in the Works on Arm program and received a really nice server. It's now deployed and managing our Docker builds.
- We depricated 3 of our build servers thanks to the hardware received from Works on Arm
- We have added 2 more lollipops for hosting our public services and shuffled lightly. We've been in need of additional hardware for our public infrastructure for awhile and the additional VPSs from Scaleway have made a big difference. -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Sunday, 03-Feb-2019 23:35:56 UTC Lollipop Cloud 📣 Updated Transparency Report 📣
https://ap.blog.lollipopcloud.solutions/~/News/updated-transparency-report
TLDR
- We have REMOVED Amazon AWS from our build infrastructure. We no longer use Amazon services.
- We have one a spot in the Works on Arm program and received a really nice server. It's now deployed and managing our Docker builds.
- We depricated 3 of our build servers thanks to the hardware received from Works on Arm
- We have added 2 more lollipops for hosting our public services and shuffled lightly. We've been in need of additional hardware for our public infrastructure for awhile and the additional VPSs from Scaleway have made a big difference. -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Saturday, 02-Feb-2019 21:35:56 UTC Lollipop Cloud Did we mention we ♥ getting reports about our services?
We are mere humans and don't always notice immediately. Being poked (even while napping) is welcome. -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Saturday, 02-Feb-2019 21:24:31 UTC Lollipop Cloud 📣 PSA 📣
Our Docker registry server hiccuped while we were napping...
We've poked it with a stick and it's back online!
Apologies for that... we will be investigating the root cause.
Thankfully NONE of our other services were affected 😉 -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Saturday, 02-Feb-2019 01:32:00 UTC Lollipop Cloud 🤞 -
Lollipop Cloud (cloud@ap.lollipopcloud.solutions)'s status on Thursday, 31-Jan-2019 20:21:00 UTC Lollipop Cloud We're back!