React-Django | Simple setup for a React-Django web app | Frontend Framework library

The issue was solved with the recent update 0.11 of @usedapp/core library.

The homepage does not have a proper URL or path defined.

For example, you can go here:

https://mangya.herokuapp.com/administrator/

Or here

https://mangya.herokuapp.com/api

...As they are valid URLs.

Your blank 'homepage' path is not listed so there is no view being hit thus you get the error.

To fix this you need to change your urls.py in MyBlog to look like this:

i dont know Django but in my React i import: import ArrowForwardIosIcon from '@material-ui/icons/ArrowForwardIos';

if you install it like this: npm i @material-ui/icons

Try to replace:

I made it work under development settings. Here are the steps that I followed

First, in the project-level urls.py, add staticfiles_urlpatterns to urlpatterns

Welcome to the community!

I reproduced your example and made it work fine. I forked your repository, made some changes to js files and package.json and added Dockerfiles (you can see this commit here

Since I didn't change database settings in settings.py I attached it as a configMap to backend deployment (see here how it's done). Config map was created by this command:

kubectl create cm django1 --from-file=settings.py

The trickiest part here is to use your domain name kubernetes.docker.internal and add your port with /backend path to environment variables you're passing to your frontend application (see here)

Once this is done, it's time to set up an ingress controller (this one uses apiVersion - extestions/v1beta1 as it's done in your example, however it'll be deprecated soon, so it's advised to use networking.k8s.io/v1 - example of a newer apiVersion is here):

First maybe some clarification :-)

The "Media" directory is used for content uploaded for example by a user. So it's more a dynamic content, not static. Or at least not static with every instance of your service. Therefore it's usually also not shipped with your application. Details in the django documentation

Also check settings documentation about MEDIA_ROOT

I assume in your settings you something like MEDIA_ROOT = "build/static/media/" or something similar, which results in the conflict.

If you want to use "media" files, hence user uploaded files, you need a different storage on Heroku anyway. Heroku Dynos have a ephemeral filesystem which means you get a fresh copy of your instance once a day, which results in loss of all that data you stored during the life-time of the instance.

To solve this this problem you can store those media files for example on AWS S3. Django has an awesome addon, which replaces the filesystem storage with AWS S3 storage. Which means the API from your point of you as a Developer does not change at all.

Here is a Django Development and PROD setting example with django-s3-storage:

Development example config (nothing special, no S3):

When you start webpack with webpack dev server (which you do with webpack serve), it compiles everything into memory and serve from there. If you want to emit files you, probably don't need dev server, so just startgin webpack watch would be sufficient. If you need dev server and want to emit files, you can set it with this writeToDisk option

i was working with the docker toolbox which includes oracle virtual box. There you can see your docker machine settings. just stop your docker machine with command in docker quickstart terminal