Thanks for trying. I’ll reconnect the serial console and try flashing and booting a rpi0_2 image again and get back to you ..read more

Yeah, I’ve noticed that Ash can really do a lot, but that the documentation, especially when it’s outside of the default use cases can be a bit lacking at times. I guess that’s normal for projects that move relatively fast. I’d be happy to help out in any way to rectify that situation ..read more

Is it possible to use this with Phoenix Channels to define the request and response types ..read more

Would you mind if I copied the resvg_code into my package so that I could tweak it for my use case? I agree with you that Resvg shouldn’t try to be too generic. I promise I won’t bother you with questions regarding the modified code. I understand if you don’t want slightly modified versions of your code in other projects, though ..read more

This is definitely an area we intend to improve at some point. The tools are all there, it’s just a matter of providing the guidance of how to use them. I will let @jimsynz answer because he is much more familiar with AshAuthentication’s internals than I ..read more

You currently have to solve this in the update hook, I’ve accomplished this by storing the scroll position and then reapply it on update. Otherwise opening an issue would be a good idea, if you believe it’s a breaking change ..read more

I have a user resource that looks more or less like that one in the Ash Authentication getting started doc, with one added field: role. Role can be one of admin, merchant, client. Only admins should be able to log in via the web frontend, merchants and clients should only be able to register and “sign in” (that is, receive a token) only via a JSON API. At this time, I’m only interested in the password strategy. On the web side, everything works well (registration is disabled, I seed an initial admin, who can log in and create more admins, if needed). However, I cannot get authentication to wor ..read more

At first this was just an experiment if something like Babashka Pods could be implemented in Elixir. A proper library would need to consider edges cases and other production ready features like the ones you mention. So my vision for a future library would be: Pods tooling (pod installation and registry) handled by babashka, since a pod would work in babashka and elixir (and any other client that implements the protocol). Pod Core: handles input/output to a pod service (encoding and decoding messages, parsing the protocol responses) Pod Process Manager (optional): start the Pod services and pr ..read more

D4no0: A lot of things could be done, but this technology promises a turnkey solution (correct me if I’m wrong), so if the only thing it offers is a wrapper over 2 protocols, then I might as well go with a more widely used solution as there will be more support. nice… good choice. @clsource just showed a proof of concept of something that he likes I was interested in it too. in this topic no one is advocating for using it over grpc or any other solution. for me particularly it’s way better to use something like this to wrap a java sdk to deal with brazilian government and bank stuff instead ..read more

cjbottaro: The button has to be of type=submit Yes, type="submit" is the default. That is why you rarely see that but often see <button type="button">, the latter meaning it’s just a “dumb” button. It is what it is cjbottaro: I’m always amazed and embarrassed about how little I know about HTML for being a “web developer”… I felt the same way when someone first pointed this out to me, and I like to fancy myself as someone who knows HTML quite well But I still keep learning little things I feel I “should” have known already. The latest was that for videos to auto-play on some devi ..read more