Giter VIP home page Giter VIP logo

lila-docker's Introduction

lila-docker

Lichess development environment using Docker Compose, for developing on Mac, Linux, or Windows (via WSL).

The only requirements for running on your local machine are git and Docker Desktop. All the other dependencies (Scala, MongoDB, Node.js, etc) are installed and run in Docker containers.

Running in Gitpod

As an alternative to running it on your local machine, you can use Gitpod (a free, online, VS Code-like IDE) for contributing. With a single click, it will launch a workspace and automatically:

  • Clone the necessary Lichess repositories
  • Install all the dependencies
  • Seed your database with test data
  • Start your development site

Click here to create a workspace:

Open in Gitpod

Instructions

  1. Install Docker Desktop and have it running

  2. Clone this repo:

    git clone https://github.com/lichess-org/lila-docker
  3. Start the services

    cd lila-docker
    ./lila-docker start

    Starting new services may take 5-10 minutes. Some services will start before others and you may see errors in the logs until everything comes online.

    Lila will be the last service to complete, at which point you can visit http://localhost:8080/ to see the site.

Stopping

To stop the containers, for later resuming via ./lila-docker start:

./lila-docker stop

To remove the containers:

./lila-docker down

URLs

Always available:

Service URL
Main lila instance http://localhost:8080/

Depending on which optional services you start:

Service URL
Mongodb manager http://localhost:8081/
Email inbox http://localhost:8025/
lila-gif http://localhost:6175/image.gif?fen=4k3/6KP/8/8/8/8/7p/8
Picfit http://localhost:3001/healthcheck
Elasticsearch manager http://localhost:8092/
API docs http://localhost:8089/
Chessground http://localhost:8090/demo.html
PGN Viewer http://localhost:8091/
InfluxDB http://localhost:8086/ (admin/password)

Usage

Scala development:

To restart lila (after making changes to any Scala code):

./lila-docker lila restart

UI (JS/CSS) development:

To watch for Typescript/SCSS changes and automatically recompile:

./lila-docker ui

Updating Routes

If you edit the conf/routes file, you'll need to update the route cache.

docker compose exec lila ./lila playRoutes

To add translation keys:

