sysbox VS streamlit

Yes, I first learned this and the name "splay" from CFengine, back in the day.

I put together a small busybox-like collection of sysadmin tools, and one of the subcommands is "splay" to sleep for a random amount of time. It's one of those things that is useful surprisingly often, even outside cron.

https://github.com/skx/sysbox

I remember in 1999 there was a project to reimplement a bunch of these tools in perl:

https://perlpowertools.com/

I even contributed a little, back then. I guess writing basic versions of "ls", for example, is trivial. But there's a lot of work getting all the tools done, with all the flags implemented and behaving as expected.

I guess there are tools like busybox, toybox, and similar, which also implement a lot of "stuff" to varying degrees of completion. From my side the biggest takeaway from those projects is the sheer convenience of deploying a single binary and installing symlinks to change functionality.

I replicated something similar with my sysbox project, collecting tools together in one golang binary with various subcommands:

https://github.com/skx/sysbox

I use at least one of those tools on a daily basis, though I suspect they're not so universally useful.

If you've got perl installed you'll might have a "GET" binary present, mine is /usr/bin/GET, which comes with the WWW-module.

Although this is written in portable perl, rather than being compiled, so the static vs. dynamic choice doesn't really mean much it is a simple alternative.

Otherwise I built a simple busybox-inspired collection of tools, written in golang, which includes a simple HTTP client too:

https://github.com/skx/sysbox

Those are just a couple of examples, I'm certain there are multiple other choices out there. But I guess curl is ubiquitous enough that most people just use it directly, and add it when missing!

That's pretty cool.

I wrote something similar in my static collection of sysadmin tools - https://github.com/skx/sysbox - In my simple pre-processor I only allow two special things:

#include "file/goes/here"

I bundled together a small collection of sysadmin/scripting-tools here:

https://github.com/skx/sysbox

Those are probably amongst the things that I use most often which are non-standard.

I used to have very full ~/bin, and ~/$(hostname), directories. In the end I pared them back and started bundling things together in one binary.

The end result is very similar to this approach, I run "sysbox blah", or "sysbox help", and use integrated subcommands.

Very helpful and makes deployment easy by having only a single binary:

https://github.com/skx/sysbox

Not bash/shell, but similar and useful idea to experiment with.

I support that in my sysbox utility-box, via the subcommands processor, and it is very helpful.

Streamlit (https://streamlit.io/)

Does it need to be live (i.e when database or underlying spreadsheet updates does it need to be reflected in real time on the dashboard) or are you ok with static display.

Live updating data is a pain I've messed around using javascript to force refresh html iframes on a timer. But I was never really satisfied with this. I've heard you can do things with websockets but that is starting to get too complicated for me (I'm not a programmer).

For static stuff one of the data scientists in my org pointed me to Streamlit (https://streamlit.io/) it's a python package I found very easy to use. Can easily combine SQL with CSV imports and display them all on one dashboard. Can use forms toggle butotns etc to control the display.

Note that there are many tools that make this easier/simpler to prototype, including chainlit, streamlit, etc… The backend API we built is amenable to interacting with them as well.

2.-Go to https://streamlit.io, log in, and create a new app from your GitHub repository.

Developed using Langchain and Streamlit technologies for enhanced performance.

Hello,

Have you ever seen the https://streamlit.io/ ? I think this is what you are looking for.

While building dashboards in Streamlit, I found myself really missing Buefy's (Bulma) modern web components.

Specially due to the inability to add new values to Streamlit's multiselect [1], some missing controls like a polished image carousel [2] or a highly customizable data table.

Long story short, we put together streamfy (Streamlit + Buefy) as an MIT licensed project in GitHub to bring Buefy to Streamlit.

Demo: https://streamfy.streamlit.app

All the form components are implemented, missing half of other non-form UX components. There is plenty of room for PRs, testing, feedback, documentation, example, etc.

Please send issues and contributions to GitHub project [3] and general feedback to X / Twitter [4]

Thanks!

[1] https://github.com/streamlit/streamlit/issues/5348

Here's your savior, let's welcome Streamlit.

Looks cool. How do you see this differing from streamlit? https://streamlit.io/

Imagine you have an AI-powered personal alerting chat assistant that interacts using up-to-date data. Whether it's a big move in the stock market that affects your investments, any significant change on your shared SharePoint documents, or discounts on Amazon you were waiting for, the application is designed to keep you informed and alert you about any significant changes based on the criteria you set in advance using your natural language. In this post, we will learn how to build a full-stack event-driven weather alert chat application in Python using pretty cool tools: Streamlit, NATS, and OpenAI. The app can collect real-time weather information, understand your criteria for alerts using AI, and deliver these alerts to the user interface.