Skip to content

Custom port forwarding #693

@Anmol1696

Description

@Anmol1696

Sometimes, people need to expose custom ports themselves.

Instead of increasing the ports list or dir, we could have a section for custom ports, like:

Option 1

chains:
  - id: osmosis-1
    name: osmosis
    ports:
      rpc: 2657
      custom:
        - name: eth-http-jsonrpc
          target: 8467
          port: 8467

Option 2:

chains:
  - id: osmosis-1
    name: osmosis
    ports:
      rpc: 2657
    customPorts:
      - name: eth-http-jsonrpc
        target: 8467
        port: 8467

Custom ports could be more open ended, and anything from a service can be opened up with custom ports.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions