yumm
Hi all! I’m new to elixir and phoenix and am trying to run this project:
https://github.com/chvanikoff/reph2
I want to convert an existing react app (or at least the rest api for the database to elixir but every example project I find on Github has some sort or error regarding ecto. I’ve tried all the examples posted in https://forum.elixirforum.com/t/user-authentication-in-phoenix/118/81 but encounter similar errors to this:
could not compile dependency :phoenix_ecto, "mix compile" failed. You can recompile this dependency with "mix deps.compile phoenix_ecto", update it with "mix deps.update phoenix_ecto" or clean it with "mix deps.clean phoenix_ecto"
I’ve tried cleaning all my mix packages as well as mix.update --all.
Are all these projects just dead or am I missing something?
Also if anyone has suggestions of a working example of a elixir server with authentication (ideally with react as well) please do hesitate to share.
Thank you to the elixir developers I can see the magic in the bottle but still feel like I’m taping on the glass.
Thank you for any/all suggestions/ideas/setting me straight
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Courses that'll move you from confusion to "Aha, now I get it!"
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Most Liked- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
yurko
This one seems to work, I’ve just tested it locally GitHub - chernyshof/react-phoenix-users-boilerplate: Elixir/Phoenix + React + users template/boilerplate. · GitHub and it uses Phoenix 1.3
One thing to note is that you’d have to use
admin@admin.comand not justadminas stated in the readme in order to log in.yurko
Yes, you need postgres and then you need to set up the connection, edit your dev config and set up username, password etc, s. react-phoenix-users-boilerplate/config/dev.exs at master · chernyshof/react-phoenix-users-boilerplate · GitHub
Your local database doesn’t have to be secure unless it’s open to the outside world. If you want to set the password you can do something like this:
NobbZ
Even though I can compile the dependencies on my system (Arch linux), it fails currently with the router and prints out about a billion of warnings.
Also the particular example you posted is written in phoenix 1.1, so it will give you a false sense of how things are done today.
You should search for examples that use a more current phoenix (1.3).
Sadly I can’t give you any links to small example projects, but only to a fully grown application: The hex.pm website.
Last Post!
yumm
@voger your correct. I was able to duplicate my project and use ‘boilerplate_dev’ as database name. please ignore the previous version of this reply as that error was simply due to a node.js server interfering with phoenix.