How stoufexis/ultimocker-5000 works
Ultimocker is a disposable route-mocking and pinging service. Its workflow reads configured inbound routes and outbound targets, serves registered routes with HTTP 200 responses, and periodically requests configured targets while appending ping activity and response data to a log. Environment variables set the listener port and ping interval. The source excerpt shows these runtime behaviors; README details clarify the configuration and container usage, but container/build setup is not part of the runtime architecture.
Main entry points: index.js Ping interval loop · config.json Route and target config · env.js Runtime settings · logs.txt Runtime log file
Components 8
Configuration
- Route and target config
config.json - Runtime settings
src/env.js
HTTP Service
- Mock route handler
src/index.js
Scheduled Pinging
- Ping interval loop
src/index.js - Outbound HTTP client
src/index.js - Runtime log file
logs.txt
Other components
- HTTP caller
- Configured ping targets
Connections 10
- Route and target config → Mock route handler: configures routes
README.md - Route and target config → Ping interval loop: provides targets
README.md - Runtime settings → Mock route handler: sets port
src/index.js - Runtime settings → Ping interval loop: sets interval
src/index.js - HTTP caller → Mock route handler: requests route
src/index.js - Mock route handler → HTTP caller: returns 200
src/index.js - Ping interval loop → Outbound HTTP client: dispatches requests
src/index.js - Outbound HTTP client → Configured ping targets: requests targets
src/index.js - Ping interval loop → Runtime log file: appends ping activity
src/index.js - Outbound HTTP client → Runtime log file: appends response data
src/index.js