|
1 | | -# Redmine Git Hosting Plugin (v0.4.5x) |
| 1 | +# Redmine Git Hosting Plugin (v0.4.6x) |
2 | 2 |
|
3 | 3 | A ChiliProject / Redmine plugin which makes configuring your own git hosting easy. This plugin allows straightforward management |
4 | 4 | of gitolite and associated public keys, the git daemon, and integrates code from Scott Schacon's "grack" utility |
@@ -354,6 +354,43 @@ This command will install the new values in the database. You should follow up |
354 | 354 | parameter(s)). If you are moving the location of the *gitScriptDir*, you might want to remove the old scripts before executing 'restore_defaults' |
355 | 355 | as described above. |
356 | 356 |
|
| 357 | +## Deployment Credentials |
| 358 | + |
| 359 | +As of version 0.4.6x, this plugin provides deployment credentials on a per-repository basis. These credentials are combinations of a public key and access |
| 360 | +permissions (R or RW+) which are attached directly to a repository rather than by attaching users to repositories. Deployment credentials may be |
| 361 | +added to a repository through the repository settings interface. They may be added by anyone who is a manager for the project or by the administrator. |
| 362 | + |
| 363 | +Public keys used in this way are called "deploy keys". They are owned by the user who created them and may be edited on the user's public_key page (which is under |
| 364 | +"my account" for individual users). Since keys have unique names (per creator), they may be reused in multiple deployment credentials (in multiple repositories), |
| 365 | +simply by selecting them from the pulldown menu on the "deployment credentials create" dialog box. |
| 366 | + |
| 367 | +One typical use-case would be for all deploy keys to be owned by the administrator and attached selectively to various repositories. Note that the "deployment |
| 368 | +credentials create" dialog is actually a convenience dialog in that it allows the simultaneous creation of both a deploy key and deployment credential in a single step, |
| 369 | +even suggesting a name for the deployment credential, with the eye to deployments that have a separate deploy key for each repository. Reusing a deploy key in |
| 370 | +another credential is a simple matter of selecting the key from a drop-down menu. |
| 371 | + |
| 372 | +## Post-Receive URLs |
| 373 | + |
| 374 | +As of version 0.4.6x, this plugin supports the inclusion of GitHub-style Post-Receive URLs. Once added, a post-receive URL will be notified when new changes |
| 375 | +are pushed to the repository. Two versions of this functionality are available: (1) either a GitHub-style POST operation will include json-encoded information |
| 376 | +about the updated branch or (2) an empty GET request will be issued to the given URL. Post-Receive URLs may be added from the repository settings page. |
| 377 | + |
| 378 | +## Automatic Mirror Updates |
| 379 | + |
| 380 | +As of version 0.4.0, this plugin can automatically push updates to repository mirrors when new changes are pushed to the repository. Mirrors |
| 381 | +must grant access to the public key defined in the gitolite_admin_id_rsa.pub public key file, which is displayed for convenience in the |
| 382 | +repository settings tab. |
| 383 | + |
| 384 | +Note that 0.4.6x introduced the ability to selectively push branches to the mirror (using the git-push refspec mechanism) rather than mirroring all branches and tags. |
| 385 | +To utilize this feature, simply select a mirror update mode of "Force Update Remote" or "Fast Forward (unforced)" instead of the default "Complete Mirroring" in the |
| 386 | +mirror create/edit dialog. More options will then become available. |
| 387 | + |
| 388 | + |
| 389 | +## Notification to CIA.vc |
| 390 | + |
| 391 | +As of version 0.4.0, this plugin can notify CIA.vc when changes are pushed to the repository. The project identifier on CIA.vc must match the |
| 392 | +project identifier specified in ChiliProject/Redmine exactly |
| 393 | + |
357 | 394 |
|
358 | 395 | ## "Smart" HTTP Functionality |
359 | 396 |
|
@@ -429,19 +466,6 @@ max_allowed_packet=32M |
429 | 466 |
|
430 | 467 | The above example should allow **Max Cache Element Size** == 32M. |
431 | 468 |
|
432 | | -## Notification to CIA.vc |
433 | | - |
434 | | -As of version 0.4.0, this plugin can notify CIA.vc when changes are pushed to the repository. The project identifier on CIA.vc must match the |
435 | | -project identifier specified in ChiliProject/Redmine exactly |
436 | | - |
437 | | - |
438 | | -## Automatic Mirror Updates |
439 | | - |
440 | | -As of version 0.4.0, this plugin can automatically push updates to repository mirrors when new changes are pushed to the repository. Mirrors |
441 | | -must grant access to the public key defined in the gitolite_admin_id_rsa.pub public key file, which is displayed for convenience in the |
442 | | -repository settings tab. |
443 | | - |
444 | | - |
445 | 469 | ## Fast Deployment with YourChili Bash Library |
446 | 470 |
|
447 | 471 | Instead of installing/configuring by hand, one option for quickly deploying a fully-functional system for hosting |
|
0 commit comments