Skip to content

docker-compose: remote environment-related fixes and doc#77

Draft
shtrom wants to merge 2 commits intomainfrom
no-bug/remote_env
Draft

docker-compose: remote environment-related fixes and doc#77
shtrom wants to merge 2 commits intomainfrom
no-bug/remote_env

Conversation

@shtrom
Copy link
Member

@shtrom shtrom commented Jan 14, 2026

  • docker-compose: pin lando.db to postgres:17
    This is what's currently running in remote environments.
  • docker-compose: add comments to document how to simulate remote environments

@shtrom shtrom changed the title No bug/remote env docker-compose: remote environment-related fixes and doc Jan 14, 2026
@shtrom shtrom requested a review from zzzeid January 14, 2026 05:31
Copy link
Contributor

@zzzeid zzzeid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment applies to mozilla-conduit/lando#834 as well. IMO this is enough of an edge case that it doesn't necessarily belong in the compose file.

Comment on lines +177 to +186
# To simulate a remote environment, uncomment the following lines...
# ENVIRONMENT: development
# DJANGO_SETTINGS_MODULE: lando.remote_settings

# ... and comment this one.
ENVIRONMENT: local
#
# This will likely trigger errors when running the `setup_dev` and
# `collectstatic` commands below. They need to be manually disabled
# during such a simulation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this may be more confusing (especially in the long term) than helpful. I would suggest, instead of adding a comment like this here, maybe we can add a separate make command to "simulate" a specific scenario (e.g., using remote_settings with "local" or "development" environment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants