Linux containers project. Foreshadowing of this move at https://linuxcontainers.org/lxd/. - Source: Hacker News / 7 months ago

The expected changes are: - https://github.com/lxc/lxd will now become https://github.com/canonical/lxd - https://linuxcontainers.org/lxd will disappear and be replaced with a mention directing users to https://ubuntu.com/lxd - The LXD YouTube channel will be handed over to the Canonical team - The LXD section on the LinuxContainers community forum will slowly Be sunset in favor of the Ubuntu Discourse forum... Source: 12 months ago

Hello community, It seems LXC images for arm7l/armhf are no longer available, not from the official Turris mirror nor from LinuxContainers.org (https://linuxcontainers.org/lxd/). Any solution or alternative for people like me heavily relying on the Turris Omnia to run LXC containers? Thanks. Source: 12 months ago

Any distribution stable enough and LXD https://linuxcontainers.org/lxd/ for containers and VMs. Source: over 1 year ago

This has been really stable, and has worked pretty well for me. I deploy the applications to a set of LXD containers (read: lightweight Linux VMs) on Proxmox, a free and open-source hypervisor with an excellent management interface. - Source: dev.to / about 2 years ago

I also read that Salt was using MessagePack to format their messages. MessagePack is a format like JSON, but more compact. - Source: dev.to / 9 months ago

So appreciate such a detailed reply, thanks. btw, why did you choose tinylib/msgp from 4 available go-impls? Source: over 1 year ago

If you find you're running the serial connection at maximum speed and it's still not fast enough, try switching to a more compact binary encoding that has both Serde and Arduino implementations, like MsgPack... Though I don't remember enough about its format off the top of my head to tell you the easiest way to put an unambiguous header on each packet/message to make the protocol self-synchronizing. Source: over 1 year ago

The information can be stored in a database or as files, serialized in a standard format and with a schema agreed with your Data Engineering team. Depending on your information and requirements, it can be as simple as CSV, XML or JSON, or Big Data formats such as Parquet, Avro, ORC, Arrow, or message serialization formats like Protocol Buffers, FlatBuffers, MessagePack, Thrift, or Cap'n Proto. - Source: dev.to / over 1 year ago

MessagePack Similar to JSONs, just more compact, although not as much as the ones above. Still, it's usefull to retain some readability in your messages. Source: over 1 year ago