Re: About RawGit, and possible replacements

On 17 Dec 2018, at 10:11, Steve Lee <stevelee@w3.org<mailto:stevelee@w3.org>> wrote:

On 13/12/2018 14:40, Nigel Megitt wrote:
There’s another pattern by the way, that I am not aware of anyone adopting yet, which is to use Github Pages, but to push the build artefacts of PR branches into specific named subfolders. This does mean that whatever build script is used to write to the branch served by Github Pages needs to be aware, and it means that serving the master branch is probably not wise.

The main issue with that pattern is it's hard to use URIs in content that are position independent and so work in pages.io<http://pages.io> and in final hosting. The reason is the root is /subfolder/ and not not  /.

What is “pages.io<http://pages.io>"? Is it in widespread use in W3 specs?


I guess relative URLS and <base> will work but you need to alter <base> between deployments.

That sounds reasonable.

I’d suggest that the current deployed version (after merging to master) be placed at the / level to work around this, assuming that PR previews do not need to be hosted any more finally. Not sure if that also helps.

Nigel



Steve Lee





----------------------------

http://www.bbc.co.uk

This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

---------------------