[WIP]: A path to white label friendly play-haskell #54
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.
Motivation
The white labeling of play-Haskell, if made easy, can be quite an attractive tool for EDSLs, who could benefit from an easier way of onboarding/showcasing their technology to stakeholders or public audiences.
Yolc is one such use case that I was after, but the likes of copilot, clash lang, may also be of interest.
Overall, it took me approximately two to three days to hack everything live at play.yolc.dev. During the process, with the hands-on experience, I put my thoughts and proposals on how I think we could make the project white labeling easier in this PR.
Proposed changes
This is a draft PR documenting my "slow" process of realizing these thoughts and keeping myself accountable for my promise...
Customizing Server <-> Worker protocol
Customizing Server
Customizing Worker
./builders/build-9.10.1.sh
to./builders/yolc-9.10.1.sh
.mkbuildscript.sh
support building from non-hackage-published local packages. In case of the EDSL project is not published to hackage.Contributor checklist