- Rust 81.6%
- Vue 12.4%
- TypeScript 5.8%
- HTML 0.1%
|
Some checks failed
Multi-Arch Docker Build and Push to Forgejo Registry / build (Dockerfile.api, api-image, api) (push) Has been cancelled
Multi-Arch Docker Build and Push to Forgejo Registry / build (Dockerfile.maprenderer, maprenderer-image, maprenderer) (push) Has been cancelled
Multi-Arch Docker Build and Push to Forgejo Registry / build (Dockerfile.util, util-image, util) (push) Has been cancelled
|
||
|---|---|---|
| .cargo | ||
| .forgejo/workflows | ||
| .idea | ||
| app | ||
| lib | ||
| ui | ||
| .dockerignore | ||
| .gitignore | ||
| build_maprenderer_wasm.sh | ||
| Caddyfile | ||
| Cargo.lock | ||
| Cargo.toml | ||
| docker-compose.sample.yml | ||
| docker-compose.yml | ||
| Dockerfile.api | ||
| Dockerfile.caddy | ||
| Dockerfile.util | ||
| DockerfileBuildArmv6Raspi | ||
| martin.sample.yaml | ||
| Readme.md | ||
moLoServ Rust
moLoServ is the name for morihofi's Location Service. Fully written in Rust, previously in Java and later Go. It contains multiple components, see below
Map Renderer
We offer two versions, based on the almost same codebase
Server side Rendering
The classic one that is at least supported since the older WiFiDB Java releases. It serves a OpenStreetMap compatible HTTP API for overlay tiles and Google Earth API support.
Client side Rendering (Beta)
A newer option besides the SSR renderer that lets the browser rendering the overlay using same data. It uses Rust compiled to WebAssembly to achieve almost same performance
API
The API offers Google compatible GeoLocation and Scan Uploads
Util
The main command that takes all the measurements and produces the grid container, that can then be passed to the API Server or the map renderers
Grid container schema
Each grid JSON entry now optionally contains a bluetooth object in addition to
wlan and cellular.
Logging
All binaries respect the MOLOSERV_LOG_LEVEL environment variable. Accepted values are
TRACE, DEBUG, INFO, WARN and ERROR. If the variable is unset, the log level
defaults to INFO. Providing an invalid value falls back to DEBUG.
Offline OSM Data
Operations that rely on OpenStreetMap require .pbf files to be downloaded and cached
locally. The utilities read from these local files and never fetch data from upstream
OSM servers at runtime.