simfactory download page points to outdated version

Create issue
Issue #1103 closed
Roland Haas created an issue

currently points to for the "current" version, which is from the last release


Comments (14)

  1. Roland Haas reporter
    • removed comment

    This is still the case. Who actually has access to the repo that hosts the website?

  2. Ian Hinder
    • removed comment seems to be a server hosted at CCT:

    $ host has address$ host domain name pointer domain name pointer

    At some point in time, the website was a branch in the simfactory subversion repository:

    Ian-Hinders-MacBook-Pro:simfactory ian$ pwd
    Ian-Hinders-MacBook-Pro:simfactory ian$ git svn info
    Path: .
    Repository Root:
    Repository UUID: cde0f5ca-dead-0410-9a94-d5ce4c5b1455
    Revision: 2435
    Node Kind: directory
    Schedule: normal
    Last Changed Author: knarf
    Last Changed Rev: 2435
    Last Changed Date: 2016-10-17 21:15:16 +0200 (Mon, 17 Oct 2016)

    Hopefully there was a hook which updated the checkout on the webserver after each commit.

    From the commit log, Frank, Erik and I have commits, so we probably had commit access. However, I can no longer commit.

    There is no www branch in the bitbucket simfactory 2 repository, and there is no bitbucket repository in the simfactory project for the website.

    Steve, perhaps you could have a look at and see how the webserver is configured?

  3. Roland Haas reporter
    • removed comment

    Since the repo is publicly visible anyway, would it make sense to transfer the commit history into then redirect on to ?

    That of course still requires that someone who can still commit to the current svn repo changes index.php (or .html) to contain the redirect to the bitbucket page.

  4. Ian Hinder
    • removed comment

    Really, we should get to the bottom of what's going on with the existing website. Someone at CCT must know something about this? Or Erik?

    The redirect you mentioned would be ugly, as the user would go to and be redirected to, and then continue to see that URL. Better would be to point the DNS entry at that site using a CNAME record. Unfortunately, unlike github, for which this works perfectly, bitbucket does not support this, and has no plans to support it (see Another option for static hosting that I have used is netlify. This will create a static website for free based on a git repo (both github and bitbucket are supported), and I have used them before. I just tried it out with the repo, and the result can be seen at at They use randomly-generated site names by default. It took about a minute to set up. However, they support CNAMEs, so you can repoint a domain to point at their site. They also support TLS via LetsEncrypt. I have used both these features and have had no problems with them.

  5. Roland Haas reporter
    • removed comment

    That sounds nice, given that bitbucket does not let us use "nice" urls, even if it means involving another company (that may fold).

    To clarify: to use we could keep the website repos on bitbucket (or github unless github supports https with our own URLs) and set up some hook to have a push to the website repo (or a branch in it) update the website on

    Do they support only strictly static websites or Jekyll based automation similar to what eg github supports?

  6. Steven R. Brandt
    • removed comment

    I'm back from all my travel. I'll try to get access to this machine and the svn repo.

  7. Ian Hinder
    • removed comment

    Roland: yes, we would keep the repos where they are, and don't even need to set up a hook. Netlify automatically detects the change to the repo and regenerates the site. They also support Jekyll and possibly other things.

  8. Log in to comment