code-to-screen

frontend

Vite installation

In the root directory:

npm create vite@latest

and the project is named frontend.

npm install
npm run dev

and the project is served at http://localhost:5173/

Added Scala.js

• Added sbt configuration.

• Added Main.scala for code in scala.js

• Run ~fastLinkJS in sbt and npm run dev on another terminal

Added laminar dependency

• Added laminar as a dependency

• Changed Main.scala to use laminar

  • It seems that something needs a @main entrypoint because leaving the code at top-level does not compile.

backend

• Added configuration in build.sbt

• Minimal "test" on browser console (in many tabs) by:

let ws = new WebSocket('ws://localhost:8080/subscribe')
ws.onmessage = function(e) { console.log(e) }
ws.send("potato")

modified frontend to use websockets

• Added dependency on 'laminext'

• Added proxy in `vite.config.js' for the websocket endpoint on the server

• To run in development mode

  • on sbt run backend/run
  • on sbt run frontend/fastLinkJS
  • in frontend folder npm run dev

added sbt-revolver

• Added the plug-in to sbt configuration

• Now to start the backend:

  • on sbt run backend/reStart (or ~backend/reStart to trigger restarting the app with changes)

  • you also have reStop and reStatus

production version

• on sbt run frontend/fullLinkJS

• copy frontend/index.html and frontend/target/scala-3.4.0/frontend-opt/main.js and frontend/public/* to backend/src/main/resources/public

• change the public/index.html to point to the main.js in the public folder

• on sbt run backend/reStart

• open http://localhost:8080

added sbt-assembly for creating uberjar

• on sbt run backend/assembly and the uberjar file is at backend/target/scala-3.4.0/code-to-screen-standalone.jar

• you can run in by java -jar code-to-screen-standalone.jar

added Dockerfile

• run docker build -t code-to-screen-scala . to build an image

• docker run --detach --publish 8080:8080 --name code-to-screen-1 code-to-screen-scala

added deploy to fly.io

• added fly.toml file

• run fly auth login and then fly deploy

  • NOTE: Added --deput=false and --ha=false; the first one because it failes otherwise and the second one to deploy only on one machine