Applications#
Applications are individual atomic services that are configured and deployed through Phalanx. Each environment can opt whether to deploy an application, and also customize the configuration of the application. This section of the documentation describes each Phalanx application.
To learn how to develop applications for Phalanx, see the Developers section.
- cachemachine — JupyterLab image prepuller
- datalinker — IVOA DataLink service
- hips — HiPS tile server
- linters - automated chechking of DNS
- mobu — Integration testing
- moneypenny — User provisioning
- noteburst — Notebook execution-as-a-service
- nublado — JupyterHub/JupyterLab for RSP
- nublado2 — JupyterHub for RSP
- obstap — IVOA OBSCore Table Access Protocol
- portal — Firefly-based RSP Portal
- semaphore — User notification
- sherlock — App ingress status and metrics
- sqlproxy-cross-project — External Cloud SQL proxy
- squareone — RSP homepage
- tap — IVOA Table Access Protocol
- tap-schema — TAP schemas
- times-square — Parameterized notebooks
- vo-cutouts — IVOA SODA image cutouts
- alert-stream-broker — Alert transmission to brokers
- exposurelog — Exposure message log
- narrativelog — Narrative observatory log
- plot-navigator — Data production plot viewer
- production-tools — Data Production monitoring
- sasquatch — Observatory telemetry
- strimzi — Kafka cluster manager
- strimzi-registry-operator — Schema registry for Alert Broker
- telegraf — Application telemetry collection
- telegraf-ds — Per-node telemetry collection