Search Results for "hub"

...Built on Kubernetes and open-source, our software platform gives you an incredible, all-inclusive infrastructure experience thanks to an intuitive UI and advanced automation. In this repo, you'll find everything you need to contribute to development. From code and scripts to documentation and information, this is the hub of all things Batteries Included. Batteries Included is a platform designed to simplify infrastructure management for businesses, offering an all-inclusive Kubernetes-based environment with tools for DevOps, GitOps, and MLOps.

Bumblebee provides pre-trained Neural Network models on top of Axon. It includes integration with Models, allowing anyone to download and perform Machine Learning tasks with few lines of code. The best way to get started with Bumblebee is with Livebook. Our announcement video shows how to use Livebook's Smart Cells to perform different Neural Network tasks with a few clicks. You can then tweak the code and deploy it. First, add Bumblebee and EXLA as dependencies in your mix.exs. EXLA is an...

Livebook is a web application for writing interactive and collaborative code notebooks. Write notebooks in Livebook then securely deploy and share them with your team and company with Livebook Hub/Enterprise. Code notebooks with Markdown support and Code cells where Elixir code is evaluated on demand. Rich code editor through Monaco: with support for autocompletion, inline documentation, code formatting, etc. Interactive results via Kino: display Vega-Lite charts, tables, maps, and more. Automation: use Smart cells to perform high-level tasks and write notebooks faster than ever. ...

...It's designed to be used as a single registered app with id, secret, and key defined on start. Poxa is a standalone elixir server implementation of the Pusher protocol. Docker images are automatically built by Docker Hub. They are available at Docker Hub. One can generate it using: docker build -t local/poxa. Poxa uses gproc extensively to register websocket connections as channels. So, when a client subscribes for channel 'example-channel', the websocket connection (which is a elixir process) is "tagged" as {pusher, example-channel}. When a pusher event is triggered on the 'example-channel', every websocket matching the tag receives the event.