1.0.7

Specify http protocol for the returned url for now until https issue is fixed.

1.0.6

Revert the https release due to issue with https certificate which is going to be solved very soon.

1.0.5

Revert removing protocol from the url resolved by the request.to() promise, and use https as default protocol.

1.0.4

Https is here !

We now support the https protocol. For now the structure of the result you get from the transfer.to() method is the following ;

var transfer = require('transfer');

transfer.to('http://localhost:8080')
  .then(result => {
    console.log(result); 
    /* { token      : '2KFQNpM', 
         url        : '2KFQNpM.transfer.pub', 
         pathUrl    : 'path.transfer.pub/2KFQNpM',
         protocols  : ['http', 'https'] } */
  });

1.0.3

• Fix token change when socket drops connection and connect again to server.
  • The client id is cached with the token on the server for 24 hours, in case a reconnection happens with same client id and same token, the communications resume between client and server.

1.0.2

• Bump version for corrupted published version at npm

1.0.1

• Fix url:port fallbacks
• Fix encoding when requesting resource
• Fix response landing on the wrong handler
• deps:
  • Accepting only minor releases
• tests:
  • Add request reproduction tests

1.0.0 (First release)

This is the first release for this package. Still a long road to go to make it better, but it's acceptable as a first iteration with basic features.

Story behind this project:

As I was at work in my current job, I was working on a task that requires a lot of configurations to prepare a testing environment. I should specify what url the provider will send an http request to, as well as whitelisting this url. So I decided to automatize this process by using ngrok, the issue is that the step where I need to whitelist the domain name should be done manually and it doesn't support wildcards. So I had 2 options, wether I go for a paid subscription to get a reserved domain, or I just build something my own. Now the goal was to automatize this process to start making my tests right away, but it's just for testing and not production, and this testing is not even something recurrent. So it was not wise to go for paid subscription for my situation, and I should not deny that building something my own is a lot of fun.

I had an AWS free tiers account, which still have may be 10 months of free cloud services, let's see how the next 10 months will be for this project, if I notice a lot of usage I'll figure out a way to scale out.

This first release has the feature that I was looking for which is the ability to use a fixed domain

var transfer = require('transfer');

transfer.to('http://localhost:8080')
  .then(result => {
    console.log(result); 
    /* { token   : '2KFQNpM', 
         url     : 'http://2KFQNpM.transfer.pub', 
         pathUrl : 'http://path.transfer.pub/2KFQNpM' } */
  });

Now I only need to whitelist path.transfer.pub and I'll have an easily automatized process.

Feel free to drop any new ideas, help this project grow and let's have fun.