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

Is redbird no longer maintained? #267

Open
Reinitialized opened this issue Oct 16, 2020 · 8 comments
Open

Is redbird no longer maintained? #267

Reinitialized opened this issue Oct 16, 2020 · 8 comments

Comments

@Reinitialized
Copy link

Reinitialized commented Oct 16, 2020

I've noticed its been over 10 months since the npm package has been updated, but seems work is being continued within this repo. Is the npm variant no longer maintained, or is there a release waiting to be finished before updating? and after further review, it seems progress on redbird has mostly grind to a halt.

Is this project dead? Should I look into alternatives for my "production" applications?

@Reinitialized Reinitialized changed the title Is NPM package no longer maintained? Is redbird no longer maintained? Oct 17, 2020
@roslovets
Copy link

I have migrated form redbird to greenlock-express. At least it works with Node v14.15.0

@crossinghoods
Copy link

Having spent about a day trying to port over and simplify Redbird to Typescript I ended up going with http-reverse-proxy-ts instead (https://www.npmjs.com/package/http-reverse-proxy-ts)

If you are looking for a quick fix here is the code to help get you up and running - 2 files, as usual npm install then node index.js

index.js

"use strict";

Object.defineProperty(exports, "__esModule", { value: true });
const http_reverse_proxy_ts_1 = require("http-reverse-proxy-ts");
const logger = new http_reverse_proxy_ts_1.Logger();

const letsEncryptServerOptions = {
    noVerify: true
};

const httpReverseProxyOptions = {
    letsEncryptOptions: letsEncryptServerOptions,
    httpsOptions: {
        port: 443,
        certificates: {
            certificateStoreRoot: './certs'
        },
    },
    log: logger,
};

const routingOptions = {
    https: {
        redirectToHttps: true,
        letsEncrypt: {
            email: 'domain@maintainer.email..com', // Update this to the domain manager's email
            production: false, // put it to true when you've tested it
        }
    }
};

const proxy = new http_reverse_proxy_ts_1.HttpReverseProxy(httpReverseProxyOptions, http_reverse_proxy_ts_1.LetsEncryptUsingAcmeClient);

proxy.addRoute("https://www.example.com", "127.0.0.1:8000", routingOptions);
logger.info(null, "Proxy server started");

package.json

{
  "name": "quick-reverse-proxy-fix",

  "version": "1.0.0",
  "description": "Reverse Proxy used to forward requests to servers",
  "main": "index.js",
  "scripts": {
    "bp": "npm run build:prod",
    "develop": "tsc -w",
    "build:prod": "tsc -p tsconfig.prod.json"
  },
  "keywords": [
    "Reverse",
    "Proxy"
  ],
  "author": "Your name",
  "license": "MIT",
  "dependencies": {
    "http-reverse-proxy-ts": "^1.0.1"
  },
  "devDependencies": {
    "@types/node": "^14.14.9"
  }
}

@roslovets
Copy link

For my purposes I have created the simpliest greenlock-proxy.

Of course it's not so powerfull as redbird, but it's easier to use if you only interested in https reverse proxy with fully automatic Let's Encrypt handling.

@crossinghoods
Copy link

For my purposes I have created the simpliest greenlock-proxy.

Of course it's not so powerfull as redbird, but it's easier to use if you only interested in https reverse proxy with fully automatic Let's Encrypt handling.

Tested your solution, works very well! Only caveat is using expressJS behind the scenes which is an extra layer with lots of dependencies. I might start a new repo based on your implementation 👍

@roslovets
Copy link

I might start a new repo based on your implementation 👍

It would be great, because I'm not a professional web developer.

@crossinghoods
Copy link

I might start a new repo based on your implementation 👍

It would be great, because I'm not a professional web developer.

Done a great job even though you claim to not be a professional web developer. I've seen professionals done way worse than what you've produced!

@Starystars67
Copy link

Starystars67 commented Dec 2, 2020

I too would like to know if this project is dead now. I'm about to be making quite a sizeable upgrade and revision to some projects I have running and I use redbird as the reverse proxy as it has a very nice to use system. I hope its not dead but certainly does appear to be.

For my purposes I have created the simpliest greenlock-proxy.

This does look very similar to redbird. Given how new it is I cant wait to see where it goes. Looks to be following the very nice simple lines redbird used. Cant wait to see what the future holds for it!

On a side note is it worth someone taking over the redbird project by forking / cloning and then should we hear back from the original project developer they can either bring the continued work back into it or choose to formally end it here and have it continue in a new repository with new maintainers and contributors?

@manast
Copy link
Member

manast commented Dec 2, 2020

It is not dead as far as I am concerned but I do not have so much time to spend on it, besides it does all I need it to do. Of course it can be cloned and maintained by others, but honestly, for niche projects like this one it is most likely not going to gain any traction.

nodiscc added a commit to awesome-selfhosted/awesome-selfhosted that referenced this issue Apr 8, 2023
nodiscc added a commit to awesome-selfhosted/awesome-selfhosted that referenced this issue Apr 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants