Skip to content
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

[CHORE] Adjust .idea tracking #2

Merged
merged 1 commit into from
Nov 10, 2015
Merged

[CHORE] Adjust .idea tracking #2

merged 1 commit into from
Nov 10, 2015

Conversation

gblair
Copy link

@gblair gblair commented Nov 10, 2015

No description provided.

zdavis referenced this pull request in zdavis/manifold Nov 10, 2015
@zdavis zdavis merged commit 1a9284b into ManifoldScholar:development Nov 10, 2015
zdavis added a commit that referenced this pull request Oct 3, 2016
This breaks apart our approach to serving the client in the interest of
increased performance in development and reduced build times. Running
npm start kicks off a number of distinct processes:

1. We build some vendor modules that change very infrequently to
/dist/build/universal/dll. This way, webpack doesn't have to watch
these files or worry about them when its building changed files.

2. The entire application is built to dist/build/server/react-server.
This javascript is responsible for the server-side rendering of
application routes.

3. Just enough javascript to render an HTML container for the client-
side code is built to dist/build/server/web-server. In the event that
the universal page rendering service is not available, the application
can still render the HTMl container and let the client-side code take
over.

4. The "react server" begins. This is the express app at defined at
src/server-react. It includes the react-server js from #2, above.

5. The "web server" begins. This is mostly a proxy server that proxies
requests to the react server, or to the asset server. In the event
that the react-server is unreachable, which is often the case when its
reloading due to code change, the webserver will return an HTML
container that the client-side code can mount on.

6. The "asset server" begins. This is the webpack dev server that
serves the client-side assets in development mode. It also serves
all other files in /dist.
@zdavis zdavis mentioned this pull request Apr 21, 2017
@zdavis zdavis mentioned this pull request Oct 15, 2019
@zdavis zdavis mentioned this pull request Mar 8, 2021
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants