-
Notifications
You must be signed in to change notification settings - Fork 531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Where in the docs does it explain how to build the front-end for a local RealApp backend? #74
Comments
It looks like the API URL is hardcoded here: elm-spa-example/src/Api/Endpoint.elm Line 56 in c8c3201
|
I found that and changed it. I then rebuilt the elm app, however for a reason I cannot understand it still points to the productionready.io target. I attempted to clear the app data, etc. No success. |
It will be hard to help without seeing your code. Do you have it on Github maybe? |
I have made no other changes to the github project of this issue
…On Fri, Apr 12, 2019, 6:44 AM Sidney Nemzer ***@***.***> wrote:
It will be hard to help without seeing your code. Do you have it on Github
maybe?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#74 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADJ46WwQR4imuhDdVqAMhuaA_kaFBZVaks5vgA8_gaJpZM4cqU3r>
.
|
All I did was run a Django server with the RealWorld API on localhost:8000
I want the front end to talk to it.
…On Fri, Apr 12, 2019, 1:51 PM Dean Kayton ***@***.***> wrote:
I have made no other changes to the github project of this issue
On Fri, Apr 12, 2019, 6:44 AM Sidney Nemzer ***@***.***>
wrote:
> It will be hard to help without seeing your code. Do you have it on
> Github maybe?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#74 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ADJ46WwQR4imuhDdVqAMhuaA_kaFBZVaks5vgA8_gaJpZM4cqU3r>
> .
>
|
Here is the only code change I have made: dnk8n@ac8d039 Can anyone shed some light here? |
Some further information. To start the web-server I do: and get the following output:
But then I get the following display on the http://localhost:8080 |
I guess I should state that I am running the RealWorld API from http://localhost:8000. It is the Django backend found at: https://github.com/gothinkster/django-realworld-example-app I have made no modifications there at all. The API is available (as can be see in the image above, 200 success codes) |
Note: I also tried: The output is as follows:
and
The website looks similar, although I think another problem has crept in here, because last week your master branch displayed correctly and now it is not. Seems it is not able to find the JS and/or the CSS? |
@dnk8n Try updating your whitelist in the Django backend, that might help |
Try https://conduit.productionready.io/api if you’re just wanting to kick the tyres. Interestingly it seems the database/backend for this Elm front-end is shared with the other ‘official’ Real World / Conduit demo .. makes sense since the Elm one is just hosted with (static) Netlify |
I had the same issue but realized that chrome was aggressively caching content. Ctrl+f5 forced it to reload. |
I may be missing something obvious, but I would expect this in the README.txt of the repo.
The text was updated successfully, but these errors were encountered: