Script destroys all non-running containers and volumes in docker #1
Description
Hello Richard/Low-Code Foundation,
Big cheers for the open sourcing of Noodl, the great work being done and the videos being posted on YT by Richard. This new backend is very exciting. I'm am only a hobbyist and have relatively low knowledge in these items, but because of the potential impacts of the current script I think it is best to pass on my experiences.
In regards to running ./setup.sh lines 184 & 185. It prunes all non-running docker containers/volumes/networks. Prior to installation I stopped most of my running containers to best facilitate the multi-container application installation and unfortunately found out the consequences afterwards.
Suggestion is to amend the code (if possible) to only purge certain containers/networks/volumes (i.e named Noodl-better-backend or similar). If the full purge is required, then users should be given fair warning in the README blog about this script and possibly while running through the initial script settings to type a note/confirmation of what running the script will do to all other non-running containers in docker.
Other opennoodl-better-backend installation feedback is:
-Macbook Silicon. Running setup.sh - SUCCESS - Can fully connect from Mac OpenNoodl Desktop and all containers accessible locally.
-QNAP + ContainerStation/Portainer + Git/Docker-compose - FAILURE - Have to manually create "web" network prior to installation. All servers running. Parse-dashboard does not recognise Parse-server. Unable to remotely connect OpenNoodl Desktop into.
-QNAP + Putty + ./setup.sh - FAILURE - "web" network created as part of script build. All servers running. Parse-dashboard does not recognise Parse-server. Unable to remotely connect OpenNoodl Desktop into.
For reference with the previous Noodl-backend. I have installed on QNAP and can access on local network from Mac & Windows OpenNoodl Desktop.
Again, keep up the great work.