I have been unable to update my production docker since the latest patch, I believe the docker method was changed, could someone point me in the right direction to migrate methods?
This is completely over my head, I let wappler manage all my docker magic and I'm definitely out of my depth here, when i deploy to prod I just sit here at the npm install indefinitely until I manually restart the server on the digital ocean side.
I believe this to be some sort of temporary network issue rather than a change in Wappler
I was pushing changes literally minutes before the 6.7 update to my prod and directly after updating it has been doing this, nothing else changed except minor html edits
You could try updating and cleaning your Node packages before deploying?
If you are running an outdated local version of Docker it is worth updating, but if everything was fine before the update it probably is not necessary as the changes were made a few versions back, and as you could deploy it suggests you're probably all good in that regard. Failing that just walk away for a while and let it do its thing. There are no errors so maybe let it run its course?
its the latest docker, it wont actually push my latest changes anymore, it just sits forever and maxes my server cpu now at that step indefinitely.
Have you pruned your remote target? Maybe worth doing this as space could be an issue and you're not seeing an error? Just throwing that one out there though...
Open Remote SSH console:
docker system prune
I will give it a go thanks
You could also try editing your Remote Target (set Node Type to Slim if not already), let Wappler do its thing. Try to Deploy. If no success then make a change to the Remote Target (change Node version to 20 (or to 22, LTS, anything but your current version as we just want a change), let Wappler do its thing, then try Deploy?
yea its already on slim and version 22, I will try going back a version and then back to the 22 version as well
lifesaver my friend, going back to 18 and then back to 22 made it push, really appreciate the help
No problem @TheBotfather more often than not a little switch about in the Remote Target tends to resolve issues when no errors are being displayed. Worth keeping on top of pruning too. Can save a hell of a lot of space and improve efficiency so always good practice to tidy up after any new deployments.
Very happy you have it all working. Onwards and upwards.
