React in Django or React as a standalone?Does Django scale?Loop inside React JSXHow to allow for webpack-dev-server to allow entry points from react-routerProgrammatically navigate using react routerreact routing and django url conflictHow to integrate Vue.js with DjangoDjango react renderIssue running React App on Django server with webpackCommunication between Django and ReactDjango rest-framework with react - blank page on frontend
Shrinkwrap tetris shapes without scaling or diagonal shapes
Is there a way to get a compiler for the original B programming language?
How to creep the reader out with what seems like a normal person?
How to make a pipeline wait for end-of-file or stop after an error?
What does the "ep" capability mean?
Will tsunami waves travel forever if there was no land?
With a Canadian student visa, can I spend a night at Vancouver before continuing to Toronto?
What makes accurate emulation of old systems a difficult task?
Why do games have consumables?
Combinable filters
How do I deal with a coworker that keeps asking to make small superficial changes to a report, and it is seriously triggering my anxiety?
Stop and Take a Breath!
How can Republicans who favour free markets, consistently express anger when they don't like the outcome of that choice?
How can I place the product on a social media post better?
How to pronounce 'C++' in Spanish
French for 'It must be my imagination'?
Why was Germany not as successful as other Europeans in establishing overseas colonies?
How to solve constants out of the internal energy equation?
US visa is under administrative processing, I need the passport back ASAP
The Defining Moment
Can someone publish a story that happened to you?
Rivers without rain
Binary Numbers Magic Trick
Apply MapThread to all but one variable
React in Django or React as a standalone?
Does Django scale?Loop inside React JSXHow to allow for webpack-dev-server to allow entry points from react-routerProgrammatically navigate using react routerreact routing and django url conflictHow to integrate Vue.js with DjangoDjango react renderIssue running React App on Django server with webpackCommunication between Django and ReactDjango rest-framework with react - blank page on frontend
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have been researching how to create django react application and the best way to go about implementing it. From this link on creating a django react app states a few way to go about implementing it.
One way is to generate a webpack and using django to load the webpack another is to run it as 2 separate applications.
What are the obvious benefits of "React in its own “frontend” Django app: load a single HTML template and let React manage the frontend" vs "Django REST as a standalone API + React as a standalone SPA"
Because I do not see a need of generating a webpack and loading the application in django template where you could create a standalone react app and use Django REST for communication?
django reactjs
add a comment |
I have been researching how to create django react application and the best way to go about implementing it. From this link on creating a django react app states a few way to go about implementing it.
One way is to generate a webpack and using django to load the webpack another is to run it as 2 separate applications.
What are the obvious benefits of "React in its own “frontend” Django app: load a single HTML template and let React manage the frontend" vs "Django REST as a standalone API + React as a standalone SPA"
Because I do not see a need of generating a webpack and loading the application in django template where you could create a standalone react app and use Django REST for communication?
django reactjs
add a comment |
I have been researching how to create django react application and the best way to go about implementing it. From this link on creating a django react app states a few way to go about implementing it.
One way is to generate a webpack and using django to load the webpack another is to run it as 2 separate applications.
What are the obvious benefits of "React in its own “frontend” Django app: load a single HTML template and let React manage the frontend" vs "Django REST as a standalone API + React as a standalone SPA"
Because I do not see a need of generating a webpack and loading the application in django template where you could create a standalone react app and use Django REST for communication?
django reactjs
I have been researching how to create django react application and the best way to go about implementing it. From this link on creating a django react app states a few way to go about implementing it.
One way is to generate a webpack and using django to load the webpack another is to run it as 2 separate applications.
What are the obvious benefits of "React in its own “frontend” Django app: load a single HTML template and let React manage the frontend" vs "Django REST as a standalone API + React as a standalone SPA"
Because I do not see a need of generating a webpack and loading the application in django template where you could create a standalone react app and use Django REST for communication?
django reactjs
django reactjs
asked Mar 22 at 18:42
EdwinEdwin
11219
11219
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The first thing you would gain by splitting your frontend and your backend is modularity. With your application logic completely separated from your user interface, you have a slightly more modular web application. Modularity aids in a number of things, including testing, readability, and maintainability.
Also with a separate API, your backend logic can be reused by any anyone or any frontend be it a mobile app or anything you could imagine even your CLI.
Your goal would be to include the final bundle of your create react app in a Django page if I understood correctly ?
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55305974%2freact-in-django-or-react-as-a-standalone%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The first thing you would gain by splitting your frontend and your backend is modularity. With your application logic completely separated from your user interface, you have a slightly more modular web application. Modularity aids in a number of things, including testing, readability, and maintainability.
Also with a separate API, your backend logic can be reused by any anyone or any frontend be it a mobile app or anything you could imagine even your CLI.
Your goal would be to include the final bundle of your create react app in a Django page if I understood correctly ?
add a comment |
The first thing you would gain by splitting your frontend and your backend is modularity. With your application logic completely separated from your user interface, you have a slightly more modular web application. Modularity aids in a number of things, including testing, readability, and maintainability.
Also with a separate API, your backend logic can be reused by any anyone or any frontend be it a mobile app or anything you could imagine even your CLI.
Your goal would be to include the final bundle of your create react app in a Django page if I understood correctly ?
add a comment |
The first thing you would gain by splitting your frontend and your backend is modularity. With your application logic completely separated from your user interface, you have a slightly more modular web application. Modularity aids in a number of things, including testing, readability, and maintainability.
Also with a separate API, your backend logic can be reused by any anyone or any frontend be it a mobile app or anything you could imagine even your CLI.
Your goal would be to include the final bundle of your create react app in a Django page if I understood correctly ?
The first thing you would gain by splitting your frontend and your backend is modularity. With your application logic completely separated from your user interface, you have a slightly more modular web application. Modularity aids in a number of things, including testing, readability, and maintainability.
Also with a separate API, your backend logic can be reused by any anyone or any frontend be it a mobile app or anything you could imagine even your CLI.
Your goal would be to include the final bundle of your create react app in a Django page if I understood correctly ?
answered Mar 22 at 18:49
stefanstefan
312
312
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55305974%2freact-in-django-or-react-as-a-standalone%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown