Home • Explore • Blog • CI
☰



docker
7th chunk of `content/get-started/workshop/06_bind_mounts.md`
e485bf23c3fb3275146b596c84c3ceb5371bcc71babf7115000000010000054f


3. Feel free to make any other changes you'd like to make. Each time you make a
   change and save a file, the change is reflected in the container because of
   the bind mount. When Nodemon detects a change, it restarts the app inside the
   container automatically. When you're done, stop the container and build your
   new image using:

   ```console
   $ docker build -t getting-started .
   ```

## Summary

At this point, you can persist your database and see changes in your app as you develop without rebuilding the image.

In addition to volume mounts and bind mounts, Docker also supports other mount
types and storage drivers for handling more complex and specialized use cases.

Related information:

 - [docker CLI reference](/reference/cli/docker/)
 - [Manage data in Docker](https://docs.docker.com/storage/)

## Next steps

In order to prepare your app for production, you need to migrate your database
from working in SQLite to something that can scale a little better. For
simplicity, you'll keep using a relational database and switch your application
to use MySQL. But, how should you run MySQL? How do you allow the containers to
talk to each other? You'll learn about that in the next section.

{{< button text="Multi container apps" url="07_multi_container.md" >}}
Title: Making Changes and Preparing the App for Production
Summary
This section discusses the hot-reloading functionality, which allows changes made in the development environment to be automatically reflected in the container without rebuilding the image. It mentions the use of `docker build` to create a new image after development and briefly introduces Docker's data management options. The section concludes by outlining the next steps: migrating the database from SQLite to MySQL and running MySQL in a multi-container setup, where containers need to communicate with each other.