Skip to content
This repository has been archived by the owner on May 11, 2022. It is now read-only.

forward mapping #5

Closed
kamilsk opened this issue May 14, 2019 · 0 comments
Closed

forward mapping #5

kamilsk opened this issue May 14, 2019 · 0 comments
Assignees
@kamilsk
Labels
type:refactoring
Projects
Minimum viable product
Milestone
lift 1.0

Comments

@kamilsk
Copy link
Owner

kamilsk commented May 14, 2019

ports are defined as one-to-one, for example, 6379 -> 6379, but it's not so flexible. some ports may be busy or not available. need possibility to define mapping for port forwarding.

REDIS_PORT = 16379 (real is 6379)
@kamilsk kamilsk added this to the lift 1.0 milestone May 14, 2019
@kamilsk kamilsk self-assigned this May 14, 2019
@kamilsk kamilsk added this to To do in Minimum viable product via automation May 14, 2019
kamilsk added a commit that referenced this issue May 30, 2019
@kamilsk
issue #5: define new flag for port mapping
57b5bd1
kamilsk added a commit that referenced this issue May 30, 2019
@kamilsk
issue #5: define execution context (scope) and update port forwarding…
527c0d9 
… logic
Minimum viable product automation moved this from To do to Done May 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@kamilsk kamilsk

Labels
type:refactoring
Projects
Minimum viable product
  
Done
Milestone
lift 1.0
Development

No branches or pull requests
1 participant
@kamilsk