containers-roadmap
piku
Our great sponsors
containers-roadmap | piku | |
---|---|---|
80 | 26 | |
5,137 | 2,570 | |
0.6% | 5.3% | |
2.0 | 6.9 | |
9 months ago | 5 days ago | |
Shell | Python | |
GNU General Public License v3.0 or later | 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.
containers-roadmap
-
General Availability of the AWS SDK for Rust
Thanks for showing up and answering questions. Congratulations on the release.
What kind of plans for support of Rust's evolving async ecosystem?
Any particular reason why the public roadmap does not show the columns similar to "Researching", "We're Working On It" like the other similar public AWS Roadmaps? See example for Containers: https://github.com/aws/containers-roadmap/projects/1
Would be nice to have fully working examples on Github, for most common scenarios across most AWS services. This is something that historically
-
Architecting for Resilience: Crafting Opinionated EKS Clusters with Karpenter & Cilium Cluster Mesh — Part 1
Second, We will only rely on one managed node group, but we will leverage Karpenter; however, karpenter needs to be deployed on a node. (This may change soon once the Karpenter is available on the EKS Control Plane.) [EKS] Karpenter inside control plane · Issue #1792 · aws/containers-roadmap
-
Running a Web Application with 100% AWS Fargate Spot Containers 🤘
As written in the AWS documentation, during periods of extremely high demand, Fargate Spot capacity might be unavailable. In concrete terms, if your ECS service is set up to execute tasks in 100% Spot, there is a risk of running out of capacity. A workaround has been created in the hope that one day this issue will be implemented by the AWS team. This workaround allows you to set up two ECS services :
-
Kubernetes SidecarContainers feature is merged
Deploying Fargate with CDK has to have been the most pleasant developer experience I have ever had with any product so far.
If image caching becomes a reality with Fargate I can't imagine a need to ever use anything else
- AWS Config supports recording exclusions by resource type
- Announcing pull through cache for registry.k8s.io in Amazon Elastic Container Registry
-
EKS/Spot vs EKS Fargate/Spot?
Eks Fargate doesn't support spot yet https://github.com/aws/containers-roadmap/issues/622
- audit logging of the master plane in EKS
-
How to use Podman inside of a container
Until podman could be used with AWS ECR/ECS it's pretty much moot in my case: https://github.com/aws/containers-roadmap/issues/626
- How to keep 100% availability with a single ec2 spot instance?
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?
eks-nvme-ssd-provisioner - EKS NVMe SSD provisioner for Amazon EC2 Instance Stores
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
kube-fledged - A kubernetes operator for creating and managing a cache of container images directly on the cluster worker nodes, so application pods start almost instantly
RaspberryPi-Note - Raspberry Pi note
netshoot - a Docker + Kubernetes network trouble-shooting swiss-army container
awesome-home-kubernetes - ⚠️ Deprecated: Awesome projects involving running Kubernetes at home
kraken - P2P Docker registry capable of distributing TBs of data in seconds
awesome-paas - A curated list of PaaS, developer platforms, Self hosted PaaS, Cloud IDEs and ADNs.
juicefs - JuiceFS is a distributed POSIX file system built on top of Redis and S3.
flyctl - Command line tools for fly.io services
copilot-cli - The AWS Copilot CLI is a tool for developers to build, release and operate production ready containerized applications on AWS App Runner or Amazon ECS on AWS Fargate.
nixpacks - App source + Nix packages + Docker = Image