search

sembr / specification

Semantic Line Breaks Specification
https://sembr.org
75 stars 5 forks source link

The https://sembr.org website appears to be down #10

Closed RohanTalip closed 1 year ago

RohanTalip commented 2 years ago

Screen Shot 2022-08-16 at 12 48 16 PM

waldyrious commented 2 years ago

Seems to be working for me at the time of writing. Maybe it got restored in the meantime since this issue was opened?

xgpt commented 2 years ago

Have you considered hosting what appears to be a static website with github pages? It is free and can even utilize your sembr.org domain name! Please let me know if you'd like assistance in transitioning to that, it would save you hosting costs and leverages the stability of GitHub to ensure that there's far less downtime. Did I mention free?

mattt commented 1 year ago

Thanks for reporting, @RohanTalip. I messed up the DNS configuration in the process of transferring to a different registrar. Apologies for any inconvenience from the downtime. 🙇

waldyrious commented 1 year ago

Just to be clear, I wasn't the reporter of this issue — @RohanTalip was :)

(Though I'll take the opportunity to subscribe to @xgpt's suggestion — why not host in GitHub pages?)

mattt commented 1 year ago

@waldyrious That's sort of besides the point. The site went down because of DNS for my custom domain, not the content hosting provider. The same thing can happen for GitHub pages.

waldyrious commented 1 year ago

Right, that's a fair point. But on the other hand, using GitHub Pages would allow this project to be more collaborative, since people could contribute to the website by merely editing files in the repo (it seems to be essentially the README minus the "Summary" section heading, right?), without requiring an extra deploy/sync step.

It's not a big deal, of course, just a set up I personally find more appealing for open source projects.

mattt commented 1 year ago

@waldyrious Thanks for sharing your feedback. For what it's worth, the site is configured to deploy automatically when the specification is changed. If I were to set this up again from scratch, I would almost certainly use GitHub Pages (which I use in plenty of other projects). But in the interest of avoiding more downtime for a site that I'm not actively working on right now, I'm inclined to keep things working the way they are.