Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Gitolite Essentials
  • Table Of Contents Toc
Gitolite Essentials

Gitolite Essentials

By : Sitaram Chamarty
4 (2)
Buy this Book
close
close
Gitolite Essentials

Gitolite Essentials

4 (2)
By: Sitaram Chamarty
Buy this Book

Overview of this book

Table of Contents (19 chapters)
close
close
close
Gitolite Essentials
Icon
Gitolite Essentials
Credits
Icon
Credits
About the Author
Icon
About the Author
Acknowledgments
Icon
Acknowledgments
About the Reviewers
Icon
About the Reviewers
www.PacktPub.com
Icon
www.PacktPub.com
Preface
Icon
Preface
Lock Free Chapter
1
Getting Started with Gitolite
Icon
Getting Started with Gitolite
Icon
Common Access Control needs
Icon
Access Control example with Gitolite
Icon
Sampling of Gitolite's power features
Icon
Gitolite and the Git control flow
Icon
Trying out Gitolite
Icon
Summary
2
Installing Gitolite
Icon
Installing Gitolite
Icon
Gitolite users and the hosting user
Icon
Preparing the server
Icon
Getting the Gitolite source
Icon
Installing the code
Icon
Setting up Gitolite
Icon
Summary
3
Your Users and Gitolite
Icon
Your Users and Gitolite
Icon
Accessing Git repositories
Icon
Accessing Gitolite repositories
Icon
Getting information from Gitolite
Icon
Gitolite commands
Icon
Getting help for commands
Icon
Troubleshooting SSH issues
Icon
Summary
4
Adding and Removing Users
chevron up
Icon
Adding and Removing Users
Icon
Adding users
Icon
Users with multiple key pairs
Icon
Giving some users a shell
Icon
Managing keys outside Gitolite
Icon
Getting user group information from LDAP
Icon
Removing users
Icon
Summary
5
Managing Repositories
Icon
Managing Repositories
Icon
Adding repositories
Icon
Adding existing repositories
Icon
Common problems and troubleshooting
Icon
Summary
6
Getting Started with Access Control
Icon
Getting Started with Access Control
Icon
Basic access control examples
Icon
Lexical syntax of the conf file
Icon
The syntax of access control rules
Icon
Branch level access control and refexes
Icon
Defining user and repo groups
Icon
The include statement
Icon
Rule accumulation and delegation
Icon
Summary
7
Advanced Access Control and Configuration
Icon
Advanced Access Control and Configuration
Icon
Making changes to the rc file
Icon
Giving users their own branches
Icon
Types of write operations
Icon
Allowing Gitweb and Git-daemon access
Icon
Specifying Git config values and Gitolite options
Icon
Applying deny rules to read access
Icon
Understanding VREFs
Icon
Summary
8
Allowing Users to Create Repos
Icon
Allowing Users to Create Repos
Icon
Putting repositories in Sub-directories
Icon
Repository wildcards
Icon
Explaining wild repos to your users
Icon
Managing with just wild repos
Icon
Deleting wild repositories
Icon
Summary
9
Customizing Gitolite
Icon
Customizing Gitolite
Icon
Core and non-core Gitolite
Icon
Types of non-core code and examples
Icon
Writing your own non-core code
Icon
Summary
10
Understanding VREFs
Icon
Understanding VREFs
Icon
Migrating update hooks
Icon
Passing arguments to the VREF code
Icon
Using the permission field
Icon
Default is success
Icon
Example VREFs and their usage
Icon
Writing your own VREF
Icon
Summary
11
Mirroring
Icon
Mirroring
Icon
Terminology and basic concepts
Icon
Setting up mirroring
Icon
Local repositories and hostname substitution
Icon
Redirecting pushes
Icon
Manual synchronization
Icon
Switching to a different master
Icon
Summary
1
Index
Icon
Index

Giving some users a shell

Some of your users may have a legitimate need to log on to the server as the hosting user and use a shell command line. If this is required for just one or two users, the simplest way to deal with this is to have them use two different keys—one for Gitolite access and one for shell access. The second key would be installed manually in the authorized keys file on the server, and would not have the command and other options that Gitolite keys have.

Tip

Non-Gitolite keys must be added right at the start of the authorized keys file, or at least before the marker line that says # gitolite start. Keys added in between Gitolite's start and end marker lines will be deleted the next time the gitolite-admin repository is pushed.

However, this requires careful handling of the second key on both the server side, as well as the client side. Some users may not be interested in learning how to handle multiple keys on their side, and how to present the correct key for each access...

CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Gitolite Essentials
End of Section 4
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon