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

Server option #4

Open
martinklepsch opened this issue Dec 16, 2014 · 4 comments
Open

Server option #4

martinklepsch opened this issue Dec 16, 2014 · 4 comments

Comments

@martinklepsch
Copy link
Owner

Opening this issue to facilitate some discussion about how to best integrate some server side component into Tenzing. Integrating some basic server is simple. Serving the index.html via that server is a little more complex though as currently different optimization levels require different <script> tags.

Options I currently see regarding those <script> tags:

  1. Modify some html template with Leiningen to account for :optimisations :none.
  2. Provide separate files index-dev.html & index-prod.html
  3. Make additional boot task that makes new main.js loading Javascript files depending on how they were compiled.
@martinklepsch
Copy link
Owner Author

If a :main option is going to be implemented into boot-cljs there would no modification be necessary.
boot-clj/boot-cljs#11

@martinklepsch
Copy link
Owner Author

boot-cljs has a unified option again: boot-clj/boot-cljs@7fd2943 which makes any html munging unnecessary.

Any contributions for a simple server side component are welcome!

@martinklepsch
Copy link
Owner Author

/cc @donmullen @pandeiro

@martinklepsch
Copy link
Owner Author

Potentially this can be achieved in a generic way by making a boot-ring type of task similar to @pandeiro's boot-http. This way a handler could be specified and you're good to go.

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