otomi-core
piku
Our great sponsors
otomi-core | piku | |
---|---|---|
75 | 26 | |
2,139 | 2,578 | |
1.5% | 5.6% | |
9.6 | 6.9 | |
1 day ago | 12 days ago | |
Mustache | Python | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
otomi-core
- Otomi – Self-Hosted PaaS for Kubernetes
- Self-hosted Kubernetes-based Heroku alternative
-
What is a self-hosted Kubernetes-based PaaS?
An example of a self-hosted Kubernetes-based PaaS is Otomi. Install Otomi on your Kubernetes cluster, compose your platform (by activating the required capabilities) and build, deploy and expose apps in just a couple of minutes. Heroku, but Kubernetes native and running on your own cluster.
- GitHub - redkubes/otomi-core: Self-hosted PaaS for Kubernetes
- GitHub - redkubes/otomi-core: Self-hosted & Git-based PaaS for Kubernetes
-
Add developer- and operations-centric tools, automation and self-service on top of Kubernetes
This video shows some of the new features of Otomi version 0.19.0 that will be released in Week 11 2023. Follow us on GitHub and be the first to try it out: https://github.com/redkubes/otomi-core
-
Selfhosted PaaS? (No dokku pls)
Otomi
- Self-hosted DevOps Platform as a Service for Kubernetes
-
Kubernetes is only a multi-node cluster kernel
Kubernetes is 'only' a multi-node cluster kernel. Some call it the Linux of the cloud.
And because K8s is only a kernel, there are now over 2000+ (open source) projects, all adding some extra functionality to it. Be it for observability, security, or networking. But all of these projects don't really collaborate and end-users don't ask for maturity of individual projects, they want sets/stacks of projects that integrate well.
Now every company has created some Stack with applications and configurations for Kubernetes, all trying to reinvent the wheel and spending an often shocking $ in doing so.
So here is my take:
- Let's create a new category in the Cloud Native Computing Foundation (CNCF) landscape and call it Integrated Stacks for K8s
- To be accepted, a stack needs to provide an open integration framework for other projects to add/integrate their apps
- Just like aLinux distro, each stack is ideal for some specific use case(s)
- A stack can be installed in one run, contains integrated apps that work out-of-the-box, has a (web) UI that acts as a desktop environment to provide easy and secure access to all features. Call it a new user experience for Kubernetes
Wouldn't it be great to have a list of all Kubernetes stacks available that everyone can use (and contribute to)? Just like (in the Linux analogy) you can choose between Linux Mint, Fedora, or Ubuntu.
We already created the first: https://github.com/redkubes/otomi-core
piku
-
Show HN: Hancho – A simple and pleasant build system in ~500 lines of Python
I like it. I wrote Piku (https://github.com/piku/piku) with much the same interest in fixing some of my pains, so I get where you're coming from with this. Will drop it into one of my current projects to build ESP32 binaries :)
-
Gokrazy Is Cool
I never had any serious issue with SD cards since the Pi 2B (and I've kept Pis running for years).
Anyway, for those wanting to deploy more generic apps, that is why I initially wrote https://github.com/piku/piku - you still have to flash the OS (and rpi-imager does that with sane defaults these days), but once you're done you have Heroku-like deployments for any language runtime you install on the Pi.
I also have https://github.com/rcarmo/ground-init, a cloud-init like shim that simplifies setting up machines (I'm a big fan of cloud-init, but since Raspbian doesn't support it and Ubuntu on ARM requires some fiddling to make it work I decided it wasn't too hard to roll my own).
(I probably should look into glueing that into rpi-imager, but there is are only so many hours in the day...)
-
Show HN: Local development with .local domains and HTTPS
I automated that away a long time ago: https://github.com/piku/piku/blob/master/piku.py#L814
-
Tool to deploy docker images from github repos?
Piku https://github.com/piku/piku
-
Stupid question: Why not use 'baremetal' OS instead of docker containers to run web apps?
So, stupid question: why couldn't I just use the 'baremetal' OS provided by Hetzner, install Postgres, Redis & node, create a separate db for each app, and run each app with https://github.com/piku/piku on a different port? For backups, I'll setup crontab to dump dbs locally and to S3.
-
Selfhosted PaaS? (No dokku pls)
piku?
- How do you deploy your side-projects?
- Ask HN: What's Your Proudest Hack?
- Piku
-
Comparing selfhosted Heroku alternatives
Piku https://github.com/piku/piku
What are some alternatives?
k3os - Purpose-built OS for Kubernetes, fully managed by Kubernetes.
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
charts - TrueNAS SCALE Apps Catalogs & Charts
RaspberryPi-Note - Raspberry Pi note
k8s-gitops - GitOps principles to define kubernetes cluster state via code
awesome-home-kubernetes - ⚠️ Deprecated: Awesome projects involving running Kubernetes at home
quickstart - Quickstarts to provision Kubernetes with Otomi
awesome-paas - A curated list of PaaS, developer platforms, Self hosted PaaS, Cloud IDEs and ADNs.
helm-charts - Temporal Helm charts
flyctl - Command line tools for fly.io services
ingress-nginx - Ingress-NGINX Controller for Kubernetes
containers-roadmap - This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).