←back to thread

1226 points bishopsmother | 1 comments | | HN request time: 0.205s | source
Show context
soperj ◴[] No.35045937[source]
For django, they should really contribute to 2 scoops django cookie cutter program, so that you can get an out of the box django instance that can just deploy to Fly.io.
replies(4): >>35046302 #>>35046664 #>>35046700 #>>35048622 #
mixmastamyk ◴[] No.35046302[source]
May be wrong, but they seem to be very focused on interesting stacks like Elixir and RoR while building on Go/Rust. The corollary being neglect of the bread/butter stacks with high market share, like Python and Java/JavaScript. Don't think I've seen a blog post discussing those three beyond a passing mention?

Not the end of the world, but mildly disappointing. At least they are all in with Postgres and Linux, a great foundation.

replies(4): >>35046409 #>>35046489 #>>35046547 #>>35048581 #
jjtheblunt ◴[] No.35046409[source]
I thought the only thing their tech stack was all in on was docker images being rewritten to run on firecracker as a substrate.

is it not agnostic about things like Elixir etc, at the tech level, though they've got super nice documentation for those tools you mentioned?

replies(1): >>35046557 #
ilaksh ◴[] No.35046557[source]
What's necessary to change for them to run on Firecracker?
replies(1): >>35046808 #
ign0ramus ◴[] No.35046808[source]
Here's a post explaining how they do it https://fly.io/blog/docker-without-docker/
replies(1): >>35047189 #
1. ilaksh ◴[] No.35047189[source]
Yeah, saw that before. I thought he was saying you have to change your Dockerfiles to use them with fly.io. Just misinterpreted that sentence.