| | |
|---|
| | | |
|---|
| | | Your ticket journals are persisted to a Redis data store. *Make sure you configure your Redis instance for durability!!* This particular service is highly-scalable and very fast. Plus you can use all of the power of Redis replication, should you want. |
|---|
| | | |
|---|
| | | The main drawback to this service is that Redis is primarily a Unix tool and works best on a Unix server. While there is a Windows port, sort-of maintained by Microsoft, it is not actively updated. |
|---|
| | | The main drawback to this service is that Redis is primarily a Unix tool and works best on a Unix server. Microsoft is engaged with the Redis community and they do maintain a semi-active port of Redis for Windows servers. |
|---|
| | | |
|---|
| | | tickets.redis.url = redis://(:{password}@){hostname}:{port}(/{databaseId}) |
|---|
| | | |
|---|
| | |
|---|
| | | |
|---|
| | | #### Milestones |
|---|
| | | |
|---|
| | | Milestones are a way to group tickets together. Currently milestones are specified at the repository level and are stored in the repository git config file. Gitblit's internal architecture has all the methods necessary to maintain milestones, but this functionality is not yet exposed through the web ui. For now you will have to control milestones manually with a text editor. |
|---|
| | | Milestones are a way to group tickets together. Milestones are specified for each repository and are stored in the repository git config file. Repository owners may create milestones through the web ui in the *Tickets* page on the *Milestones* tab. |
|---|
| | | |
|---|
| | | [milestone "v1.5.0"] |
|---|
| | | status = Open |
|---|
