I 've found out that Azure websites (trial version) doesn't autostart my node sever process (it starts only when I load the url in the web browser); and that when there are no requests in a while, the process is killed.

I mean, when I git push my server, I would like it to start running immediately and continuously.

I read (here, for example) that this might have to do with the way iisnode manages Azure Websites, and that I can't do anything to change it. Is this the actual way Azure websites work? Is there any way I can deal with this?

Thanks in advance,

Bruno.

You've find the answer. There is no other answer.

The process termination because of inactivity comes from IIS - there is Idle Timeout setting. Which to my knowledge is not configurable in Azure Web Sites (at least not Free tier). Check out also this SO question and its answer to get better understanding on why you can't change this timeout on the FREE and STANDARD tiers.

And here is an interesting workaround to avoid this idle timeout. Actually if you use technique, you will also have kind-of "auto start", in terms that when your scheduler hits your site after a new deployment, it will "boot up".