Fix for issue that suddenly appeared for reasons I can't determine in which the corp docs hosted site stopped working with the same manual build I've always been using as it started to try to find the links from the root of the site instead if relatively in the docs folder. Adding the site_url seems to have fixed this issue and doesn't break a local install copy of the docs from within AyaNova so this seems to be resolved.

This commit is contained in:
2024-05-03 22:35:35 +00:00
parent 7ccbe545dd
commit 68966ea668
2 changed files with 23 additions and 4 deletions

View File

@@ -6,8 +6,9 @@ theme:
logo: "img/logo.svg" logo: "img/logo.svg"
site_name: AyaNova manual site_name: AyaNova manual
site_dir: "../../../server/AyaNova/wwwroot/docs" site_dir: "../../../server/AyaNova/wwwroot/docs"
site_url: https://ayanova.com/docs/
strict: true strict: true
copyright: Copyright © 2022-2024 Ground Zero Tech-Works Inc. REV-2024-05-03 copyright: Copyright © 2022-2024 Ground Zero Tech-Works Inc. REV-2024-05-03-c
extra: extra:
generator: false generator: false
# Extensions # Extensions

View File

@@ -1,6 +1,24 @@
@REM cd c:\data\code\raven\docs\8.0\ayanova
@REM mkdocs build -s
@REM cd c:\data\code\raven\docs\8.0\customer
@REM mkdocs build -s
@REM cd ..\..\..
@REM pause
@echo ****************** CLEAN ALL OUTPUT FOLDERS **********
rmdir c:\data\code\raven\server\AyaNova\wwwroot /s/q
mkdir c:\data\code\raven\server\AyaNova\wwwroot
rmdir C:\data\code\raven\dist\installers /s/q
mkdir C:\data\code\raven\dist\installers
@echo ******************** BUILD MAIN DOCS ******************************
cd c:\data\code\raven\docs\8.0\ayanova cd c:\data\code\raven\docs\8.0\ayanova
mkdocs build -s mkdocs build
@echo ******************** BUILD CUSTOMER DOCS ******************************
cd c:\data\code\raven\docs\8.0\customer cd c:\data\code\raven\docs\8.0\customer
mkdocs build -s mkdocs build
cd ..\..\.. cd ..\..\..
pause pause