4 ms·

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 t

by soperj 4y ago

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.

mixmastamyk 4y ago
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.
- jjtheblunt 4y ago
  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?
  - ilaksh 4y ago
    What's necessary to change for them to run on Firecracker?
    - ign0ramus 4y ago
      Here's a post explaining how they do it https://fly.io/blog/docker-without-docker/ https://fly.io/blog/docker-without-docker/
      - ilaksh 4y ago
        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.
- deleted 4y ago
  [deleted]
- ilaksh 4y ago
  You can use any Docker image.
- tomwojcik 4y ago
  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=nudTtrPJKotygYa9f0F87A&s=19 https://twitter.com/flydotio/status/1578039196618575874?t=nu...
nilsbunger 4y ago
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.
llimllib 4y ago
https://github.com/ehmatthes/django-simple-deploy 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
- soperj 4y ago
  thank you!
tomwojcik 4y ago
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 https://github.com/tomwojcik/django-fly-sqlite-template Psql https://github.com/tomwojcik/django-fly-postgres-template https://github.com/tomwojcik/django-fly-postgres-template

by soperj 4y ago

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.

mixmastamyk 4y ago

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.

jjtheblunt 4y ago
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?
- ilaksh 4y ago
  What's necessary to change for them to run on Firecracker?
  - ign0ramus 4y ago
    Here's a post explaining how they do it https://fly.io/blog/docker-without-docker/ https://fly.io/blog/docker-without-docker/
    - ilaksh 4y ago
      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.
deleted 4y ago
[deleted]
ilaksh 4y ago
You can use any Docker image.
tomwojcik 4y ago
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=nudTtrPJKotygYa9f0F87A&s=19 https://twitter.com/flydotio/status/1578039196618575874?t=nu...

nilsbunger 4y ago

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.

llimllib 4y ago

https://github.com/ehmatthes/django-simple-deploy 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

soperj 4y ago
thank you!

tomwojcik 4y ago

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 https://github.com/tomwojcik/django-fly-sqlite-template Psql https://github.com/tomwojcik/django-fly-postgres-template https://github.com/tomwojcik/django-fly-postgres-template