Learnings from One Year of Building an Open Source Elixir Application
1–10 of 24 posts
Re: Learnings from One Year of Building an Open Source Elixir Application
#2Having a sign up button or perhaps context or text on the site might've been helpful...
Re: Learnings from One Year of Building an Open Source Elixir Application
#3Having a sign up button or perhaps context or text on the site might've been helpful...
You're completely right, it seems a little counterintuitive but one thing I learned early on while building a different community site (Designer News) was the way to build a wholesome community was to be invite only in the beginning. That and real first and last names.
Which means it's a poor user experience. Sorry for the trouble, I wonder if any folks have better ideas here?
Re: Learnings from One Year of Building an Open Source Elixir Application
#4Having a sign up button or perhaps context or text on the site might've been helpful...
You're completely right, it seems a little counterintuitive but one thing I learned early on while building a different community site (Designer News) was the way to build a wholesome community was to be invite only in the beginning. That and real first and last names. Which means it's a poor user experience. Sorry for the trouble, I wonder if any folks have better ideas here?
Not a single page even mentions that it's invite only =/. Context for that would be a good start heh
Re: Learnings from One Year of Building an Open Source Elixir Application
#5I really enjoyed this article and the one about the ambient notification cube! Well-written. It's nice to hear someone else talk about how hard it it to stay consistent with worthwhile projects while maintaining a day job. Congrats on sticking it out!
Re: Learnings from One Year of Building an Open Source Elixir Application
#6One of the interesting things about the Elixir/Phoenix community is that building your own authentication system seems to be encouraged. Even if you're using one of the plugs available (guardian?) you still have to do a ton of manual lifting.
Re: Learnings from One Year of Building an Open Source Elixir Application
#7One of the interesting things about the Elixir/Phoenix community is that building your own authentication system seems to be encouraged. Even if you're using one of the plugs available (guardian?) you still have to do a ton of manual lifting.
This seems to be the case in many places outside of Rails. I know that Clojure, at least, seems to encourage implementing things yourself by way of leveraging smaller libraries and modules.
Auth is genuinely hard, and turnkey solutions often aren't enough.
Re: Learnings from One Year of Building an Open Source Elixir Application
#8Great writing. Elixir/Phoenix has been on my radar for learning something exciting considering it is faster out of the box and can handle tons of concurrent connections.
For the lazy, here is the github link from this article:
Re: Learnings from One Year of Building an Open Source Elixir Application
#9One of the interesting things about the Elixir/Phoenix community is that building your own authentication system seems to be encouraged. Even if you're using one of the plugs available (guardian?) you still have to do a ton of manual lifting.
This seems to be the case in many places outside of Rails. I know that Clojure, at least, seems to encourage implementing things yourself by way of leveraging smaller libraries and modules. Auth is genuinely hard, and turnkey solutions often aren't enough.
Let's not also forget that lots of projects people are using Phoenix for are APIs (either for mobile apps or single page web applications). Because of that, it makes sense to glue together smaller libs to match your house style for how you want that auth contract to work.
Re: Learnings from One Year of Building an Open Source Elixir Application
#10One of the interesting things about the Elixir/Phoenix community is that building your own authentication system seems to be encouraged. Even if you're using one of the plugs available (guardian?) you still have to do a ton of manual lifting.
It really depends what you are going for. There are libraries out there that are pluggable for lots of different auth mechanisms like https://github.com/ueberauth/ueberauth
If you want something like Devise from the Rails world, there is also Coherence. https://github.com/smpallen99/coherence