-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transfer ownership of S3 instance backing whatpr.org #98
Comments
@tobie what would the concrete work here be? Are different S3 buckets used for WHATWG and everything else, or is it just that the custom domain (whatpr.org) makes the URLs nicer for WHATWG preview? How abstracted away is the storage backend, could it be replaced with something on DigitalOcean easily to keep all our hosting in one place? |
It's a dedicated S3 instance. With some other AWS services to handle the domain name (notably Route 53, iirc). I'm about to setup an Open Collective account to get funding to continue supporting PR Preview and Specref. If that gets funded, I'm happy to continue maintaining that part of the infrastructure and continue to improve the project (e.g. adding support for mono repos like the CSSWG's). |
@tobie did you get Open Collective set up, and is the plan to keep supporting PR Preview? |
I have, though I haven't promoted it. |
@tobie could you create a group or whatever the best organization unit is on AWS and add philip@foolip.org so I can see the setup? I'm evaluating what it'd look like to fix #107 using AWS and the setup you describe in #89 (comment) is similar to what I'm attempting. |
Haha. I'm not touching AWS permissions with a 10-foot pole unless I have three free days behind it to fix whatever I break doing so. I can walk you through it over a call if you want me to, however. |
Oh my, sounds like you've had some things blow up in the past :) Let's not to this until there's a practical reason beyond my curiosity, then. |
I think this is done? |
Yes. iirc. |
@foolip @sideshowbarker I think you'd be ideal for handling this given you handle most of the existing server infrastructure. Let me know if that'd be prohibitive.
cc @tobie
The text was updated successfully, but these errors were encountered: