jcollins

Fair. Making https work with mDNS seamlessly sounds like work (i.e. local CA would be needed I think). It would make things nice though.

Tailscale Operator for Kubernetes sounds like it'd fit your second bullet point. It's has a really good experience. I've only used for my person homelab but I've been more than impressed by it.

The only thing I can say with confidence is that if you're using ARM containers it is really fast, probably thanks to the Apple Silicon.

I imagine memory consumption is on par with running on Intel. I don't think Docker Desktop can really change that.

Yes, it runs ARM containers natively.

There is overhead for sure but if you use x86 containers on an Intel Mac or arm64 containers on an Apple Silicon mac, it's pretty performant.

You don't, see the download link at the bottom of the page.

Docker Desktop already ran on Macs. This is specifically for the new Apple Silicon support (M1). It's not native, technically, but it feels native the way Docker Desktop works. Basically they manage the VM for you, so you don't have too.

I've been subscribed to https://www.devopsweekly.com/ for a long time. I usually find something interesting in it every week.

Hi, I'm a member of the team that built Gyro.

Gyro, a command-line cloud automation and management tool, started as internal tool over 5 years ago. We had a vision of building one tool that would pull together several different tools (Chef, Service Discovery, Authentication, Deployments, etc) into a single interface that would greatly simplify the day to day management of our systems. This goal was very successful in transitioning to a DevOps model. Our developers are able to make configuration changes, do their own deployments, and build there own test environments without help from the operations team. And most importantly they've embraced this model because it gave them the power to make changes without waiting for an operations team and in turn it helped the operations team by reducing their work.

We decided to clean up the code and open source it. The result is Gyro (getgyro.io).

What makes this different than what exists?

- Designed with logic (for loops, if conditions, etc) from the beginning (https://gyro.dev/guides/language/control-structures.html)

- Workflows provide the ability to stage complex changes and rollback (https://gyro.dev/guides/workflows/)

- Extensions allow for tight integrations with other operations tooling (https://gyro.dev/extending/)

For some screenshots of Gyro see (https://getgyro.io/introducing-gyro), source is available one Github (https://github.com/perfectsense/gyro)

We're really excited to open source Gyro and see how people extend it!

The "pluggable convergence engines" is what we've built in Gyro[1] for this very reason. We wanted to have more control over how changes are made in production.

An example is doing blue/green deployments where you want to build a new web/application layer, pause to validate it (or run some external validation), then switch to that layer and deleted the old layer. All while having the ability to quickly roll back at any stage. In Gyro, we allow for this with workflows[2].

There are many other areas we allow to be extended. The language itself can be extended with directives[3]. In fact, some of the core features like loops[4] and conditionals are just that, extensions.

It's also possible to implement the articles concept of "non-destructive prod" by implementing a plugin that hooks into the convergence engines (we call it the diff engine) events and prevents deletions[5].

We envision folks using all these extension points to do creative things. For example, it's possible to write a directive such as "@protect: true" that can be applied to any resource and would prevent it from ever being destroyed using the extension points described above.

[1] https://github.com/perfectsense/gyro [2] https://gyro.dev/guides/workflows [3] https://gyro.dev/extending/directive/ [4] https://gyro.dev/guides/language/control-structures.html [5] https://github.com/perfectsense/gyro/blob/master/core/src/ma...

I've found a combination of Spring Boot executable jar + a small jlink built JRE runtime packaged next to the executable jar works fairly well.

Our zipped distribution is 50mb. Uncompressed the executable is 26mb and the runtime is 75mb.

I'd love for it to be smaller but I can't complain. This also makes solving for Linux, macOS, and Windows pretty trivial. They each get their own zip with packaged runtime.

I second this. Learn to fly.

I'm never happier than when I'm flying. I can see how a similar effect happens to sky divers.

https://github.com/beetlebugorg/mod_dims/wiki

Backed by Imagemagick. We usually run it behind a CDN like Akamai or Cloudfront but you can also use Apache httpd’s built-in file caching.

I bet he’s referring to having a controller but I think you can run it on your laptop, configure everything and then turn off the controller. I don’t think the controller is needed after initial configuration unless you want the stats collection.

I have the cloud key (the dongle) so I could be wrong.

It is easy but it’s still slightly harder than the average consumer would want.

I came to the exact same conclusion. The Ubiquiti solution was slightly more expensive but it works flawlessly. Very happy with it!

We saw this earlier this year after upgrading to a new Linux kernel.

The solution for us was to set this in sysctl.conf:

net.ipv4.neigh.default.gc_thresh1=0

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1331150... https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1331150...

We actually use a storage format very similar to the FriendFeed schema in Dari. Dari is a open source Java persistence layer with a full query API that stores all it's data in a JSON blob in one table with a few extra tables for indexing the JSON data.

https://github.com/perfectsense/dari

Here is the SQL schema: https://github.com/perfectsense/dari/blob/master/db/src/main...

We've used this model for almost five years now with great success. It's simplified rolling out "schema changes" since no tables need to be changed. It's also been optimized to a point where it's extremely fast.

I make about $1000 a month from Whiteboard Capture Pro and more than that from consulting. Plus I have a day job.

I just happened across http://abcnews.go.com the other day on my iPad and thought it was fairly well done and the page turn animations were decent. Check it out.

Ruby may at some point be an optional language but it's not going to replace Objective-C.

No one has that I'm aware of. At least not just taking the code and submitting it as-is. I've had many people email me about the code because they were trying to use it for their app.

If somebody did just re-submit it as a paid app I'd be fine with that. It is open source after all. I do think that's unfair to end-users though who probably wouldn't know it's free and it would add to the clutter of the App Store.

This could be interesting if enough folks post. Here is my info.

I've published 2 apps, one paid (Whiteboard Capture Pro), one free (Picture Me). Picture Me code is open sourced as well (http://bit.ly/7rmKdT). Originally I did some marketing with Google Adsense but it's too hard to track its success so I stopped. I've had some free marketing thanks to mentions in blogs, etc. Recently Apple even made a super awesome video about one of the apps (http://bit.ly/cbtkg3).

Income wise, it's decent. Surprisingly stable at it's current level. Let's just say it's paid for a WWDC trip, three iPhones and 2 iPads and there is plenty left over, plenty.

Interesting idea for a service. I wrote an Apache module that is very similar.

http://code.google.com/p/moddims/

In general, just human faces. But I had a friend tell me they drew a picture of a face on a whiteboard and it detected it.

Almost definitely won't detect a dog. :)

Good point about the license. Consider it public domain. I'll make a note about it on the blog entry.

I'll slap it up on github in a few and update the links.

http://github.com/beetlebugorg/PictureMe/tree/master

That's probably a good place for it. I guess I felt like posting it to github would be turning it into a "project", which definitely isn't the goal but I suppose I could just dump code there for the taking. Other folks do it. =\

Right, detecting who is in a picture would be "face recognition". Good point though.

Used AppViz to pull reports. Then used the sqlite database from AppViz to write some custom queries. Used that data to fill in a graph in iWorks Pages app. Tweaked the graphs by adding custom shapes to it. All relatively easy in Pages once you understand how it works.

http://pastie.org/469387 http://pastie.org/468282

Apple's iWorks Pages

They're from AppViz. It's an application for the Mac that parses App Store reports and generates graphs/etc from them.

http://www.ideaswarm.com/products/appviz/