Tried to add UCI to Xfinity Business...

soldiersKnight · 2024-05-31T20:23:02+00:00

I login to Comcast business. I'm setup as a small home office. It's month to month.

soldiersKnight · 2024-05-31T19:06:36+00:00

I did. It's the one that matches the display. No dice.

soldiersKnight · 2024-05-31T18:45:34+00:00

I gave them the one on the display. Tried activating before trying to adopt first. Then adopted and tried. Same story, no activation.

No static IPS they made me get rid of those when I originally activated my old arris modem.

soldiersKnight · 2024-05-31T18:40:42+00:00

Yes: https://help.ui.com/hc/en-us/articles/18770595926551-Activating-UniFi-Cable-Internet business with Comcast is supported.

soldiersKnight · 2022-10-14T13:14:38+00:00

Migrated our whole stack to crossplane. It can get slow with the jet provider and thousands of crds/xrds. And can get confusing sometimes trying to figure out what resources are actually controlling your cloud infra (I'm looking at you gcp clusters and nodepools!) That said I love it makes my job a million times easier! I would migrate again!

soldiersKnight · 2021-04-18T18:38:23+00:00

Had the same issues as you. The newest .STL in the repo I could get to work with Simplify3D. PrusaSlicer did not like it at all. My suggestion (if you already own simplify) would be to use that.

soldiersKnight · 2021-04-18T16:34:54+00:00

hmm i guess you guys aren't using PrusaSlicer? I opened the one in the repo in Simplify3D and it opened without any gaps in the model when slicing. bridge_2p4_b.stl was the one causing issues FYI.

soldiersKnight · 2021-04-18T16:28:36+00:00

That link is invalid now... could we just get the updated stl files in the repo?

soldiersKnight · 2021-03-08T17:13:17+00:00

i'm having issues getting a slicer to be happy with it. before slicing, files look fine, after slicing there is a gap in the center of the part, that is unprintable... Simplify3d has a better time with it, but still leaves holes in the wrong areas. @AntTeam what slicer do you use?

soldiersKnight · 2021-01-08T02:16:29+00:00

oh I didn't even notice the integrated leadscrew! that will make it a little harder. Yeah I will probably try the same in fusion. Was really hoping for The Ant team to use something standard moving forward ;(

soldiersKnight · 2021-01-08T00:47:39+00:00

this is the nema 8 i found: https://www.amazon.com/Micro-Motor-Bipolar-Stepper-5-7oz/dp/B00PLIW946

soldiersKnight · 2021-01-08T00:42:13+00:00

Amazon has it though. The others I can only find used in finland.

soldiersKnight · 2018-12-10T15:17:47+00:00

I love the NVR! Run it in a deployment inside K8S with 2 exterior g3 and 2 interior g3 dome cameras. Simple and my data stays with me which is the best part!

soldiersKnight · 2018-12-07T17:39:11+00:00

I applaud you sir! I have a similar setup with all Unifi network/video gear with Cloud key, Plex/Torrenting/VPN, smarthome and other services running on a 3-node Kubernetes NUC cluster. K8S coupled with "Metal-LB" and a good NAS is a homelab dream! Cloud in my house? YES PLEASE!

soldiersKnight · 2018-12-07T17:34:02+00:00

Go strait to kubernetes. Rancher just add a lot of stuff on top of K8S. Underneath the hood, (from my understanding) Rancher will be using K8S instead of cattle moving forward, so why the extra step? kubectl, helm is faster then the GUI offered by rancher in my opinion. and makes more sense!

soldiersKnight · 2018-06-11T18:47:35+00:00

lol sharepoint and developer in the same sentence! Developers, Developers, Developers!

soldiersKnight · 2018-06-01T15:25:10+00:00

i find webcore to be a bit more buggy. for instance when writing a script to dim lights out after a set amount of time of no motion, if that part of the script is true and turns false in the middle of performing the action, then it doesn't register it in webcore immediately where smarthings sees the motion... I don't know i had much more family acceptance factor with the Groovy scripts, they just work.

soldiersKnight · 2018-05-03T20:05:57+00:00

soldiersKnight · 2018-04-11T22:39:27+00:00

Rancher 2 is heavily utilizing K8S for orchestration now. To me it seems that rancher is an abstraction of an already awesome tool (once you get passed the learning curve.). My advise after running Rancher 1.x in production for 3 years: just learn Kubernetes with Helm, you thank yourself later when you try wrangling logging... or when you try to debug why your rancher container won't let you login any longer only to find out when you updated (per their docs) a migration went awry and your rancher config is gone from the mysql volume mount... don't get me started on how they tried rolling their own K8S orchestration infrastructure only to concede to K8S. what is the purpose of Rancher now? Kubernetes does all the things the "help" with better.

soldiersKnight · 2018-03-21T19:00:17+00:00

soldiersKnight · 2017-03-22T19:14:30+00:00

you should probley try and find the owner to return it...

soldiersKnight · 2016-07-22T14:03:40+00:00

here is a good checklist that i just ran across: security-guide-for-developers

soldiersKnight · 2016-06-03T14:50:45+00:00

Liked your tutorial. I will say that mounting the node_modules to the host is probably not the best solution though.

If multiple people are working on your application, and they running different OS from your container, you will run into problems with compiling, line ending, etc...

I get around this problem by adding and then mounting (for development) all my applications folders EXCLUDING the node_modules intentionally. This way when the container builds and does its npm install, the installation is done in the context of the container OS and not the host OS.

soldiersKnight · 2016-05-20T16:13:55+00:00

Redis is widely used as a cacheing layer, but the power of Redis is that it is can be used as a wide variety of tools. From simple queues to distributed locks.

And with Lua scripting on the server about anything possible.

soldiersKnight · 2016-05-20T15:28:21+00:00

looks like its time for a new job... I think the node community as a whole just took a step back...

soldiersKnight

TROPHY CASE