Thomas Sibley

Supporting redirects (i.e. resolution of partial dataset paths) for non-core/staging sources would take substantial consideration of how that information is stored (a manifest file, but [we'd like to get rid...

I put out [a call for further discussion on Slack](https://bedfordlab.slack.com/archives/C01LCTT7JNN/p1699055751187019), and that's generated a little more commentary there.

We (@jameshadfield @joverlee521 @j23414 @huddlej @kimandrews @victorlin @tsibley) talked for 75 minutes on this topic during today's dev chat, but consensus on an expectation was not reached. To summarize, I...

Personally, to be frank, it is exhausting to have to advocate for what would be basic best practice accepted (even expected!) in many other software shops. :/

@victorlin [wrote](https://github.com/nextstrain/nextstrain.org/issues/748#issuecomment-1795948477): > 1. A resource is created on AWS console. This is covered by [docs on import](https://docs.nextstrain.org/projects/nextstrain-dot-org/en/latest/terraform.html#importing-resources) and seems straightforward, though I haven't had the chance to try it...

> as well as walk thru a new separate example of using Terraform to manage new GitHub Actions / AWS Batch integrations that I plan to write as part of...

https://github.com/nextstrain/infra#readme

This [came up again](https://bedfordlab.slack.com/archives/C02Q4Q5S85A/p1646761817573609?thread_ts=1646436089.277949&cid=C02Q4Q5S85A) today on Slack. Two considerations if we remove `manifest_guest.json` and start crawling S3 for core/staging: - [ ] There's a bunch of stuff in the buckets...

I'd recommend taking the same approach I used to integrate the Gatsby dev server into the nextstrain.org codebase. The gist is that we'd run `auspice develop` as a sidecar server...

Yep. The identifier might be a monotonically increasing integer or it might be the commit id of the deployed code. (We discussed both but didn't decide.) > For review apps...