nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Stash as dedicated user

Kota Sreenivasa Shravana Kumar

In our Linux production environment, Stash is running as user root. However, Atlassian recommends that, for production or enterprise environment, stash should be run from a dedicated user account stash.

Just wanted to check with the Atlassian experts, if the following procedure is correct to implement the above recommended method. Let me know, if there are any issues. if there is any Atlassian link where this exact procedure including commands described would also be useful.

1. Stop Stash

2. create stash user as follows

useradd stash

3. chown -R stash:stash <stash installation directory>

4. chown -R stash:stash <stash home directory>

5. Start Stash

Thanks

Accepted answers

Michael Heemskerk

As long as in step 5 you actually start Stash as the stash user, that should work.

All comments

Michael Heemskerk

As long as in step 5 you actually start Stash as the stash user, that should work.

Kota Sreenivasa Shravana Kumar

Thanks for the quick response. Agreed that step 5 should run as stash user. Another question. After implementing the above said procedure, we got to validate the same to make sure that three is no impact to the users. What kind of testing do you suggest ? something like git clone or git push or anything else ? Please advise.

Michael Heemskerk

I'd try to:

clone an existing repository
push to an existing repository
create a new repository in Stash
clone the repository, make some changes and push the commits back
clone the repository again
delete the repository

That would test read, write and directory creation permissions.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket-server

bitbucket-administration