Most active commenters
  • ilaksh(3)

←back to thread

1226 points bishopsmother | 13 comments | | HN request time: 1.133s | source | bottom
1. 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 #
2. 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 #
3. 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 #
4. ◴[] No.35046489[source]
5. ilaksh ◴[] No.35046547[source]
You can use any Docker image.
6. ilaksh ◴[] No.35046557{3}[source]
What's necessary to change for them to run on Firecracker?
replies(1): >>35046808 #
7. nilsbunger ◴[] No.35046664[source]
Their problem right now isn't adding more customers - they seem to have more than they can handle!

If I were them I'd focus as many resources as possible on making the stack rock-solid, and away from acquiring more customers or adding more capabilities.

In fact I'd try to down-scope some features if at all possible, like the example they give of disabling app deploys while they're doing platform updates.

We use fly.io at a small scale and it's worked really well for us, but the money is in customers at a larger scale who must have 100% reliability.

8. llimllib ◴[] No.35046700[source]
https://github.com/ehmatthes/django-simple-deploy will deploy to fly (or platform.sh) out of the box, should be pretty much the experience you're describing
replies(1): >>35046822 #
9. ign0ramus ◴[] No.35046808{4}[source]
Here's a post explaining how they do it https://fly.io/blog/docker-without-docker/
replies(1): >>35047189 #
10. soperj ◴[] No.35046822[source]
thank you!
11. ilaksh ◴[] No.35047189{5}[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.
12. tomwojcik ◴[] No.35048581[source]
I don't disagree with you, but they tweeted

> We’ll readily admit our docs still have a Django-shaped hole in them.

https://twitter.com/flydotio/status/1578039196618575874?t=nu...

13. tomwojcik ◴[] No.35048622[source]
I needed a cookie cutter for my side projects so I've created one for sqlite that I actively use and a similar one for postgres. Both are very basic, contributions welcome.

Sqlite https://github.com/tomwojcik/django-fly-sqlite-template

Psql https://github.com/tomwojcik/django-fly-postgres-template