Can you "pause" the zetta server? Or separate _run from listen?

[wooliet]

I am looking for a way to "pause" the zetta server so that HTTP requests are rejected (with 503 code). The purpose is to be able to start zetta (call listen) but prevent activity until other system initialization is complete.

An alternative might be to remove call to Zetta.prototype._run from inside Zetta.prototype.listen and offer the ability to call them separately.

[wooliet]

Went with a zetta app that blocks requests until a server.pubsub message comes in.

module.exports = function requestBlockApp(server) {
  var goodToGo = false;
  server.pubsub.subscribe('good-to-go', function(){
    goodToGo = true;
  });
  server.httpServer.cloud.use(function(handle) {
    handle('request',  { affinity: 'hoist' }, function(env, next){
      if(goodToGo) {
        return next(env);
      }
      if(env.argo.currentUrl.indexOf('/_initiate_peer') === 0) {
        return next(env);
      }
      env.response.statusCode = 503;
      env.response.setHeader('Content-Type', 'application/json');
      env.response.end(JSON.stringify({
        message: 'my error message'
      }));
    });
  });
};

Question

Not letting _/initiate_peer pass through causes continuous retries. Is there anything else I should be allowing through by default?

[abdul49]

Hi Wooliet,
I am also looking for a same solution to pause the "zetta listen" first perform some authentication and then establish the connection.
I need help because i am new to node js and it is difficult to understand the code without explaination .