What is the purpose of the Deploy button when you’re on a local Docker target?
I understand the purpose of the Deploy button for a remote Docker target…it pushes the changed files to the remote server/hosting.
But what happens (if anything) when I push the Deploy button on a local Docker target? The latest files are already there because they are on my local machine. So what am I pushing and where am I pushing it to?
Deploy builds your docker based local web server and database server as well and runs them
I understand that when I make some database changes (e.g. schema) I would need to hit the ‘Deploy’ button for the changes to be visible in the Design view.
But when I was making some changes to a database queries for a table, I needed to hit Deploy in order for the changes to be visible in the browser. I’m not sure if I’m doing something wrong where the changes aren’t being reflected properly in the browser, but I’m just a bit uncertain when I need to deploy to local Docker. As I’m getting into a habit now (which I’m sure is unnecessary) of just redeploying to my local Docker target whenever a change doesn’t show in the browser.
Can anyone suggest the list of events/actions that would require a local Docker redeployment?
On local you only hit Deploy when first starting the project to start the app and database server - database changes are automatically applied when you modify through the database manager. File changes are also automatically reloaded
Thanks @Apple. Must be something else I’m not doing for the changes not to propagate.
