You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Script para alterar o schema e collation do banco de dados de Latin1 para UTF-8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
IOTstack is a framework for running arbitrary collections of Docker containers using docker compose. The canonical example is the "MING" stack (Mosquitto, InfluxDB, Node-RED and Grafana).
From time to time, someone asks a question like this:
I have read that Docker's "volume mounts" are recommended and/or better than "bind mounts". Why does IOTstack use "bind mounts"?
Unless you understand the differences between Docker's mount types, it's difficult to see why you would want choose one type over the other. This gist attempts to explain the differences between Docker bind and volume mounts, and then answers the question of why IOTstack uses Docker bind mounts exclusively.