Fix glance configuration error

This commit is contained in:
Daniel Cosme
2026-05-07 14:22:55 -04:00
parent 237db5abb4
commit 81ccb02f5f
2 changed files with 6 additions and 10 deletions
+3 -5
View File
@@ -6,6 +6,9 @@ data:
background-color: 186 21 20 background-color: 186 21 20
contrast-multiplier: 1.2 contrast-multiplier: 1.2
primary-color: 97 13 80 primary-color: 97 13 80
# Note: assets are cached by the browser, changes to the CSS file
# will not be reflected until the browser cache is cleared (Ctrl+F5)
custom-css-file: /assets/user.css
branding: branding:
custom-footer: | custom-footer: |
@@ -28,11 +31,6 @@ data:
# svilen: # svilen:
# password: 123456 # password: 123456
theme:
# Note: assets are cached by the browser, changes to the CSS file
# will not be reflected until the browser cache is cleared (Ctrl+F5)
custom-css-file: /assets/user.css
pages: pages:
# It's not necessary to create a new file for each page and include it, you can simply # It's not necessary to create a new file for each page and include it, you can simply
# put its contents here, though multiple pages are easier to manage when separated # put its contents here, though multiple pages are easier to manage when separated
+3 -5
View File
@@ -3,6 +3,9 @@ theme:
background-color: 186 21 20 background-color: 186 21 20
contrast-multiplier: 1.2 contrast-multiplier: 1.2
primary-color: 97 13 80 primary-color: 97 13 80
# Note: assets are cached by the browser, changes to the CSS file
# will not be reflected until the browser cache is cleared (Ctrl+F5)
custom-css-file: /assets/user.css
branding: branding:
custom-footer: | custom-footer: |
@@ -25,11 +28,6 @@ server:
# svilen: # svilen:
# password: 123456 # password: 123456
theme:
# Note: assets are cached by the browser, changes to the CSS file
# will not be reflected until the browser cache is cleared (Ctrl+F5)
custom-css-file: /assets/user.css
pages: pages:
# It's not necessary to create a new file for each page and include it, you can simply # It's not necessary to create a new file for each page and include it, you can simply
# put its contents here, though multiple pages are easier to manage when separated # put its contents here, though multiple pages are easier to manage when separated