remote driver for bluepill board
Write composable declarative 3D behaviors like a story.
A library to help quickly and easily set up getters and setters.
Rust FFI of Basic USB CDC support in C generated by ST official IDE
Rust FFI of Basic USB HID support in C generated by ST official IDE
A no_std compatible Rust driver for the low power ST 3-Axis MEMS 14-bit accelerometer LIS2DW12 using the SPI bus in async or blocking mode
Blipper infrared utility
A cortex-m bootloader toolkit
A lightweight websocket library for embedded systems (no_std)
A fork of the embedded-websockets crate that uses embedded-io-async for async IO.
Virtual FAT16 file system for embedded USB Mass Storage Device use
Infrared remote control library
Platform-agnostic driver for keypad matrix circuits
Hitachi HD44780-compatible LCD screen support for embedded development
Safe Rust Bindings for ThreadX using threadx-sys
Bluepill keeps your daemons up while taking up as little resources as possible. After all you probably want the resources of your server to be used by whatever daemons you are running rather than the thing that's supposed to make sure they are brought back up, should they die or misbehave.
Bluepill keeps your daemons up while taking up as little resources as possible. After all you probably want the resources of your server to be used by whatever daemons you are running rather than the thing that's supposed to make sure they are brought back up, should they die or misbehave. Forked from http://github.com/arya/bluepill
send events to gearman when a bluepill process state changes
send events to nagios when a bluepill process state changes
The original bluepill process monitor worked well. In 2013 several changes were introduced that were detrimental to the stability of bluepill, as well as the system running it. This fork reverts back to the stable/non-destructive code.
EventedBluepill keeps your daemons up while taking up as little resources as possible. After all you probably want the resources of your server to be used by whatever daemons you are running rather than the thing that's supposed to make sure they are brought back up, should they die or misbehave.
Bluepill keeps your daemons up while taking up as little resources as possible. After all you probably want the resources of your server to be used by whatever daemons you are running rather than the thing that's supposed to make sure they are brought back up, should they die or misbehave.
Bluepill keeps your daemons up while taking up as little resources as possible. After all you probably want the resources of your server to be used by whatever daemons you are running rather than the thing that's supposed to make sure they are brought back up, should they die or misbehave.
Bluepill keeps your daemons up while taking up as little resources as possible. After all you probably want the resources of your server to be used by whatever daemons you are running rather than the thing that's supposed to make sure they are brought back up, should they die or misbehave.
Bluepill keeps your daemons up while taking up as little resources as possible. After all you probably want the resources of your server to be used by whatever daemons you are running rather than the thing that's supposed to make sure they are brought back up, should they die or misbehave.
Bluepill keeps your daemons up while taking up as little resources as possible. After all you probably want the resources of your server to be used by whatever daemons you are running rather than the thing that's supposed to make sure they are brought back up, should they die or misbehave.
Bluepill keeps your daemons up while taking up as little resources as possible. After all you probably want the resources of your server to be used by whatever daemons you are running rather than the thing that's supposed to make sure they are brought back up, should they die or misbehave.