I am looking into the access for gitlab pages and I'm confused by the private and public settings:
It is unclear to me about the differences in Everyone. The docs say that even for private repositories everyone can browse? This is basically the same for all of the project types?
I'm looking to setup git pages only visible to those with internal or private access to the repository.
Related
I am trying to connect my data factory resource using my Organization Name in Github, but the private repos inside my oraganization does not show up in the dropdown.
Any one knows how to enable it?
I search for any configuration in github to enable it, but looks like everything is ok.
Is there a way to grant permission in Gitlab so that a person or role only has access to a Wiki? No issues, no source, etc.
Not quite.
See the GitLab permissions docs.
The lowest level you can assign is Guest, which can:
Create issues
Download and browse job artifacts.
View wiki pages
But guest cannot access source code.
I have created a gitlab repo and also have set up SSH keys. I can push my changes to the repo. When another developer wants to contribute to the same repo (project), how can I set up Gitlab so that he can also work with the repository. I would be glad if someone can give me instructions as to how to do that as steps.
He is going to need to setup his own SSH key or you will need to give him one of the private keys if that's the route you want to go...
Otherwise, you could just invite him to edit the repo (assuming he has an account). To navigate to those settings go to your desired project repository in your web browser, and find the "Settings" menu on the left side. Inside there, you will see "Members". There you can enter the developer's credentials to allow him access to the repo.
My company want to get VSTS. But they do not want users to be able to access their personal VSTS accounts at work. They are concerned that users will upload source code to their personal VSTS accounts and download it at home. Or worse, they are worried that users can upload a virus to their personal VSTS account, come into work and download it. I'm sure everyone will understand why they want to do this.
Without getting into ethical reasons about how companies need to trust employees etc......They want to stop this or reduce this as much as possible.
Is there any guidance on how to achieve this?
One solution is to maybe block *.visualstuido.com but whitelist only our company VSTS account? This is messy because there will be a bunch of other visualstudio.com urls that we will need to access such as {accountname}.vsrm.visualstudio.com.
There is no way for us to know all the urls that we will need to allow access if we block *.visualstudio.com
any advice is appreciated!
I don’t think you can achieve it. There are many ways that can store/download the source code except VSTS, such as github. Users also can upload/download the source code through email. So you can’t prevent them to do it unless block to access internet.
The simple way is that:
Build an intranet network
Clone VSTS repository to a shared folder
Others work with that repository (commit changes to that repository)
Push changes to VSTS by yourself or build the app to track repository and push commits automatically.
I am trying to give a designer access to specific folders within an Azure website I have. I would like for the designer to have access via FTP. However, according to this post, having multiple FTP user accounts on the same Azure website is not possible and the accepted answer suggests coming up with a "different way to manage" the website. This means that if you want collaboration on an Azure website, you have to share the entire directory structure. Please correct me if I am wrong.
I know you can download the Publish Profile settings from Azure as seen on this post. This does not solve the issue as the publish profile simple gives you the FTP credentials for a specific website (instead of all of your Azure websites) but still does not provide the option to create new FTP users with limited directory permissions.
So, my question is: is there some way to edit the Publish Profile settings when they are downloaded so folder access is limited? If not, what methods have you used for website development collaboration on Azure where certain folders should be hidden and protected?
For collaborative work with Azure Websites, you can enable source control. This includes tfs, git, dropbox, bitbucket, and codeplex. Dropbox is not the best collaborative tool, as it's not designed to be a version control system, but it's very convenient.
If you have a repository with any of the abovementioned providers, you can now give your designer their own account with the version control system.
You guys are right about using a source control system like GitHub instead of trying to provide access by creating a second FTP user.
Others have asked this question - not in the context of azure though.
This post talks about using submodules on github to give a contractor access to a subfolder and all folders / files under that sub folder.
SO - I believe linking azure to github would be necessary and then from there, creating and managing submodules from github would allow for collaboration. I believe a required aspect of this would be to have a private repo on github for the main repo. All of the files in the repo would otherwise be available for forking which would defeat the entire purpose of maintaining some discretion on access rights in the first place.