Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Ask HN: Permantly phasing out a site – How to do it properly?
1 point by moepstar on May 12, 2015 | hide | past | favorite | 2 comments
o, i have a website which i haven't updated in years and am finally planning to shut it down but at the same time want to make sure it is still there to read for the public (niche website, still has some historical information that might be relevant for some).

Since it is running on WordPress and i am not exactly keen on updating and maintaining that anymore, what would be the best way to still have it available for others to read and get rid of WordPress?

One way i could see is spider and save it with something like HTTrack and put up the static HTML-Copy. The other way i can think of is to provide a link to a web.archive.org snapshot.

However, since the web.archive.org snapshot might disappear in the case of a HDD-failure there (and IIRC they don't keep backups, what's gone is gone for good) this options isn't ideal.

I plan on keeping the domain, since the few $ for an .org domain a year are worth the inconvenience to me compared to updating all registrations and whatnot which still have that domains email somewhere in user profiles etc.

HN, how do you deal with such situations?



Why not disable guest commenting/posting. Then delete the login page? That will effectively turn the page into an archive. You would still have to keep the database running, but that is trivial.


Still, there'll be truckloads of WP scripts (and at least one theme) under the hood which might or might not have exploits found in the future...

Therefore i, ideally, want to get rid of the liabiltiy WordPress is.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: