Repository administrators can enable serving of static web pages for any existing branch or tag in the repository settings screen. Once enabled, the base URL for pages in this branch or tag is being displayed next to the branch or tag name.
Web pages are available under the following URL:
If there is no index.html file available in the root level of a branch or tag, you need to link to the page directly by appending the file path to the URL. Example:
Of course by hosting your web pages directly in Bitbucket Server, you also get automatic version control by Git.
Access to web pages is based on repository permissions. Users need at least read access to the repository to view web pages in Bitbucket. For security reasons, pages are not available for branches or tags in personal repositories by default. But in the plugin settings, you can configure which groups are allowed to enable pages in personal repositories.
The main difference between Pages for Bitbucket Server and the websites feature of Bitbucket Cloud is that we support websites on a repository level, not just on the account level. This brings the following advantages:
|Websites on Bitbucket Cloud||Pages for Bitbucket Server|
|On Bitbucket Cloud you can only publish one repository per user.||With the Pages add-on you can publish as many repositories as you want.|
|On Bitbucket Cloud you can only publish a single branch of the repository.||With the Pages add-on you can serve static web pages from any branch or tag you like.|
|On Bitbucket Cloud the website is public on the internet. Anyone with the URL can access it.||The Pages add-on uses the permissions of the underlying repository, which allows you to control specifically who can access the pages and who not.|
|Bitbucket Cloud can only serve a website when the site's URL is <username>.bitbucket.org.||The Pages add-on allows you to use your own custom domain.|