How to resolve the circular dependency with auth_plug
?
#170
Labels
awaiting-review
An issue or pull request that needs to be reviewed
chore
a tedious but necessary task often paying technical debt
discuss
Share your constructive thoughts on how to make progress with this issue
question
A question needs to be answered before progress can be made on this issue
technical
A technical issue that requires understanding of the code, infrastructure or dependencies
First, let me make it clear that what I am trying to do is deploy this
auth
app at my own domain: https://authix.org.This code base depends on
auth_plug
, as can be determined frommix.exs
:But the instructions for
auth_plug
are clear that in order for it to work you have to first get anAUTH_API_KEY
: https://github.com/dwyl/auth_plug#2-get-your-auth_api_key-But, the instructions for getting the
AUTH_API_KEY
tell me to go to URL where theauth
app is deployed and get anAUTH_API_KEY
.But that is circular because what I am trying to do is to deploy this
auth
app to a domain in the first place. How can I get theAUTH_API_KEY
if I can't deploy the app that gives me theAUTH_API_KEY
?Should I just make up an
AUTH_API_KEY
? Should I just get anAUTH_API_KEY
from https://dwylauth.herokuapp.com even though I don't want anything to do with that domain and am trying to deploy theauth
app to https://authix.org?Is it the intention of the authors of this
auth
app that it should be possible for someone to deploy it to a domain of their own choosing?The text was updated successfully, but these errors were encountered: