[tarl0s]

At Hakuna we use our own service to start and stop our Jira and NPM servers; the instances are automatically stopped at night or whenever nobody needs to do `npm install`.

In our use case, the EC2 instance starts in about 50 seconds, with another minute needed to start the Jira service.

We have a demo, deployable directly from our CLI, that starts a Nginx server on an Oracle Cloud instance in less than 40 seconds.

If the instance is being stopped and a new request arrives, it will have to wait shutdown + startup, yes.

[gregmac]

Thanks.

Is there UI feedback to the user during the wait, or does the browser just show "waiting for response" for the whole time? If a user refreshes the browser a bunch of times during the wait, will the Hakuna proxy give up on those requests or still pass all of them through to the target server?

[tarl0s]

We cannot provide UI feedback during the wait: being a HTTPS proxy, we would need the SSL certificate to reply to the request, otherwise it would be some kind of MitM.

If the client closes the socket before the start of the server, the proxy gives up on its requests.

[mkl]

You should probably check your website on mobile. For me on Firefox Android, the unmoving header takes up 60-70% of the screen and the actual scrolling content is crammed into the bottom fraction.