The documentation here is great:
However, I have a need that isn't covered here. I have some flat html files that are produced from a build process. I'd prefer to have the repo that builds it also be the repo that is used for the bitbucket.io "site". That would be possible, if the bitbucket.io web-root were configurable to be in a "web" (or other named) folder, rather than being required to be the repository root.
I don't want to expose all the processing files to the website. I only want the bitbucket.io "site" to have the flat HTML available to web users.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot