Open Source Go System Software

Inspired by MailCatcher, easier to install. Built with Go, MailHog runs without installation on multiple platforms. Run it from Docker Hub or using the provided Dockerfile. The SMTP server starts on port 1025, the HTTP server starts on port 8025, in-memory message storage. ESMTP server implementing RFC5321. Support for SMTP AUTH (RFC4954) and PIPELINING (RFC2920). Web interface to view messages (plain text, HTML or source). Supports RFC2047 encoded headers. Real-time updates using EventSource. Release messages to real SMTP servers. Chaos Monkey for failure testing. HTTP API to list, retrieve and delete messages. See APIv1 and APIv2 documentation for more information. HTTP basic authentication for MailHog UI and API. Multipart MIME support. Download individual MIME parts. In-memory message storage. MongoDB and file based storage for message persistence. Lightweight and portable. No installation required.

With flexible deployments models using clusters, superclusters, and leaf nodes, optimize communications for your unique deployment. The NATS Adaptive Edge Architecture allows for a perfect fit for unique needs to connect devices, edge, cloud or hybrid deployments. With true multi-tenancy, securely isolate and share your data to fully meet your business needs, mitigating risk and achieving faster time to value. Security is bifurcated from topology, so you can connect anywhere in a deployment and NATS will do the right thing. With the ability to process millions of messages a second per server, you’ll find unparalleled efficiency with NATS. Save money by minimizing cloud costs with reduced compute and network usage for streams, services, and eventing. NATS self-heals and can scale up, down, or handle topology changes anytime with zero downtime to your system. Clients require zero awareness of NATS topology allowing you future proof your system to meet your needs of today and tomorrow.

Pydio Cells is the mature open source alternative to dropbox and box, for the enterprise. Why building your own box? You need to access your documents across multiple devices, and regularly share documents (weblinks) and folders with your contacts and teams. Still, using a consumer SaaS box or drive service is neither practical nor safe. And enterprise SaaS box or drive services are expensive and come with Disk Storage that you already have on your servers or private cloud. How to build your own box with Pydio? Easily install Pydio on your servers or cloud of choice, Simply share documents and folders with your teams, Administrate your box with an Entreprise grade console (rights, groups, plug ins), Access documents with a Web Gui, Smartphones and tablet apps (iOS, Android), Sync folders on your computer (PC, Mac, Linux).

PingMe is a personal project to satisfy my needs of having alerts, most major platforms have integration to send alerts but its not always useful, either you are stuck with one particular platform, or you have to do alot of integrations. I needed a small app which i can just call from my backup scripts, cron jobs, CI/CD pipelines or from anywhere to send a message with particular information. And i can ship it everywhere with ease. Hence, the birth of PingMe. Everything is configurable via environment variables, and you can simply export the logs or messages to a variable which will be sent as message, and most of all this serves as a swiss army knife sort of tool which supports multiple platforms. Supported services Discord Email Microsoft Teams Mattermost Pushover Pushbullet RocketChat Slack Telegram Twillio

AEBL Mobile Media Player, changing how we consume media. AEBL is a media player and a digital media platform in use in the IHDN XPO network media system ( http://www.ihdn.ca/Xpo_VI.html ). AEBL is foremost a mobile media distribution and playback framework. It was created to be the core technology that is used in a television ad insertion and digital sign, and further development has opened up many more applications. It currently is designed to run on a raspberry Pi, although it is being ported to other systems. The AEBL blog is located here: http://aeblm2.blogspot.ca/ For those interested in trying it out, you will need a Raspberry Pi (should be the B series with 512MB) and a SD card (4GB or higher, recommend base 8GB but the larger, the better, for content storage). The current image is a ~680MB 7zip compressed file of it's original 2.7GB size, located on dropbox, here: https://www.dropbox.com/s/lj0r6yia4tsnz8w/140815-aeblpi.img.7z?dl=0

kiosk is a multi-tenancy extension For Kubernetes. Secure cluster sharing & self-service namespace provisioning. Accounts & account users to separate tenants in a shared Kubernetes cluster. Self-service namespace provisioning for account users. Account limits to ensure quality of service and fairness when sharing a cluster. Namespace templates for secure tenant isolation and self-service namespace initialization. Multi-cluster tenant management for sharing a pool of clusters. Kubernetes is designed as a single-tenant platform, which makes it hard for cluster admins to host multiple tenants in a single Kubernetes cluster. However, sharing a cluster has many advantages, e.g. more efficient resource utilization, less admin/configuration effort or easier sharing of cluster-internal resources among different tenants.