Cloud
Data Center 4.7
Versions
- 9.5
- 9.4
- 9.3
- 9.2
- 9.1
- 9.0
- 8.19
- 8.18
- 8.17
- 8.16
- 8.15
- 8.14
- 8.13
- 8.12
- 8.11
- 8.10
- 8.9
- 8.8
- 8.7
- 8.6
- 8.5
- 8.4
- 8.3
- 8.2
- 8.1
- 8.0
- 7.21
- 7.20
- 7.18
- 7.19
- 7.17
- 7.16
- 7.15
- 7.14
- 7.13
- 7.12
- 7.11
- 7.10
- 7.9
- 7.8
- 7.7
- 7.6
- 7.5
- 7.4
- 7.3
- 7.2
- 7.1
- 7.0
- 6.10
- 6.9
- 6.8
- 6.7
- 6.6
- 6.5
- 6.4
- 6.3
- 6.2
- 6.1
- 6.0
- 5.16
- 5.15
- 5.14
- 5.13
- 5.12
- 5.11
- 5.10
- 5.9
- 5.8
- 5.7
- 5.6
- 5.5
- 5.4
- 5.3
- 5.2
- 5.1
- 5.0
- 4.14
- 4.13
- 4.12
- 4.11
- 4.10
- 4.9
- 4.8
- 4.7
- See all
Running Bitbucket Server with a dedicated user
Advanced actions
- Running the Bitbucket Server installer
- Automated setup for Bitbucket Server
- Starting and stopping Bitbucket Server
- Install Bitbucket Server from an archive file
- Install and configure a remote Elasticsearch instance
- Running Bitbucket Server as a Linux service
- Running Bitbucket Server as a Windows service
- Bitbucket Server config properties
- Proxying and securing Bitbucket Server
- Enabling SSH access to Git repositories in Bitbucket Server
- Using diff transcoding in Bitbucket Server
- Changing the port that Bitbucket Server listens on
- Moving Bitbucket Server to a different context path
- Running Bitbucket Server with a dedicated user
- Bitbucket Server debug logging
- Data recovery and backups
- Lockout recovery process
- Scaling Bitbucket Server
- High availability for Bitbucket Server
- Clustering with Bitbucket Data Center
- Enabling JMX counters for performance monitoring
- Getting started with Bitbucket Server and AWS
- Disabling HTTP(S) access to Git repositories in Bitbucket Server
- Smart Mirroring
- Git Large File Storage
On this page
Related content
- Clone a repository
- Clone your repository and manage files locally
- Getting started with Git and Bitbucket Server
- Install Bitbucket Server from an archive file
- Importing code from an existing project
- Creating projects
- SSH user keys for personal use
- Enabling SSH access to Git repositories in Bitbucket Server
- SSH access keys for system use
- Creating SSH keys
For production installations, we recommend that you create a new dedicated user that will run Bitbucket Server on your system. This user:
- Should be local.
- Should not have admin privileges.
- Should be a non-privileged user with read, write and execute access (called "Full control" permission on Windows) on the Bitbucket Server install directory and home directory.
Note that, on Windows, running Bitbucket Server (whether as a service, or not) as a user that is part of the Administrator group can cause Windows to spend a lot of time running permission checks, with a consequent performance impairment for Git operations.
See also Running Bitbucket Server as a Windows service and Running Bitbucket Server as a Linux service.
For Linux, here is an example of how to create a dedicated user to run Bitbucket Server:
$ sudo /usr/sbin/useradd --create-home --home-dir /opt/atlassian/bitbucket --shell /bin/bash atlbitbucket
Last modified on Sep 16, 2015
Related content
- Clone a repository
- Clone your repository and manage files locally
- Getting started with Git and Bitbucket Server
- Install Bitbucket Server from an archive file
- Importing code from an existing project
- Creating projects
- SSH user keys for personal use
- Enabling SSH access to Git repositories in Bitbucket Server
- SSH access keys for system use
- Creating SSH keys
Powered by Confluence and Scroll Viewport.