Patrick Hulce

Rough roadmap idea if we proceed: 1. Abstract away all fetching of statistic definitions behind a function/API call that requires the config + project as input 2. Add a flag...

There is no roadmap outside of what's contained here in GitHub issues with respective priority, though existence of an issue is not a guarantee it will be implemented. No one...

Ah so not really a service privacy policy (that would be mostly up to you as the operator of the service and data steward for your clients) but functionality for...

As a thought for your workaround, I would personally setup a proxy in front of LHCI that routes to multiple instances based on the domain each locked down with basicAuth...

Thanks @LukeLeber! Two followup questions: - Do you have any insight to share into how that works with the uploading portion of server functionality? For example, is it easy to...

> Unfortunately, I don't have any insight into how this change would work, functionally. I haven't had time to take a deep dive into the project source yet. Sorry I'll...

Thanks @somehowchris! I think that approach moves the responsibility of mapping actions/objects back onto LHCI. The most likely way I see this resourced and implemented is something closer to your...

That's essentially what I was thinking of yes @somehowchris. LHCI would just fail all incoming requests with a 503 error until the migration completes.

> So just a 503 or 503 with a html page for the users? I'm thinking a dead simple `503 Service Unavailable (Migration)` response. This is a pretty narrow occurrence...

Anyone familiar with docker deployment on AWS is welcome to add a section for it, PRs much appreciated :)