Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Is there an existing issue for this?
Describe the bug
In v6 hosting bundle, IIS does not automatically restart the website when it detects the change to the web.config, if a previous change caused an exception. However, in v3 and v5 IIS would restart the site if a change to the web.config was made regardless of previous changes.
Expected Behavior
I update some IIS servers running .Net Core websites without remote access to the IIS server (RDP or PS). However, I do have remote access to the file system.
In .Net Core 3 & 5 I would take a website offline by editing the web.config and renaming the ‘processPath’ to ‘filename..OFF’ , IIS would shut down the site, I copy in the updated files, edit the web.config, rename the ‘processPath’ back to the correct filename, IIS detects the change and starts up the site.
In v6 this no longer works, and I don’t know if that’s intentional or not (see below).
Alternatively, if I rename the web.config to web.config.off, IIS shuts down the site as normal, I update the files, rename the web.config back, IIS detects the change and starts up the site as normal.
The main difference between the two approaches can be seen in the event viewer. In the first where I ‘break’ the web.config IIS adds an info line to the event viewer to say the site has shutdown (detecting the config change) followed by two exceptions to say the renamed processPath could not be found. In the second method where I rename the web.config I still get an info message to say the site has shut down but no error messages.
Steps To Reproduce
'Break' the IIS Site by editing the web.config and changing the processPath to an invalid value. Allow IIS to shutdown, fix the web.config by renaming the processPath back to a valid path. In v3 and v5 the site would come back up automatically, in v6 it does not come back up.
Exceptions (if any)
No response
.NET Version
6.0.2
Anything else?
No response
The text was updated successfully, but these errors were encountered: