Securing Git operations between the user's computer and Bitbucket is a separate consideration - see Enabling SSH access to Git.Īccess to Bitbucket can be secured by enabling HTTPS (HTTP over SSL) for the Tomcat application server that is bundled with Bitbucket.You can set the context path for Bitbucket if you are running another Atlassian application, or Java web application, at the same hostname and context path as Bitbucket.
The address with which to access Bitbucket, by default, will be Change the base URL if required.Bitbucket, by default, will listen for requests on port 7990 – this port can be changed if required.You may also wish to consider the following: When set up this way, the user accesses Bitbucket directly over HTTP, without using SSL – all communication between the user's browser and Bitbucket will be unsecured.
Git config ssh proxy install#
Automatically decline inactive pull requestsĬonnecting to Bitbucket directly over HTTPĬonnecting directly to Bitbucket (that is, Tomcat) is the default install configuration, as described on Getting started.Setting a system-wide default branch name.Use a CDN with Atlassian Data Center applications.Improving instance stability with rate limiting.Configuring Project links across Applications.Adding additional storage for your repository data.Enabling JMX counters for performance monitoring.Export and import projects and repositories.Disable HTTP(S) access to Git repositories.Migrate Bitbucket Server from Windows to Linux.Migrating Bitbucket Server to another server.Connect Bitbucket to an external database.
Administer Bitbucket Data Center and Server
0 kommentar(er)
