WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Utilize ngrok to be able to run on non-public facing cluster #16

@jpopelka

Description

@jpopelka

There's Release bot as Github App, but it's currently not running because we lack resources on Openshift Online, where the bot is deployed.

For the Github App to be able to talk to the service (the deployed bot) the service url needs to be publicly available which rules out most of our internal Openshift clusters.

Today I woke up and got an idea that we could possibly work-around it with ngrok.
Not sure it'd work, but worth trying.
The thing is that AFAIK one has to have paid account to use custom subdomains, so we'd probably need to run the ngrok in the same pod as the release-bot - which already is quite stuffed.

I've also found @vpavlin's https://github.com/vpavlin/ngrok-openshift which we could borrow some bits from ;-)

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