Posts: 7
Threads: 1
Joined: Sep 2022
Reputation:
0
09-15-2022, 01:23 AM
(This post was last modified: 09-18-2022, 04:04 PM by jener8tionx .
Edit Reason: Moode, not Mood
)
Thank you in advance for any help you can provide.
I have a 1600x480 screen and I am trying to modify the CSS to have a more useful display. I am running a pi 3b with Moode 8.1.2 64bit on a fresh install. The only setting changes were to set wifi settings, turn on the local display, and turn on SSH.
I am trying to follow the directions at:
https://github.com/moode-player/docs/blo...-end-stuff
As I understand it, Gulp will minify the CSS files (and other files), so any changes need to be run through a build/deploy sequence through Gulp to make this happen.
I am logging into the pi via Putty pi/moodeaudio and performing the following commands:
Code:
~ $ cd ~
Note that "npm ci" gives the following error when running:
Quote: npm WARN deprecated uuid@2.0.3: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
After this is complete (all seems fine, except as noted above), I can navigate to localhost:3000 and I get the output in my browser in the attachment. I'm not sure what I am supposed to see here, but this doesn't look helpful. I can also go to localhost:3001, but that appears to be a bunch of settings that are similarly unhelpful for something like changing CSS.
I am then using Notepad+++ with the SSH pulgin to navigate to home/pi/moode/www/css to locate the files cloned from the repository. If I edit a file like "moode.css" hit save (overwriting the files in the same directory), I can see serial updates in Putty. It looks like Gulp 'saw' the saved change and is rebuilding the mini-fied files.
This is where I am stuck, a restart of the pi doesn't show the new CSS changes. The files at home/pi/moode/www/css still show my changes, but no update on the display (local or via localhost).
I have also tried the directions at 2.1:
Code:
~ $ cd ~
Note that after following the instructions in 2.2, I believe I can start with running "npm ci" and skip the earlier steps. If I do this, the UI on the local screen shows "401 Unauthorized" until I also run:
Code:
~moode $ node\_modules/.bin/gulp build
The pi will then show the UI, but it will not be any of the files I edited at home/pi/moode/www/css.
Attached Files Thumbnail(s)
Posts: 1,394
Threads: 24
Joined: Jun 2022
Reputation:
49
09-15-2022, 10:37 AM
(This post was last modified: 09-15-2022, 10:40 AM by Nutul .)
(09-15-2022, 01:23 AM) jener8tionx Wrote: https://github.com/moode-player/docs/blo...-end-stuff Code:
~ $ cd ~
Quote: npm WARN deprecated uuid@2.0.3: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.Code:
~ $ cd ~
Code:
~moode $ node\_modules/.bin/gulp build
I am not familiar with having the dev-env on the final PI. Moreover I wasn't successful having Gulp to deploy on my remote PI, so I adopted an traditional, manual deploy process:
1. install the development environment on my Linux laptop
2. grab the sources from the GIT repository
3. make my changes locally (almost everywhere)
4. run build and deploy commands
5. manually copy the files on the running PI (I use an automatic script, which you can see below)
6. hit F5 on my browser to see the changes in effect.
Code:
#!/bin/bash
you just need to replace
< you> @<your_machine > with the actuall thing; the source and destination paths are the same on (well, almost) every machine.
Posts: 75
Threads: 3
Joined: Apr 2018
Reputation:
2
try using
Code:
~/moode $ sudo node_modules/.bin/gulp build --force
the dev runs a cache under the build dir for some reason.
Posts: 7
Threads: 1
Joined: Sep 2022
Reputation:
0
09-15-2022, 11:03 PM
(This post was last modified: 09-15-2022, 11:05 PM by jener8tionx .)
Thank you. I tried a few more things, and this is what I determined:
Posts: 579
Threads: 16
Joined: Apr 2020
Reputation:
23
Nice to see you all are trying the development tools
@
jener8tionx :
If you want to use the gulp watch mode local on the pi you need to arrange the following:
make sure the host moode.test is in you host file (and point to 127.0.0.1)
make sure the pi can start a webbrowser on the remote console (ssh session).
For point 2 I use under Window MobaXTerm as ssh client. MobaXTerm has a X server buildin, which will allow the Pi to start a browser and use you X server on Windows 10 for rendering.
@
Nutul :
You indicate you did have problems with the remote deploy.
To be sure you setup the correct remote target in the package.json ?:
Code:
"remote": {
The gulp script is just like your own script using scp for copying the files.
@
grumbleweed :
Yes there is a cache. Use the first time the clean target or --force option to start fresh. Minifying and creating source maps cost time ... a lot of time if you doing multiple development cycles after each other. In that case the cache will save to you time.
And to all:
Keep an eye on which branch/tag your are using for personal development. The head of develop, can break you own system, because it can need a db upgrade or need additional packages.
The savest is to checkout a branch based on the tag of your current running version.
Posts: 7
Threads: 1
Joined: Sep 2022
Reputation:
0
Thank you again. I have an odd issue that I think may be related to to my Gulp usage (but admittedly, I don't know why this would be an issue). Once I run Gulp, I cannot get cover art thumbnails to generate. There are no files in /var/local/www/imagesw/thmcache even though there is cover art for the album.
If I add a library before using Gulp (like a normal person would), then everything works fine and the thumbnails are generated. I have run the log and it looks like "Job regen_thumcache" just hangs.
Screenshots:
Thank you all again for holding my hand through this.
Posts: 13,999
Threads: 318
Joined: Mar 2018
Reputation:
571
Post the console output from the Gulp build.
Posts: 7
Threads: 1
Joined: Sep 2022
Reputation:
0
(09-18-2022, 12:51 AM) Tim Curtis Wrote:
Here you go.
Code:
pi@moode:~ $ cd moode
Posts: 7
Threads: 1
Joined: Sep 2022
Reputation:
0
09-18-2022, 04:13 PM
(This post was last modified: 09-18-2022, 04:48 PM by jener8tionx .)
I was able to recreate the issue on a fresh install (Using 2022-07-08-moode-r812-arm64-lite.img).
After flashing the drive I did the following:
1. Set up wifi, turned on local display, turned on SSH, restart.
2. Connected to NAS via SAMBA and created library. Thumbnails are generating correctly.
3. Regenerated thumbnails. Check with '
moodeutl -l ' and regen_thumcache runs correctly.
4. In SSH completed the following:
Code:
~ $ sudo apt-get update
5. Regenerated thumbnails. Check with '
moodeutl -l ' and regen_thumcache runs correctly.
6. In SSH completed the following:
Code:
~ $ cd moode
7. Regenerated thumbnails. Check with '
moodeutl -l ' and regen_thumcache runs correctly.
8. In SSH completed the following:
Code:
~/moode $ node_modules/.bin/gulp build
For clarity, I did not edit any of the files in /moode/.
9. Regenerated thumbnails. Check with '
moodeutl -l ' and regen_thumcache hangs.
Here is the terminal output showing the last good thumbnail regen, the Gulp build/deploy, and then hanging:
Code:
20220918 115235 thumb-gen: flac: Zend media exception: Not a valid FLAC bitstream
You can see that I ran the regen, waited a bit and then ran it again a minute or so later to show that it failed.
Posts: 13,999
Threads: 318
Joined: Mar 2018
Reputation:
571
I do my Gulp builds on a Mac using the commands below and then from one or more Pi's I mount an SMB share on my Mac and then copy the updated files into the Pi's for testing. I think it's sort of like what @
Nutul does.
Code:
sudo node_modules/.bin/gulp build && sudo node_modules/.bin/gulp deploy --test
Check permissions and timestanmps on the files deployed to /var/www/ they should be 0755 and the timestamps should reflect the time the Gulp build was run.
Try running /var/www/util/thumb-gen.php from the command line and see if there are any errors.
09-15-2022, 01:23 AM
(This post was last modified: 09-18-2022, 04:04 PM by jener8tionx.
Edit Reason: Moode, not Mood
)
