Currently when you for instance remove the login.html from the theme Mendix still deploys this file. The same goes for some other files from the theme. As a site admin I do not want these files to be deployed because it means the user can then for instance access login.html and it will render the default Mendix login.html. I now redirect that to index.html but it would be better if those files were not deployed if I do not need / want them.
this idea relates to this forum post:
“when you for instance remove the login.html from the theme Mendix still deploys this file” I’m not sure that this is true.
What often happens (a lot in css), is that you for instance will upload bg1.png to your project and deploy it (locally).
than lets say you add bg2.png, and delete bg1.png.
Deploy again, and bg2.png will be in your local deployment.
because bg1 is not overwritten, it can still be accessed.
Deploying doesn’t seem to remove previously uploaded files (at least locally, and in the theme folder) It might be something taking a look at :D.
But I’d def ask someone more into the security side of MX ;)