elixir-secure-coding
An interactive cybersecurity curriculum designed for enterprise use at software companies using Elixir (by podium)
real world example app
Exemplary real world application built with Elixir + Phoenix (by gothinkster)
elixir-secure-coding | real world example app | |
---|---|---|
1 | 2 | |
551 | 870 | |
1.1% | - | |
2.9 | 0.0 | |
4 months ago | almost 2 years ago | |
Elixir | Elixir | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
elixir-secure-coding
Posts with mentions or reviews of elixir-secure-coding.
We have used some of these posts to build our list of alternatives
and similar projects.
real world example app
Posts with mentions or reviews of real world example app.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Phoenix namespacing conventions
After that, you're left with everything else in your application, much of which is interrelated on the data level. Using this repo as an example, you find that it has Accounts and then Blog as the primary namespaces (which make sense), which then leaves you with blog.ex which is a file containing a ton of database reading/writing/helper functions for all these different entities in the namespace (this is how the generators will also scaffold things, continuing to pile on the functions). It feel strange to me to have one giant file that forever grows proportional to the size of the namespace with so many concerns. Is it a good idea to split these things out (particularly when the ecto models aren't responsible for database queries in Pheonix) or am I just thinking about this the wrong way??
-
Phoenix
Getting Id token - here is some example: https://github.com/gothinkster/elixir-phoenix-realworld-example-app