Convert subdomain install to subdirectory install
NYCDH does not have a wildcard SSL certificate, so we cannot enforce HTTPS across the entire NYCDH multisite install due to our multisite configuration using a subdomain set up.
Converting our multisite install from a subdomain configuration to a subdirectory one would allow us to enforce HTTPS.
I'll look into making this conversion some time after DH Week is completed so we won't disrupt anything.
#7 Updated by Raymond Hoh over 2 years ago
I'm almost ready to make the switch to a subdirectory install, but before I do, can you audit the list of sites here:
And make sure to either delete or archive sites that are no longer active? The reason I ask is making the switch will require some manual work from me to update the site URLs.
Let me know if you have any questions.
#8 Updated by Raymond Hoh over 2 years ago
I took the liberty of going through all the sites on NYCDH.
These are the ones we can keep for sure:
These ones have test content and are candidates for removal:
- http://montclair.nycdh.org/ (just a landing page to another site)
- http://bpham.nycdh.org/ (has unpublished drafts, last active 2014, but basically empty)
- http://aids.nycdh.org (basically empty, except for a few intro posts)
- http://jlab.nycdh.org (basically empty, except for an intro post)
The rest of the sites not listed can be deleted.
Let me know what you think before I do the subdirectory switchover.
#9 Updated by Raymond Hoh over 2 years ago
- Status changed from New to Resolved
I've gone ahead and converted the subdomain install into a subdirectory one. I've also written a redirect rule so all older subdomain links should get automatically redirected to their subdirectory equivalent.
When you have a chance, this would be a good opportunity to remove sites that have either no content or barely any content at all. I've already made a site audit in my previous post. Let me know what you think.
For now, I'm going to mark this as resolved. Let me know if you encounter any bugs.