Skip to content

[WIP]: A path to white label friendly play-haskell #54

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

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

hellwolf
Copy link

@hellwolf hellwolf commented Jan 22, 2025

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

⚠️ Bear in mind, though, that the code itself is not ready until I mark this draft PR ready for review.

This is a draft PR documenting my "slow" process of realizing these thoughts and keeping myself accountable for my promise...

Customizing Server <-> Worker protocol

  1. submit function assumes

Customizing Server

  • Customizable page header
  • Customizable worker commands (default is Run, Asm, Core
  • Customizable example code

Customizing Worker

  • Customizable resource limits, e.g. resource memory for systemd process
  • Customizable worker command
  • Customizable ghc version <-> builders scheme: e.g. customizable from ./builders/build-9.10.1.sh to ./builders/yolc-9.10.1.sh .
  • Make mkbuildscript.sh support building from non-hackage-published local packages. In case of the EDSL project is not published to hackage.
  • Customizable project template, since the EDSL project may not build from a "Main" module entirely written by the user.

Contributor checklist

  • My PR is related to [TICKET NUMBER], if applicable
  • I have read and understood the CONTRIBUTING guide

@hellwolf hellwolf changed the title [WIP]: A path to whitelable friendly play-haskell [WIP]: A path to white lable friendly play-haskell Jan 22, 2025
@hellwolf hellwolf changed the title [WIP]: A path to white lable friendly play-haskell [WIP]: A path to white label friendly play-haskell Jan 22, 2025
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.

1 participant