Fork di lean4game del PHC per la settimana matematica del 2025 https://lean4game.phc.dm.unipi.it/
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Go to file
Jon Eugster 52b42544ac
Create LICENSE
2 years ago
.github/workflows copy action from lean4web 2 years ago
.vscode add vs code settings 2 years ago
client Merge pull request #79 from leanprover-community/automatic_inventory_doc 2 years ago
server rename to local/game 2 years ago
.gitignore update .gitignore 2 years ago
DOCUMENTATION.md update installation instruction 2 years ago
LICENSE Create LICENSE 2 years ago
NOTES.md unzip 2 years ago
NOTES_SUBDOMAIN.md notes subdomain 2 years ago
README.md running games locally documentation 2 years ago
ecosystem.config.js update ecosystem.config.js 2 years ago
package-lock.json use cross-env to make npm scripts work on windows 2 years ago
package.json use cross-env to make npm scripts work on windows 2 years ago
tsconfig.json ignore server/ when building webpack 2 years ago
webpack.config.js node_modules regex does not seem to work on windows 2 years ago

README.md

Lean 4 Game

This is a prototype for a Lean 4 game platform. The project is based on ideas from the Lean Game Maker and the Natural Number Game (NNG) of Kevin Buzzard and Mohammad Pedramfar. The project is based on Patrick Massot's prototype: NNG4.

Progress & Contributing

Currently the interface is still undergoing bigger changes, contributions are of course welcome, but it might be better to wait with them for a bit until proper support for external games is implemented and the existing games are separated from this repository. (ca. Sept. 2023)

Documentation

For game developers, there is a work-in-progress Documentation: Create a Game. Best to talk with us directly.

For the game engine itself, documentation is missing currently.

NPM Scripts

  • npm start: Start the project in development mode. The browser will automatically reload when client files get changed. The Lean server will get recompiled and restarted when lean files get changed. The Lean server will be started without a container. The client and server can be started separately using the scripts npm run start_client and npm run start_server. The project can be accessed via http://localhost:3000. Internally, websocket requests to ws://localhost:3000/websockets will be forwarded to a Lean server running on port 8080.

  • npm run build: Build the project in production mode. All assets of the client will be compiled into client/dist. On the server side, the command will set up a docker image containing the Lean server. The two parts can be built separately using npm run build_client and npm run build_server.

  • npm run production: Start the project in production mode. This requires that the build script has been run. It will start a server on the port specified in the PORT environment variable or by default on 8080. You can run on a specifiv port by running PORT=80 npm run production. The server will serve the files in client/dist via http and give access to the docker-contained Lean server via the web socket protocol.

Security

Providing the use access to a Lean instance running on the server is a severe security risk. That is why we start the Lean server in a Docker container secured by gVisor.