Skip to content

user76-real/Overlord

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Overlord

Hello, I made this project for fun.

Just use docker please the src is fine to use as well but you need golang, bun, garble and openssl.

To use docker copy the docker-compose.yml to your working directory and run

docker compose up

On first startup, if secrets are not provided through environment variables, Overlord generates them and persists them to data/save.json (inside Docker: /app/data/save.json). This includes:

  • JWT signing secret
  • Agent auth token
  • Initial admin bootstrap password

Keep save.json private and backed up. Use values from that file if you need to recover bootstrap access.

to update run

docker compose pull

It's literally just docker any question chatgpt can answer so don't worry.

Production package (Windows)

Build a production-ready package where the server can still build client binaries at runtime:

build-prod-package.bat

Linux/macOS:

./build-prod-package.sh

Windows output folder:

release

Windows package includes:

  • Overlord-Client
  • overlord-server.exe
  • overlord-server-linux-x64
  • start-prod-release.bat
  • start-prod-release.sh
  • public

build-prod-package.bat also minifies public/assets/*.js into the release package.

Note: both packaging scripts always skip building client binaries and export Overlord-Client source for runtime builds.

About

No description, website, or topics provided.

Resources

License

Stars

0 stars

Watchers

0 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages

  • Go 28.7%
  • JavaScript 27.9%
  • TypeScript 25.4%
  • HTML 11.9%
  • CSS 3.1%
  • Batchfile 1.2%
  • Other 1.8%