Does the app have node name(s) set up based on this scheme (which the connection guide assumes)?
If you ssh to the node and look up its node name (fly ssh console, app/bin/youapp remote, the name should be in the iex prompt, or you could run Node.self) - is it the same that you’re using in the Livebook connection param?
(1) “node name” → Thx for pointing this out. That was not obvious to me. Made the changes and redeployed
(2) “ssh console” → cool Node.self produces exactly the same output that I am using for the Name connection parameter in Livebook (IE: node name@ipv6)
I scrolled past this in the guide: ERL_AFLAGS="-proto_dist inet6_tcp" livebook server --name livebook@127.0.0.1
It works now! Not sure if (1) was necessary, but thanks a lot for chiming in!!
Sorry for the confusion, I thought you were using fly.io’s Livebook launcher - it would’ve been able to connect to any node (well, provided the right cookie and all that) as long as both apps are in the same organization (= share the same internal network).
** (File.Error) could not stream “/Users/bla/someFile”: no such file or directory
Does Livebook give you a convenient way to utilize the local file system?
IE: I am doing some exploratory testing with my app. I do not want to constantly deploy and move files to the container and run stuff like seeds.exs.
I would like to just consume local csv/json files and pipe the data to the production app
(alternatively: might just use kino and copy and paste the data into an input field)