MCPcopy Index your code
hub / github.com/FlashpointProject/FlashpointUltimateUpdater

github.com/FlashpointProject/FlashpointUltimateUpdater @1.0

Chat with this repo
repository ↗ · DeepWiki ↗ · release 1.0 ↗ · + Follow
59 symbols 140 edges 5 files 1 documented · 2%
What it actually does AI analysis from the code graph — generated when you open this
loading…
README

Flashpoint Ultimate Updater

Screenshot

Flashpoint Ultimate Updater is designed to install extremely large numbers of immutable files from a remote server. Built on the back of the grab library.

Features: - Resumable install state - Speed limitter - Pause and start downloader - Scan and repair existing files - Resume partial file downloads - Install information fetched from remote server - Upgrade existing install to new version - Force upgrade when version no longer available on remote server

Setting up your remote server

  1. Install python and install indexer dependencies
python -m pip install -r requirements.txt
  1. Create an index for each install version you want to serve. Save the resulting sqlite file to somewhere accessible on your webserver you wish to keep the updater metadata.
  2. directory_to_scan - Directory of static files to index
  3. version_name - Version name to show in the updater
  4. serve_url - URL to where the directory of static files will be available on
python ./index.py <directory_to_scan> <version_name> <serve_url> <output.sqlite>
  1. Create the metadata file that is fetched by the updater. Save to meta.json somewhere accessible online.
  2. current - Version name of the current version. Must match version_name from index above
  3. path - URL to the current sqlite file.
  4. available - List of available versions still being hosted, same format as current. If any are removed, users will be forced to upgrade to the current version.
{
  "current": "Release 2.0",
  "path": "https://example.com/updater-data/release-2.0.sqlite",
  "available": [
    "Release 1.0",
    "Release 2.0"
  ]
}
  1. Edit the built in config.json to point to the meta.json file and compile your version. Placing config.json manually next to any compiled executable will override this.
{
  "meta_url": "https://example.com/updater-data/meta.json"
}

Keep reading on to Building to create an updater with the new config.json

Building

  1. Bundle the config json

fyne bundle -o bundle.go config.json

  1. Package for desired operation system and set the icon

fyne package -os <windows/linux/darwin> -icon icon.png

Ta-da, there's a new executable in the folder!

Core symbols most depended-on inside this repo

Close
called by 8
repo.go
Error
called by 7
types.go
Stop
called by 6
downloader.go
NewRequest
called by 4
downloader.go
FormatBytes
called by 4
main.go
Resume
called by 3
downloader.go
setupLayout
called by 3
main.go
loadDatabaseResume
called by 3
main.go

Shape

Method 24
Struct 19
Function 16

Languages

Go95%
Python5%

Modules by API surface

types.go26 symbols
repo.go13 symbols
main.go11 symbols
downloader.go6 symbols
index.py3 symbols

For agents

$ claude mcp add FlashpointUltimateUpdater \
  -- python -m otcore.mcp_server <graph>

⬇ download graph artifact