pack
porter
Our great sponsors
pack | porter | |
---|---|---|
46 | 37 | |
2,373 | 4,089 | |
2.0% | 2.0% | |
9.5 | 9.9 | |
2 days ago | 4 days ago | |
Go | TypeScript | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
pack
- Différentes façons de déployer une application front faites en JS
-
K8s powered Git push deployments
I've recently found this quote by Kelsey Hightower:
"I'm convinced the majority of people managing infrastructure just want a PaaS. The only requirement: it has to be built by them."
Source: https://twitter.com/kelseyhightower/status/85193508753294540...
In the last few weeks, I've experimented a bit with Flux (https://fluxcd.io/), Tekton (https://tekton.dev/) and Cloud Native Buildpacks (https://buildpacks.io/) on how to provide K8s powered git push deployments without using a dedicated CI/CD server.
My project is still in early alpha stage and just a proof of concept :-) My vision is to expand it into an Open Source PaaS in the future.
Do you think the above quote is true? What does an open source PaaS need to be like in order to be accepted by software developers?
Some other projects have been discontinued in the past (like Flynn or Deis) or were created before the Kubernetes era.
Is it the right direction to provide a Heroku like solution based on K8s or is it better to provide an Open Source Infrastructure as Code library with building blocks to avoid everything from scratch?
-
Crafting container images without Dockerfiles
Although Dockerfiles have the benefit of migrating existing workloads to containers without having to update your toolchain, I definitely prefer the container-first workflow. Cloud Native [Buildpacks](https://buildpacks.io/) are a CNCF incubating project but were proven at Heroku. Buildpacks support common languages, but working on a Go project I've also had a great experience with [ko](https://ko.build/). Free yourself from Dockerfile!
-
Kubero : alternative à Heroku pour Kubernetes …
Cloud Native Buildpacks
-
The world outside of WordPress
It's big and overwhelming and sometimes scary. But you know what? It's also fun, engaging, and very refreshing. Because I'm a DevRel, I don't have many chances to focus on something particular. Still, I'm having a lot of fun exploring different CMSs (like Statamic, Craft, or Sanity), new approaches (at last, I understood why the headless approach is so important), and diving into tech I never used before (hello Buildpacks).
- Does anyone use any alternatives to Dockerfile for creating containers? Something with nicer syntax?
- Jetstack Paranoia: A New Open-Source Tool for Container Image Security
-
YAML Buildpack: Auto Validate Configuration Repositories
[5] https://buildpacks.io/
-
Devbox 📦 : Instant, easy, and predictable shells and containers
Devbox analyzes your source code and instantly turns it into an OCI-compliant image that can be deployed to any cloud. The image is optimized for speed, size, security and caching ... and without needing to write a Dockerfile. And unlike buildpacks, it does it quickly.
-
A selfhosted Heroku clone on your Kubernetes cluster
I had a short look into buildpacks.io . So I don't have a firm opinion yet. But as much i understand now, it really builds Container images. Kubero goes a different approach. The buildstep only compiles the project to a mounted volume, which is mounted readonly to the running container. Further more is the detection step unnecessary, since the dev knows what he wants to build and selects the buildimage. How ever, I'm still looking into it, so see if my project can profit from the great work there in any other way.
porter
-
Show HN: Hatchet – Open-source distributed task queue
Yep, we're backed by YC in the W24 batch - this is evident on our landing page [1].
We're both second time CTOs and we've been on both sides of this, as consumers of and creators of OSS. I was previously a co-founder and CTO of Porter [2], which had an open-core model. There are two risks that most companies think about in the open core model:
1. Big companies using your platform without contributing back in some way or buying a license. I think this is less of a risk, because these organizations are incentivized to buy a support license to help with maintenance, upgrades, and since we sit on a critical path, with uptime.
2. Hyperscalers folding your product in to their offering [3]. This is a bigger risk but is also a bit of a "champagne problem".
Note that smaller companies/individual developers are who we'd like to enable, not crowd out. If people would like to use our cloud offering because it reduces the headache for them, they should do so. If they just want to run our service and manage their own PostgreSQL, they should have the option to do that too.
Based on all of this, here's where we land on things:
1. Everything we've built so far has been 100% MIT licensed. We'd like to keep it that way and make money off of Hatchet Cloud. We'll likely roll out a separate enterprise support agreement for self hosting.
2. Our cloud version isn't going to run a different core engine or API server than our open source version. We'll write interfaces for all plugins to our servers and engines, so even if we have something super specific to how we've chosen to do things on the cloud version, we'll expose the options to write your own plugins on the engine and server.
3. We'd like to make self-hosting as easy to use as our cloud version. We don't want our self-hosted offering to be a second-class citizen.
Would love to hear everyone's thoughts on this.
-
Launch HN: Nullstone (YC W22) – An easier way to deploy and manage cloud apps
Co-founder of Porter (https://porter.run) here - we do not use Terraform under the hood. We moved away from an IaC based system earlier this year to better manage our users' infrastructure distributed across multiple cloud accounts. A decision that definitely turned out to be conveniently prescient :)
With this new system, we are also able to immediately reconcile drifts that occur in our user's infrastructure, which an IaC based system did not allow us to do.
-
Serving 250k Developers with One Support Engineer
Aptible hosts (and pays for) AWS resources on your behalf, similar to Heroku/Render/Railway. Last year, we built support for integrating Aptible into your own AWS account, but only a handful of existing customers are currently using that, and it's not available in the product by default. I'd be interested to learn why you prefer this model. If you're willing to chat about it, my email is in my profile.
Alternatively, have you checked out other PaaS-in-your-own-IaaS solutions like:
- https://www.flightcontrol.dev/
- https://coolify.io/ (OSS, not managed)
These might not meet all your needs, and I think they're all relatively new.
-
Ask HN: Who is hiring? (November 2022)
Porter (YC S20) | Full Time | Full-Stack Engineer | NYC or Remote | https://porter.run
Hey HN, I'm Alexander, co-founder of Porter. We're building Heroku in your own cloud - we let users link up their own AWS/GCP, point to the code they want to run, and then put the rest of the hosting process on autopilot (CI/CD, SSL, autoscaling, zero downtime deploys, infra monitoring, etc).
We're hiring NYC-based or remote engineers that are passionate about building tools for developers. As we're a fast-growing seed-stage startup, you should be comfortable with regularly shifting priorities and iterating at a very high (daily) velocity.
Tech stack: Go, Typescript, React, Kubernetes, AWS
If you'd like to take a look at our codebase, we're open source - check it out at https://github.com/porter-dev/porter.
Open positions:
- Kubernetes Engineer: https://www.workatastartup.com/jobs/45970
- Full-stack Engineer: https://www.workatastartup.com/jobs/43716
Please apply by sending an email to jobs [at] porter [dot] run or applying through https://www.workatastartup.com/jobs/43716.
-
Acorn: A lightweight PaaS for Kubernertes, from Rancher founders
How does this compare against https://porter.run/ ?
-
Ask HN: Are You Leaving Heroku?
Honestly you should checkout open source + self-host alternatives like porter (https://github.com/porter-dev/porter). I tried it in a project before and the developer experience was surprisingly good.
- Heroku: We’ve Heard Your Feedback
- Show HN: Algorithmic Trading for Everyone
-
Ask HN: Who is hiring? (March 2022)
Porter (YC S20) | Full Time | Full-Stack Engineer | Remote or NYC | https://porter.run
Hey HN, I'm Alexander, co-founder of Porter (https://porter.run). We're building Heroku in your own cloud. We let users link up their own AWS/GCP, point to the code they want to run, and then put the rest of the hosting process on autopilot (CI/CD, SSL, autoscaling, zero downtime deploys, infra monitoring, etc).
We're hiring engineers that are passionate about building tools for developers. If you have some experience with either Typescript or Go, or you're very interested in this space, we'd love to talk with you. As we're a fast-growing seed-stage startup, you should be comfortable with regularly shifting priorities and iterating at a very high (daily) velocity.
Some of the technical challenges we face:
* Abstracting Kubernetes - any PaaS spans a variety of use cases, so building a consistent and useful layer of abstraction requires constant awareness of the needs of many user profiles.
* Cloud Agnosticism - one of Porter's main benefits is that you get the same interface for managing services regardless of where you host. Our job is to reduce multi-cloud infrastructure complexity to a unified interface.
* Auto-Generated Frontend - each of our app/add-on templates uses a form.yaml file that programmatically generates a settings UI on the dashboard using a library of our own input primitives. Designing, expanding, and testing the functionality of these templates is non-trivial.
If this interests you, please apply by sending an email to jobs [at] porter [dot] run or applying through https://www.workatastartup.com/jobs/43716.
- Tools / software / resources library
What are some alternatives?
coolify - An open-source & self-hostable Heroku / Netlify / Vercel alternative.
kaniko - Build Container Images In Kubernetes
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
engine - The Orchestration Engine To Deliver Self-Service Infrastructure Faster ⚡️
kubevela - The Modern Application Platform.
rancher - Complete container management platform
helm-charts - Prometheus community Helm charts
jib - 🏗 Build container images for your Java applications.
CapRover - Scalable PaaS (automated Docker+nginx) - aka Heroku on Steroids
okteto - Develop your applications directly in your Kubernetes Cluster
porter - Porter enables you to package your application artifact, client tools, configuration and deployment logic together as an installer that you can distribute, and install with a single command.