Elixir support improvements and Dictaphone Deep Dive Demo Docs

Fresh Produce
1

New with flyctl v0.2.126

Demo:

fly launch --from https://github.com/fly-apps/phoenix-dictaphone
fly launch --attach --from https://github.com/rubys/cog-whisper
fly deploy

The specific changes that made this possible:

  • Deploy redis if redis is detected in mix.exs
  • Deploy tigris if ex_aws_s3 is detected in mix.exs

That brings the number of working dictaphone demos to five. Check them out at Deep dive demo.

1 Like
2

Thanks for the update… It was a little surprising how short the patch was—really only a couple of lines.

It seems like the m × n problem has now mostly been solved for these attachment-style auxiliaries…

Might there be scope for eventually having similar consolidations w.r.t. helpers that run “underneath” the app—so to speak? People could publish Git repositories (à la --from) that would handle just the LiteFS slice or just the SSH+rsync aspect. It would be handy if those could be paired with fly.toml extensions as well:

[[mounts]]
  be_litefs = true
  source = "data"
  destination = "/var/lib/litefs"

Or…

[[mounts]]
  replication = "rsync"
  source = "vaultwarden"
  destination = "/data"
  interval = "15m"

It seems like you were maybe contemplating something along these lines back when Kamal first came up:

https://community.fly.io/t/run-an-ssh-server/17767

It’s otherwise daunting to consider doing things for all m frameworks…

3

The feature you are describing is pretty much what K8S sidecars provide: Sidecar Containers | Kubernetes

All I feel comfortable confirming at this point is that it is a “known requirement”. When or if it will land, or whether or not it will be available separate from FKS isn’t something I can confirm beyond saying that it is being looked at.

1 Like