Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,416
Community Members
 
Community Events
177
Community Groups

seting up an artifacotry for bitbucket correctly

Hello All

 I have two questions regarding setting up Artifactory as git lfs server for bitbucket (server)

1)

In this article from the community it say to put this section

[lfs]
url = "https://<USERNAME>:<PASSWORD>@<DOMAIN>.jfrog.io/artifactory/api/lfs/<REPO-NAME>"

in the .lfsconfig

 

This is not good cause the user name and password are expose.

So I searched and found this article that say not to push the .lfsconfig to bitbucket.

Moreover it say "Alternatively, you can configure the .lfsconfig without credentials and make it part of the Git repository.
Then, upon pushing or pulling, users will be prompted for credentials "

  1. How do I config the lfsconfig without credentials ? simply put url without user and password ?
  2. Will the users need to put their credentials every time they push ?

2)

Is it good idea to have lfs-local repo for each of my project/repositories in bitbucket ?

Or just have one lfs-local repo for all of the repositories in bitbucket ?

(cause the content is not human readable. It is sha1)

 

Thanks

  omatza

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS

Atlassian Community Events