After modifying a translation/source/*.xml file, run:

docker compose run --rm ui /lila/bin/trans-dump

Code formatting:

./lila-docker format

Optional: Make the database persistent

docker compose cp mongodb:/data/db ./database

Then in docker-compose.ymladd - ./database:/data/db to mongodb volumes

Berserk (Python library):

To install the development version of Berserk and run a sample script against your local development site:

docker compose run --rm -w /berserk python \
    bash -c "pip install -e . && python /scripts/berserk-example.py"

Scala Metals (IDE helper):

  1. In VS Code, open this lila-docker project and install the Dev Containers extension
  2. Cmd+Shift+P > "Dev Containers: Rebuild and Reopen in Container"
  3. A new VS Code window will open, attached to the container instead of your host machine
  4. File > Open Folder > "/workspaces/lila-docker/repos/lila" (or whichever Scala project you want to work on)
  5. Install + Enable the Scala Metals extension (Cmd+Shift+X > "Scala (Metals)")
  6. Cmd+Shift+P > "Metals: Import build"

Once the build has been imported, you should have code completion, go to definition, etc when you open a Scala file.

Scalachess:

If you're making changes to the Scalachess library, you can have lila use it instead of the published Maven version:

  1. Update the build.sbt file in the scalachess repo:

    -  ThisBuild / version           := "15.6.7"
    +  ThisBuild / version           := "my-test-1"  # give it a custom version
  2. Update the Dependencies.scala file in the lila repo:

    -  val chess = "org.lichess" %% "scalachess" % "15.6.7"
    +  val chess = "org.lichess" %% "scalachess" % "my-test-1"
  3. Publish the local scalachess changes and restart lila:

    docker compose exec -w /scalachess lila sbt publishLocal
    docker compose restart lila

Other Scalachess commands:

## formatting
docker compose run --rm -w /scalachess --entrypoint="sbt check" lila
docker compose run --rm -w /scalachess --entrypoint="sbt prepare" lila

## compile
docker compose run --rm -w /scalachess --entrypoint="sbt compile" lila

## test
docker compose run --rm -w /scalachess --entrypoint="sbt testKit/test" lila

## package
docker compose run --rm -w /scalachess --entrypoint="sbt package" lila

Dartchess:

## run formatter
docker compose run --rm -w /dartchess mobile dart format .

## analyze
docker compose run --rm -w /dartchess mobile bash -c "dart pub get && dart analyze"

## run tests
docker compose run --rm -w /dartchess mobile bash -c "dart pub get && dart test -x full_perft"

Developing Chessground locally

By default, your local lila instance will use the version of chessground that is published to npm. If you want to make changes to that library and see them reflected in your local lila instance, you can do the following:

  1. Update the package.json in the lila repo:

    "dependencies": {
    -  "chessground": "^8.3.11",
    +  "chessground": "link:/chessground",
    }
  2. Start the chessground compiler in watch mode:

    docker compose run --rm -w /chessground ui bash -c "pnpm install && pnpm run compile --watch"
  3. Start the lila ui build in watch mode:

    ./lila-docker ui

Then you can see the updated chessground demo at http://localhost:8090/demo.html and when you refresh lila, it will use the local copy of chessground.

Developing PGN Viewer locally

To re-compile the PGN Viewer after making changes:

docker compose run --rm -w /pgn-viewer ui bash -c "pnpm run sass-dev && pnpm run bundle-dev"

See the changes on the PGN Viewer demo page: http://localhost:8091/

InfluxDB Monitoring

To view the InfluxDB monitoring dashboard, start your environment with the Monitoring service enabled and then visit http://localhost:8086/ (admin/password)

You can also see all the metrics logged by running:

curl --get http://localhost:8086/query \
    --header "Authorization: Token secret" \
    --data-urlencode "db=kamon"  \
    --data-urlencode "q=show measurements;"

Mobile

  1. On your Android phone:

    1. Connect your phone to the same wifi network as your host machine
    2. Enable Developer Mode
    3. In Developer Options, enable Wireless Debugging and tap into its menu
  2. On your host machine:

    1. Have the lila-docker services running, with the Mobile optional service started

    2. Configure lila to run with your host's IP address or hostname instead of localhost

      ./lila-docker hostname
      • Then verify that your phone can access the site at http://[your-selection]:8080
    3. Connect to your phone

      ./lila-docker mobile
    4. Get a shell on the container:

      docker compose exec -it mobile bash
      
      # verify your phone is listed
      adb devices
    5. Install the app dependencies:

      flutter pub get
      dart run build_runner build
    6. Run the app:

      flutter run -v \
          --dart-define LICHESS_HOST=$LILA_URL \
          --dart-define LICHESS_WS_HOST=$LILA_URL
      • No substitutions necessary. The $LILA_URL environment variable will already be set on the container.
      • First time you run it, it might take a while

lila-docker's People

Contributors

amitdash291 avatar carbrex avatar fitztrev avatar juesto avatar kraktus avatar tors42 avatar trevorbayless avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

lila-docker's Issues

Development server on EC2 instance port 8080 causing problems

I deployed the development server on my EC2 instance. There is no issue accessing ports 8081 or 8025, but the main port 8080 is causing problems. Looking at the docker logs for this container this is the error.

24.4.198.26 - - [10/Feb/2024:00:42:31 +0000] "GET / HTTP/1.1" 301 0 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 16_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.5 Mobile/15E148 Safari/604.1" "

docker start getting killed automatically on mac

No idea about scala and how it runs but I installed docker on my mac and cloned this repo
When I run this command
lila-docker git:(main) ./lila-docker start
it takes a while and seems to be going to good but after a bit I see this error

lila-1  | [info] done compiling
lila-1  | [info] compiling 7 Scala sources to /lila/modules/appeal/target/scala-3.4.1/classes ...
lila-1  | [info] done compiling
lila-1  | [info] compiling 6 Scala sources to /lila/modules/playban/target/scala-3.4.1/classes ...
lila-1  | Killed
lila-1 exited with code 0
image I have a decent machine image

Should I allocate more memory to docker or something on those lines?

Outbound emails

I was looking to have real outbound emails for registration. I'm not sure how to configure the docker image to do this.

Content Security Policy console errors

  1. Visit http://localhost:8080/forum

See console error:

Refused to load the font 'data:application/octet-stream;....'
because it violates the following Content Security Policy directive:
"font-src 'self' localhost:8080".
  1. Visit http://localhost:8080/patron

See console error:

Refused to execute inline script because it violates the following Content Security Policy directive:
"script-src https://*.paypal.com https://*.stripe.com 'nonce-nAz29QMpZzMbeetZjks5zcwp' 'self' localhost:8080".
Either the 'unsafe-inline' keyword, a hash ('sha256-b+mf6EIMFYxuAIdk6/2IF09zTUsJrlW6qZaw4opG6QU='), or a nonce ('nonce-...') is required to enable inline execution.

Allow custom ports

For each port that gets exposed to the host OS, allow it to be customized in case it's already in use.

ports:
-  - 8080:80
+  - ${LILA_PORT:-8080}:80

Image upload server error

When writing a blog post, the image upload doesn't work in the dev environment.

image

Possible picfit misconfiguration.

03:13:28.632 [error] p.c.s.n.PlayRequestHandler - Cannot invoke the action
lila.base.LilaException$$anon$1: Not Found 404 page not found
     at lila.base.LilaException$.apply(LilaException.scala:19)
     at lila.base.LilaTypes.fufail(LilaTypes.scala:21)
     at lila.base.LilaTypes.fufail$(LilaTypes.scala:8)
     at lila.Lila$.fufail(Lila.scala:3)
     at lila.memo.package$package$.fufail(package.scala:3)
     at lila.memo.PicfitApi.lila$memo$PicfitApi$picfitServer$$$_$store$$anonfun$1(Picfit.scala:95)
     at scala.concurrent.impl.Promise$Transformation.run(Promise.scala:470)
     at scala.concurrent.BatchingExecutor$AbstractBatch.runN(BatchingExecutor.scala:134)
     at scala.concurrent.BatchingExecutor$AsyncBatch.apply(BatchingExecutor.scala:163)
     at scala.concurrent.BatchingExecutor$AsyncBatch.apply(BatchingExecutor.scala:146)

Make token setup optional

--tokens is passed to lila-db-seed during database setup to auto create user tokens

If a password other than "password" is chosen, it should ask if tokens should be setup.

image

If on Gitpod environment, prompt if workspace should be public

By default, your gitpod-hosted lichess dev site is only accessible from the same browser you're logged into gitpod with. All other requests get a 401.

This causes problems for people trying to access it via code or the mobile app for instance if they're trying to use it that way.

  1. add prompt to setup cli
  2. conditionally call gitpod_public()

Lila PR preview sites

Support a link that, when clicked, will start a gitpod instance but with a PR's branch checked out instead of master. Will allow others to test a PR easily.

You can setup environment variables on Gitpod in the url like this:

- https://gitpod.io/#https://github.com/lichess-org/lila-docker
+ https://gitpod.io/#lila-pr=12345/https://github.com/lichess-org/lila-docker

Then, if lila-pr is set, we can fetch and checkout during setup.

git fetch upstream pull/12345/head:preview
git checkout preview

Workflow to reflect typescript changes?

Hi,

I love this initiative of having a gitpod environment to onboard on lichess dev.

In the doc it is stated that

UI (JS/CSS) development:
To watch for Typescript/SCSS changes and automatically recompile:
docker compose run --rm ui bash -c "/lila/ui/build -w"

Unfortunately, when I did execute this command, it seems not enough to fully reflect changes on the running website.
Basically, I have to restart lila with:

Scala development:
To restart lila (after making changes to any Scala code):

docker compose restart lila

despite my changes are not directly related to Scala code.

Did I misunderstand something?

The current dev workflow is not so satisfactory.
Basically, I was trying to debug the JS code with some console.log...
And I have to wait lots of time to see the actual effect.

I'm sure I'm missing something.

Thanks a lot!

Python error when trying to setup mobile

I am setting up local docker for flutter mobile app and seeing the following error

 => [python internal] load build definition from python.Dockerfile                                                              0.0s
 => => transferring dockerfile: 231B                                                                                            0.0s
 => [ui internal] load build definition from ui.Dockerfile                                                                      0.0s
 => => transferring dockerfile: 383B                                                                                            0.0s
 => ERROR [python internal] load metadata for docker.io/library/python:3.12.3-alpine3.19                                        0.1s
 => ERROR [ui internal] load metadata for docker.io/library/node:20.12.2-bookworm-slim                                          0.1s
 => ERROR [python internal] load metadata for docker.io/library/eclipse-temurin:22_36-jdk-alpine                                0.1s
------
 > [python internal] load metadata for docker.io/library/python:3.12.3-alpine3.19:
------
------
 > [ui internal] load metadata for docker.io/library/node:20.12.2-bookworm-slim:
------
------
 > [python internal] load metadata for docker.io/library/eclipse-temurin:22_36-jdk-alpine:
------
failed to solve: node:20.12.2-bookworm-slim: failed to resolve source metadata for docker.io/library/node:20.12.2-bookworm-slim: error getting credentials - err: exec: "docker-credential-desktop": executable file not found in $PATH, out: ``

Do i need specific version of python or node? I have node v22.0.0 not sure why the error is specifying other node version.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.