Environments

needs verification

DNS is the Domain Name System that maps hostnames to services. APK means Android application package.

Staging is the validation lane. Production serves the public product. The checked-in configuration establishes the targets below; conflicting prose and historical hostnames still need reconciliation.

Service directory

Service	Staging	Production	Status and source
lt-web	stg.lt.org; older config candidate staging.lt-web.pages.dev	lt.org	Needs verification: DNS targets lt-stg.pages.dev; compare web config
lt-core	core.stg.lt.org	core.lt.org	Verified configuration: mobile build profiles
lt-strapi admin	cms.stg.lt.org/admin; older cms-stg.lt.org candidate	cms.lt.org/admin	Needs verification: infra guide versus older automation environment
Meilisearch	Internal service; no public staging hostname documented	search.lt.org	DNS, staging host responsibilities
Finished media	media.stg.lt.org	media.lt.org	Cloudflare R2 contract and verification
LT Player demo media	demo.lt.org	Shared demo media, not a production app	R2 guide
lt-app	LT STG, TestFlight on iOS, internal APK on Android	Latest Thinking identifier reserved for publisher decision	Variants, distribution runbook
lt-docs	Deployment URL unknown	Deployment URL unknown	Gap; public help repository
lt-player documentation	Player showcase	Player documentation	Observed live on 10 September 2026; exact release revision unverified
lt-docs-internal	No staging deployment	Hosting target undecided	Hosting decision pending
Legacy Drupal site	Not a current environment	latestthinking.com	Historical context in technology notes

An environment link identifies a service location, not permission to administer it. Start with getting access.

Five virtual machines

A virtual machine (VM) is an isolated server. Each environment separates stateless application containers from persistent data. The operations VM builds and deploys across a private network. The website remains on Cloudflare Pages, outside these five VMs.

Environment topology

100%

Drag to pan. Scroll or pinch to zoom. Keyboard: + / −, arrows, 0 to fit, Escape to close.

This is a service topology, not a firewall specification. The deployment guide describes runner, registry and private deployment paths. The R2 guide explains the media split.

Branches and promotion

For the application deployment pipeline, staging deploys to staging and main deploys to production. Promotion is a reviewed merge from staging into main.

lt-player is distributed as an npm package, with develop for stories and main for releases. Its release process is separate from the server deployment pipeline.

For maintainers: local development

The shared welink-dev-services stack supplies Traefik routing and supporting services. These hostnames describe local development, not remotely accessible environments.

Local websitehttp://lt.localhost

Local lt-corehttp://core.lt.localhost

Local CMShttp://cms.lt.localhost

Mailpithttps://mail.localhost

MinIO object storagehttps://s3.localhost

For a physical phone, follow the mobile networking guide. Seeded local roles are documented in the core repository; this site does not reproduce their credentials.

Unresolved environment details

The staging web and CMS names disagree across sources. Older production guides still mention pre-cutover targets and temporary aliases, while DNS and cutover evidence use the live hostnames above. The cutover report leaves alias retirement pending. Help-site and internal-site hosting remain undocumented or undecided. The player showcase and documentation were verified at player.lt.org during review. Track ownership and resolution in open questions.

For maintainers: source references

These references require repository access. Everything needed to understand this page is explained above.

• Infrastructure DNS
• staging guide
• production cutover evidence
• DNS
• web config
• mobile build profiles
• infra guide
• older automation environment
• staging host responsibilities
• Cloudflare R2 contract and verification
• R2 guide
• Variants
• distribution runbook
• public help repository
• technology notes
• Infrastructure architecture
• staging hosts
• production hosts
• deployment guide
• Push-to-deploy rule
• Player workflow
• Core setup
• web setup
• CMS setup
• mobile networking guide