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

Split out the UI component from the server component #59

Open
shankari opened this issue Aug 22, 2018 · 1 comment
Open

Split out the UI component from the server component #59

shankari opened this issue Aug 22, 2018 · 1 comment

Comments

@shankari
Copy link
Contributor

They are really not related, except that we check both of them out on the e-mission server.
Combining them:

  • makes the server repository unnecessarily big,
  • requires the node/npm/bower stack on the server, which is not needed otherwise, and
  • causes a ton of diffs as libraries are updated beyond the checked-in ones.

We should split out the UI code and make it available as a submodule instead - to be used only on production servers, if people want. The main e-mission server repository should still have a web page served by default, but it should be a simple static page with no dependencies.

@shankari
Copy link
Contributor Author

This should make the docker script (#594) much easier...

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

No branches or pull requests

1 participant