You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If CONTENT_URL_PREFIX is not being set, but WORKSHOPS_URL is, and content.url is not set in the workshop file, calculate what CONTENT_URL_PREFIX would be by using the directory of the URI that specifies the location of the workshop file.
which forces people to fix it by setting CONTENT_URL_PREFIX.
That is, it points at ocp-3.9 when should be ocp-3.11. It could instead use .. for content.url and wouldn't have to worry then about it ever needing to be updated.
Note, if it is mean't to work like this in any way I am not seeing it, and get errors when content.url is not set or when putting . as value.
The text was updated successfully, but these errors were encountered:
If
CONTENT_URL_PREFIX
is not being set, butWORKSHOPS_URL
is, andcontent.url
is not set in the workshop file, calculate whatCONTENT_URL_PREFIX
would be by using the directory of the URI that specifies the location of the workshop file.Thus if
_workshop.yml
file is just:and
WORKSHOPS_URL
was:for
content.url
use:Further, if
content.url
does exist, but includes a relative filename path, append that to the end of the calculated location. Thus if had:would use:
or when normalised:
This would make it easier to avoid situations like:
where even though in
ocp-3.11
branch it has:which forces people to fix it by setting
CONTENT_URL_PREFIX
.That is, it points at
ocp-3.9
when should beocp-3.11
. It could instead use..
forcontent.url
and wouldn't have to worry then about it ever needing to be updated.Note, if it is mean't to work like this in any way I am not seeing it, and get errors when
content.url
is not set or when putting.
as value.The text was updated successfully, but these errors were encountered: