Michael Dukelsky wrote to Rj Clay:
MD> Hello Rj,
MD> 
MD> Wednesday January 17 2018, Rj Clay wrote to Wilfred van Velzen:
MD> 
MD>  WvV>>  RC> https://huskyproject.github.io.
MD>  WvV>>
MD>  WvV>> This url gives a 404 error...
MD> 
MD>  RC>    And will until the 'huskyproject.github.io' repo is created 
MD>  RC> either by renameing the 'homepage' repo or forking it).  That's why
MD>  RC> I said "would be"...
MD> 
MD>  RC>     It's part of GitHubs 'Pages' functionality. If you're not aware;
MD>  RC> that's where if one has a repo named '  RC> name>.github.io', one can have web site there and GH makes it
MD>  RC> available as a website.
MD> 
MD> In fact there are more options to publish the 'homepage' repository.
MD> 
https://help.github.com/articles/configuring-a-publishing-source-for-github
MD> -pages/
MD> 
MD> I've set the source of GitHub Pages to the master branch of 'homepage' 
MD> repository and the site now is at
MD> https://huskyproject.github.io/homepage/

   Yes, that's the way to do it for an individual git repository, usually 
using
a branch named 'gh-pages' and that's how I've done it for other sites I'm
associated with at github.  For the user or project wide site, the
repository would need to be named huskyproject.github.io, in order for it to
be available at https://huskyproject.githup.io.  One can then also have a 
domain
name that can redirect to that but someone one would have to maintain the
domain name in dns; I use that functionality for one of mine site there.


MD> But the site is outdated and needs an update. It would be very good if you 
MD> could do the job.

    I'd be glad to (in part to make up for how long it's been since I worked 
on
 the one at SourceForge...) but it's the web site for the whole husky 
project
so I'll wait until the repository is renamed properly for that.
 



Jame


    Greetings, Rj Clay
    email: admftn{at}ftn.rocasa.net

--- MBSE BBS v1.0.6.8 (GNU/Linux-i386)