Statping: Theme Editor Not Working for Docker

Created on 21 May 2020 · 6Comments · Source: statping/statping

Describe the bug

Clicking "Enable Local Assets" in "Theme Editor" in the Settings, does not enable custom theming. The page does not change. And the following appears the browser console:

Error: "Request failed with status code 500"

Looking at the statping log, I find:

statping    | INFO[2830] creating assets in folder: /app/assets
statping    | INFO[2830] Dump Statping assets into /app/assets         type=source
statping    | INFO[2830] Creating folder '/app/assets'                 type=source
statping    | INFO[2830] Creating folder '/app/assets/js'              type=source
statping    | INFO[2830] Creating folder '/app/assets/css'             type=source
statping    | INFO[2830] Creating folder '/app/assets/scss'            type=source
statping    | INFO[2830] Inserting scss, css, and javascript files into assets folder  type=source
statping    | INFO[2830] /banner.png
statping    | INFO[2830] /css/main.css
statping    | INFO[2830] /css/main.css.gz
statping    | INFO[2830] /css/style.css
statping    | INFO[2830] /css/style.css.gz
statping    | INFO[2830] /css/vendor.css
statping    | INFO[2830] /css/vendor.css.gz
statping    | INFO[2830] /favicon.ico
statping    | INFO[2830] /js/bundle.js
statping    | INFO[2830] /js/main.chunk.js
statping    | INFO[2830] /js/main.chunk.js.gz
statping    | INFO[2830] /js/polyfill.chunk.js
statping    | INFO[2830] /js/style.chunk.js
statping    | INFO[2830] /js/vendor.chunk.js
statping    | INFO[2830] /js/vendor.chunk.js.gz
statping    | INFO[2830] /robots.txt
statping    | INFO[2830] Copying robots.txt to /app/assets/robots.txt  type=source
statping    | INFO[2830] Copying banner.png to /app/assets/banner.png  type=source
statping    | INFO[2830] Copying favicon.ico to /app/assets/favicon.ico  type=source
statping    | INFO[2830] Compiling CSS from SCSS style...              type=source
statping    | INFO[2830] Compiling SASS /app/assets/scss/main.scss into /app/assets/css/main.css  type=source
statping    | INFO[2830] Running command: /usr/local/bin/sass /app/assets/scss/main.scss /app/assets/css/main.css
statping    | Internal Error: File to read not found or unreadable: /app/assets/scss/main.scss
statping    | ERRO[2830] Failed to compile assets with SASS exit status 65  type=source
statping    | ERRO[2830] /usr/local/bin/sass /app/assets/scss/main.scss /app/assets/css/main.css  type=source
statping    | INFO[2830] Statping assets have been inserted            type=source
statping    | ERRO[2830] failed to compile assets, exit status 65  Internal Error: File to read not found or unreadable: /app/assets/scss/main.scss
statping    | : exit status 65  type=handlers
statping    | ERRO[2830] sending error response for /api/theme/create: failed to compile assets, exit status 65  Internal Error: File to read not found or unreadable: /app/assets/scss/main.scss
statping    | : exit status 65  code=0 method=GET type=handlers url=/api/theme/create

I'm using docker image: statping/statping:latest which was Statping 0.90.41 when I experienced this behavior.

To Reproduce

Steps to reproduce the behavior:

Using the docker image: statping/statping:latest
Go to the Theme Editor in the settings
Click on the "Enable Local Assets" button
Check log for error

Expected behavior

I would expect clicking "Enable Local Assets" would result in allowing me to define a custom theme without throwing errors.

bug stale

Source

wkelton

👍7

All 6 comments

I believe all that is missing is for main.scss to be copied to /app/assets/scsss.

I manually copied main.scss to /app/assets/scss/main.scss in my container. After I reloaded the Theme Editor page, I was able to paste in my custom theme and click "Save Style". SASS was compiled successfully:

statping    | INFO[4573] Compiling SASS /app/assets/scss/main.scss into /app/assets/css/main.css  type=source
statping    | INFO[4573] Running command: /usr/local/bin/sass /app/assets/scss/main.scss /app/assets/css/main.css
statping    | INFO[4573] Compiling SASS /app/assets/scss/base.scss into /app/assets/css/base.css  type=source
statping    | INFO[4573] Running command: /usr/local/bin/sass /app/assets/scss/base.scss /app/assets/css/base.css
statping    | INFO[4573] Compiling SASS /app/assets/scss/mobile.scss into /app/assets/css/mobile.css  type=source
statping    | INFO[4573] Running command: /usr/local/bin/sass /app/assets/scss/mobile.scss /app/assets/css/mobile.css
statping    | INFO[4573] SASS Compiling is complete!                   type=source

wkelton on 21 May 2020

👍1

Same

mrspartak on 14 Jun 2020

I see a similar issue, but after enabling the theme in settings - none of the sass files are copied to the sass folder.
I wget them from github repo and it seems to work.