Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[considering] Dev/Staging/Production server containers on the same machine #7

Open
DeanAyalon opened this issue Jun 7, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@DeanAyalon
Copy link
Owner

Will require forwarding a different port for FileMaker to access, or forwarding it through proxy
Check if nginx-proxy has the ability to listen on different ports (5003)

Will probably not be ideal for real scenarios, but potentially could help single-machine developers

Current thinking:

services:
  fms${FMS_ENV:+-}${FMS_ENV} # fms OR fms-$FMS_ENV
# alternative: 
  fms-${FMS_ENV:-prod} # cleaner yml but not as nice of a container name

This would lead to an easy quick switch by simply changing the .env file, without compose replacing the container

Alternative

services:
  fms:
    extends: 
      file: compose.base.yml
      service: fms
    profiles:
      - prod
    environment:
      VIRTUAL_HOST: ${DOMAIN}
      # Is there a way to ensure host1.domain:5003 reaches here in nginx-proxy?
      
  fms-dev:
    ...
  fms-staging:
    ...

Would be messy and require many more environment variables, but may allow for easier control without changing env files

@DeanAyalon DeanAyalon added the enhancement New feature or request label Jun 7, 2024
@DeanAyalon DeanAyalon self-assigned this Jun 7, 2024
@DeanAyalon
Copy link
Owner Author

This may help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant