FitNesse.org needs a new home.

[unclebob]

I've been hosting fitnesse.org for twenty years or so; but the time is coming when this should change. I suggest that the contents of fitnesse.org be moved to a github static website. Also, at some point, fitnesse deserves it's own github account.

[fhoeben]

@unclebob an account was created some time time ago (https://github.com/fitnesse). I think an easy step for the Git repo would be if you transferred ownership of the repo to that account. Would that we a good idea?

Currently the site is, of course, served using FitNesse itself. Technically I suppose we could have FitNesse itself generate a static site (although that would be a new feature to create) is that what your thinking of for serving it using GitHub?

[jediwhale]

FYI, I have a need for generating a static site from FitNesse, for another project of mine. If that's the way we want to go, I can raise my priority for that feature and start working on it.

[unclebob]

I'm happy to transfer ownership of the github site to github.com/fitnesse. Does anyone know how to do that? They have the concept of a "successor" which apparently would transfer ownership in the event of my death or incapacity. Anyway, I'll keep looking into this.

As for the static site, fitnesse.org is still running fine in one of my EC2 servers; but it would be better if the fitnesse community took this over somehow. A static site is likely the best option. God known how long that ancient version of FitNesse that powers fitnesse.org will continue to run.

[unclebob]

Hmmm. Transferring ownership looks like it could be complicated. We'd have to coordinate pretty closely to get it done.

https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository

[fhoeben]

It doesn't seem that complicated. But I just scanned quickly.

(And just to make it explicit: fitnesse.org is running the latest FitNesse as far as I'm aware. Although it's HTTP server features are no match for the latest static servers, of course)

[jediwhale]

I will get going on publishing a FitNesse site to a set of static HTML files. Then we can decide where to host them.

[jediwhale]

Just noticed the FrontPage at fitnesse.org is different from the FrontPage here in github. Anyone know where the fitnesse.org version came from?

Update: I found woodybrood/fitnessedotorg but it hasn't been updated for 5 years and doesn't have UserGuide or AcceptanceTests. Is fitnesse.org content merged from two github repos?

[fhoeben]

fitnesse.org is served using the content from https://github.com/fitnesse/fitnessedotorg

When I release a new version of FitNesse:

• I run the build-release.sh script from https://github.com/fitnesse/fitnesse-release (I just noticed the description of the process in the RELEASE.md is a bit outdated, as Bintray no longer exists)
• then I switch to my local copy of https://github.com/fitnesse/fitnessedotorg,
• pull the latest changes from GitHub,
• merge these into a separate branch that is tracking an 'ec2' remote (which is the server actually serving the site in production)
• when I push these changes to the remote it stops the currently running process serving fitnesse.org and starts a new one using the latest content

[jediwhale]

I have a publish feature working and I want to test it on the fitnesse.org content. I looked in https://github.com/fitnesse/fitnessedotorg and I didn't find the user guide. I looked at the build-release.sh script but I didn't see how the user guide from https://github.com/unclebob/fitnesse gets copied - maybe I'm missing something?

EDIT: My mistake, I was running with -o option so it didn't unpack the .FitNesse branch into FitNesseRoot! Removed -o and everything is good.

[jediwhale]

I've published the fitnessedotorg content at https://jediwhale.github.io/fitnessedotorg The download links don't work because they use a DownloadResponder in the FitNesse server. So far, everything else looks good.

[fhoeben]

@jediwhale I think we should probably replace the download responder with regular downloads.
I think there are a couple of options there:

1. just make the .jar file part of the static content
2. add links to download from Maven central (I believe we can have a stable link that always points to the latest release)
3. create proper releases on GitHub, and upload the .jar files as artefacts there

Option 1 is probably easiest to achieve (and similar to what is done now in the fitnessedotorg repository). But if the static content is managed via git (which I believe GitHub.io is) putting large binaries in for each release will make the repository grow very quickly in size and to me doesn't feel quite right.

Option 2 is (once we figure out the stable url) quite easy as well, but does make our site depend on the availability of Maven central. I think that availability is quite good so I don't see a real problem.

Option 3 has the appeal to make the releases nice and visible from the GitHub page. I always found it a pity the releases weren't tracked there.

All these options do have the downside of no longer tracking how often the jar was downloaded. Now I have to admit I didn't look at the often (if at all), but it was a feature we had...

[jediwhale]

Option 3 looks good - I think github even counts the downloads :)
Edit: If Maven is the usual way to do it in the Java world, we should probably do that.

[jediwhale]

Back to work on this... Playing a bit with github releases, looks like a good way to go. It generates release notes from the commit history. I'm going to redo the publisher to use the velocity engine, since it's already being used and generating the html by hand is getting too complicated...

[jediwhale]

Please note a copy of the http://fitnesse.org site is now available at https://fitnesse.github.io/fitnessedotorg/ At this time, it only has a link to the latest version available for download.Let me know if you see any other differences or missing information in the github.io site. I'll add some of the older versions to the download page, and if everything else looks OK, we can point fitnesse.org to the github.io site.

[mh182]

I just want to mention that it would make sense to redirect requests from http://fitnesse.org/ and https://fitnesse.org to https://fitnesse.github.io/fitnessedotorg/.

I just read a book which provided a link to http://fitnesse.org. My Firefox redirects http://fitnesse.org to https://fitnesse.org which shows an "Unable to connect" error.

[fhoeben]

@mh182 I believe there was an issue with the server of http://fitnesse.org/, but that is fixed now. For me that link now works again. Is your Firefox still taking you to a https url automatically (which indeed does not exist)?

@unclebob to me transferring the repo to the fitnesse organization on GitHub does not seem that complex. Can we maybe discuss the issues you see in further detail?

One thing I do see we need to do to take over fitnesse.org is that we would have to change the DNS registration for fitnesse.org to point to the GitHub static site instead. I believe there is some documentation at https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site

[mh182]

http://fitnesse.org/ is working now.

[aquddos123]

It looks like http://fitnesse.org broke again.

[fhoeben]

Back up

[aquddos123]

Thanks @fhoeben. Its working now.

[djbrown]

fitnesse.org seems broken again (Firefox and Chrome).
also docs.fitnesse.org doesn't work neither.
fitnesse.github.io/fitnessedotorg works fine though.

[fhoeben]

Seems to be fine now

[fhoeben]

I believe the setup using GitHub pages to serve https://fitnesse.org works quite well.
And I am under the impression that you are not quite ready to transfer the repository to the fitnesse GitHub organization yet, @unclebob.

Closing this issue