Show cask version of webapp as eventual replacement for play #843
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Compile with no warnings, some renamed processor variables, view changes
Clean it up more Get rid of debug files
|
This is being pushed to github as a backup and made into a PR to document what I had been working on. This was built on top of the processors2 branch and that is largely the reason for the extra long history. It could be modified to be an independent branch. I'm not intending to merge it until it's clear that there will be someone around to maintain it. |
|
Thank you @kwalcock ! |
|
It's still of concern that neither cask nor http4s have reached version 1. This update makes use of scalatags which is very much more handy than string manipulation to generate html. We also lose Java 8 at runtime with cask, but just for the webapp. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The play version is significant overkill for a webapp with next to no state. Because of recent significant changes to play, the webapp was only working for one Scala version, and it requires a completely different project structure and deployment mechanism. The cask version is intended to streamline and simplify the project.