This PR should resolve #42. Now, Django serves straight from the build directory as opposed to manually running Babel and Webpack, as suggested by @bl-nero. This means that now we have to run npm run build in the frontend directory first before running python manage.py runserver.
The build script has been updated to reflect this change.
This also has resulted in removing the associated Babel and Webpack files as well as a small change to package.json, removing the npm run dev script, which was responsible for running Babel and Webpack.
settings.py has been updated to include updates to the CORS settings, and requests from the same origin localhost have been whitelisted.
This PR should resolve #42. Now, Django serves straight from the
builddirectory as opposed to manually running Babel and Webpack, as suggested by @bl-nero. This means that now we have to runnpm run buildin thefrontenddirectory first before runningpython manage.py runserver.The build script has been updated to reflect this change.
This also has resulted in removing the associated Babel and Webpack files as well as a small change to
package.json, removing thenpm run devscript, which was responsible for running Babel and Webpack.settings.pyhas been updated to include updates to the CORS settings, and requests from the same originlocalhosthave been whitelisted.