Hello Rj,

Thursday January 18 2018, Rj Clay wrote to Michael Dukelsky:

 MD>> I've set the source of GitHub Pages to the master branch of
 MD>> 'homepage' repository and the site now is at
 MD>> https://huskyproject.github.io/homepage/

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

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

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

I've renamed the 'homepage' repository to 'huskyproject.githup.io' but now the
site is at a weird address of
https://huskyproject.github.io/huskyproject.githup.io/
:-(
Are you sure that this variant is better?

Looks like the common form of the site URL is
https://organization_name.github.io/repository_name

Now everyone who cloned the repository as 'homepage' has to run the following
command in the local repository:

(if you access GitHub using ssh)
git remote set-url origin
git@github.com:huskyproject/huskyproject.githup.io.git

or
(if you access GitHub using https)
git remote set-url origin
https://github.com/huskyproject/huskyproject.githup.io.git

It is not mandatory but it is strongly recommended.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20170303