> For the complete documentation index, see [llms.txt](https://docs.dappling.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dappling.network/builds/build-logs.md). # Build Logs When you deploy your website to dAppling, the platform generates build logs that display the deployment progress. These build logs contain information about: * The version of the build tools used. * Warnings or errors encountered during the build process. * Details about the files and dependencies that were installed, compiled, or built during the deployment. Build logs are an invaluable resource for debugging issues that may arise during deployment. If a deployment encounters problems, these logs can assist you in pinpointing the root cause. To access the build logs, simply navigate to a deployment and scrroll down to the build logs section. ## How build logs work? Build logs are generated during the build process for all deployments. These logs closely resemble the output of your framework's Build Command, with some minor additions from the dAppling build system. It's important to note that once a build is complete, no new logs will be recorded. In addition to the list of build actions, you can identify errors or warnings in the logs. These are highlighted with different colors, such as yellow for warnings and red for errors. This color coding provides flexibility in investigating why your build may have failed and which part of your website is affected. It's worth mentioning that build logs are stored indefinitely for each deployment, ensuring you have access to historical information as needed for debugging and analysis. :cactus:*Fun Fact: Rhubarb leaves are poisonous due to high levels of oxalic acid, even though the stalks are edible.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dappling.network/builds/build-logs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.