09-16-2022, 12:48 PM
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:
@Nutul :
You indicate you did have problems with the remote deploy.
To be sure you setup the correct remote target in the package.json ?:
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.

@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).
@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": {
"host": "yourmoodedevice",
"user": "pi",
"password": "moodeaudio"
},
@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.