Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Cloudron Forum

Apps | Demo | Docs | Install

Enable extra ports in Matrix app

Scheduled Pinned Locked Moved Matrix (Synapse/Element)
4 Posts 2 Posters 247 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • yusfY Offline
    yusfY Offline
    yusf
    wrote on last edited by yusf
    #1

    Since the discussion of what, if any, appservices should be bundled with the Matrix app may be endless: can we have a bunch of extra tcp ports enabled in the manifest?

    This way we can all integrate appservices ourselves according to our specific needs.

    My suggestion is then to expand CloudronManifest.json to include:

    "tcpPorts": {
        "APP_SERVICE_1": {
            "title": "Application Service 1,
            "description": "The port 1 for extra appservices",
            "defaultValue": 29001
        },
        "APP_SERVICE_2": {
            "title": "Application Service 2,
            "description": "The port 2 for extra appservices",
            "defaultValue": 29002
        },
        "APP_SERVICE_3": {
            "title": "Application Service 3,
            "description": "The port 3 for extra appservices",
            "defaultValue": 29003
        },
        "APP_SERVICE_4": {
            "title": "Application Service 4,
            "description": "The port 4 for extra appservices",
            "defaultValue": 29004
        },
        "APP_SERVICE_5": {
            "title": "Application Service 5,
            "description": "The port 5 for extra appservices",
            "defaultValue": 29005
        },
        "APP_SERVICE_6": {
            "title": "Application Service 6,
            "description": "The port 6 for extra appservices",
            "defaultValue": 29006
        },
        "APP_SERVICE_7": {
            "title": "Application Service 7,
            "description": "The port 7 for extra appservices",
            "defaultValue": 29007
        },
        "APP_SERVICE_8": {
            "title": "Application Service 8,
            "description": "The port 8 for extra appservices",
            "defaultValue": 29008
        },
        "APP_SERVICE_9": {
            "title": "Application Service 9,
            "description": "The port 9 for extra appservices",
            "defaultValue": 29009
        },
        "APP_SERVICE_10": {
            "title": "Application Service 10,
            "description": "The port 10 for extra appservices",
            "defaultValue": 29010
        },
    },
    1 Reply Last reply
    0
  • girishG Do not disturb
    girishG Do not disturb
    girish Staff
    wrote on last edited by
    #2

    I think we need to first find out if these services are separate servers or just installable modules that synapse itself somehow automagically runs. If they are separate servers, we have to make them into a separate matrix integrations app which has all the necessary ports open.

    1 Reply Last reply
    0
  • girishG Do not disturb
    girishG Do not disturb
    girish Staff
    wrote on last edited by
    #3

    I guess https://matrix.org/bridges is the use case right ? It seems they are all just separate servers written in all sorts of languages.

    1 Reply Last reply
    2
  • yusfY Offline
    yusfY Offline
    yusf
    wrote on last edited by
    #4

    Yes, they’re all separate servers. But they each need their own port into the synapse server.

    My suggestion is to leave some extra ports open instead of trying to assemble an app with all/most/some of the appservices.

    This way we can integrate appservices today rather than dreaming about 20 maintained ones sometime in the future, if ever. (Wouldn’t blame anyone for not trying to maintain 20 wildly different appservices since they’re all very fluid pieces of software)

    1 Reply Last reply
    0
  • ericdrgnE ericdrgn referenced this topic on
  • ericdrgnE ericdrgn referenced this topic on

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Login

  • Don't have an account? Register

  • Login or register to search.