Deploy (build.publish) setting being ignored
See original GitHub issueUsing this example, there is a setup for build.publish
with a value of public
. There is no build really just a nice simple index.hml
file in the public path. Using a netlify.yml
file for the config, but a netlify.toml
had the same issue.
See this Deploy log and the image below. The deploy is from the root.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
asp.net - Build succeeds, but publish fails - Stack Overflow
However, when publishing the folder was ignored. It turns out I had to create the empty folder 1st and then copy in the...
Read more >Visual Studio publish profiles (.pubxml) for ASP.NET Core app ...
Learn how to create publish profiles in Visual Studio and use them for managing ASP.NET Core app deployments to various targets.
Read more >Locked Files When Publishing .NET Core Apps to IIS with ...
By default WebDeploy doesn't place an app_offline.htm file into the folder while publishing which is really bad form. Publish Profile Setting: ...
Read more >Build configuration overview - Netlify Docs
Reference basic build settings for a repository using continuous deployment, and understand build image options for your site.
Read more >Compose file version 3 reference - Docker Documentation
The build option is ignored when deploying a stack in swarm mode The docker stack command does not build images before deploying.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@kripod @talves I just looked into it and you’re correct. I think I’ve identified the issue. I will post once we have more information.
@kripod @talves This should be fixed now.
I have tested against
talves/netlify-plugin-debug
and it correctly deploys. Thanks for your patience and please let me know if there is anything else that is still broken.