chore(onedev): fix config
This commit is contained in:
Nicolas Meienberger
parent
2b21a95f85
commit
3932ffa1df
|
|
@ -17,31 +17,31 @@
|
||||||
"type": "random",
|
"type": "random",
|
||||||
"label": "DB_PASSWORD",
|
"label": "DB_PASSWORD",
|
||||||
"min": 32,
|
"min": 32,
|
||||||
"env_variable": "DB_PASSWORD"
|
"env_variable": "ONEDEV_DB_PASSWORD"
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"type": "text",
|
"type": "text",
|
||||||
"label": "Onedev Inital Username",
|
"label": "Onedev username",
|
||||||
"max": 50,
|
"max": 50,
|
||||||
"min": 3,
|
"min": 3,
|
||||||
"required": true,
|
"required": true,
|
||||||
"env_variable": "initial_user"
|
"env_variable": "ONEDEV_USERNAME"
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"type": "text",
|
"type": "email",
|
||||||
"label": "Onedev Inital Email",
|
"label": "Onedev email",
|
||||||
"max": 50,
|
"max": 50,
|
||||||
"min": 3,
|
"min": 3,
|
||||||
"required": true,
|
"required": true,
|
||||||
"env_variable": "initial_email"
|
"env_variable": "ONEDEV_EMAIL"
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"type": "password",
|
"type": "password",
|
||||||
"label": "Onedev Inital Password",
|
"label": "Onedev password",
|
||||||
"max": 50,
|
"max": 50,
|
||||||
"min": 3,
|
"min": 8,
|
||||||
"required": true,
|
"required": true,
|
||||||
"env_variable": "initial_password"
|
"env_variable": "ONEDEV_PASSWORD"
|
||||||
}
|
}
|
||||||
]
|
]
|
||||||
}
|
}
|
||||||
|
|
|
||||||
|
|
@ -1,4 +1,4 @@
|
||||||
version: "3.7"
|
version: '3.7'
|
||||||
|
|
||||||
services:
|
services:
|
||||||
onedev:
|
onedev:
|
||||||
|
|
@ -9,10 +9,10 @@ services:
|
||||||
- hibernate_connection_driver_class=org.postgresql.Driver
|
- hibernate_connection_driver_class=org.postgresql.Driver
|
||||||
- hibernate_connection_url=jdbc:postgresql://onedev-db:5432/onedev
|
- hibernate_connection_url=jdbc:postgresql://onedev-db:5432/onedev
|
||||||
- hibernate_connection_username=tipi
|
- hibernate_connection_username=tipi
|
||||||
- hibernate_connection_password=${DB_PASSWORD}
|
- hibernate_connection_password=${ONEDEV_DB_PASSWORD}
|
||||||
- initial_user=${initial_user}
|
- initial_user=${ONEDEV_USERNAME}
|
||||||
- initial_password=${initial_password}
|
- initial_password=${ONEDEV_PASSWORD}
|
||||||
- initial_email=${initial_email}
|
- initial_email=${ONEDEV_EMAIL}
|
||||||
- initial_server_url=${APP_DOMAIN}
|
- initial_server_url=${APP_DOMAIN}
|
||||||
restart: unless-stopped
|
restart: unless-stopped
|
||||||
volumes:
|
volumes:
|
||||||
|
|
@ -20,7 +20,7 @@ services:
|
||||||
- /var/run/docker.sock:/var/run/docker.sock
|
- /var/run/docker.sock:/var/run/docker.sock
|
||||||
ports:
|
ports:
|
||||||
- ${APP_PORT}:6610
|
- ${APP_PORT}:6610
|
||||||
- "6611:6611"
|
- '6611:6611'
|
||||||
depends_on:
|
depends_on:
|
||||||
- onedev-db
|
- onedev-db
|
||||||
networks:
|
networks:
|
||||||
|
|
@ -39,7 +39,7 @@ services:
|
||||||
restart: unless-stopped
|
restart: unless-stopped
|
||||||
environment:
|
environment:
|
||||||
- POSTGRES_USER=tipi
|
- POSTGRES_USER=tipi
|
||||||
- POSTGRES_PASSWORD=${DB_PASSWORD}
|
- POSTGRES_PASSWORD=${ONEDEV_DB_PASSWORD}
|
||||||
- POSTGRES_DB=onedev
|
- POSTGRES_DB=onedev
|
||||||
volumes:
|
volumes:
|
||||||
- ${APP_DATA_DIR}/data/postgres:/var/lib/postgresql/data
|
- ${APP_DATA_DIR}/data/postgres:/var/lib/postgresql/data
|
||||||
|
|
|
||||||
|
|
@ -6,21 +6,21 @@ It works by analyzing source code with ANTLR, extracting symbols for storage inc
|
||||||
|
|
||||||
You can also jump to symbol definition in diff while reviewing commits or pull requests.
|
You can also jump to symbol definition in diff while reviewing commits or pull requests.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Code Search with Regular Expression
|
## Code Search with Regular Expression
|
||||||
|
|
||||||
You may switch to any commit, and search code with regular expression. OneDev under the hood indexes the code with Lucene incrementally. At search time, literal tri-grams in the regular expression are extracted for a coarse search, followed by exact match in the result. This makes the regex search blazing fast, even for large repositories like Linux.
|
You may switch to any commit, and search code with regular expression. OneDev under the hood indexes the code with Lucene incrementally. At search time, literal tri-grams in the regular expression are extracted for a coarse search, followed by exact match in the result. This makes the regex search blazing fast, even for large repositories like Linux.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Annotate Source/Diff with Static Analysis Result to Facilitate Code Review
|
## Annotate Source/Diff with Static Analysis Result to Facilitate Code Review
|
||||||
|
|
||||||
Of course this can be done by many third party applications at GitHub, however they display the result on their own applications, and this makes review activities such as adding comment over analysis result difficult. Not to mention that you need to pay for these services.
|
Of course this can be done by many third party applications at GitHub, however they display the result on their own applications, and this makes review activities such as adding comment over analysis result difficult. Not to mention that you need to pay for these services.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Customizable Issue State and Field, with Deep CI/CD Integration
|
## Customizable Issue State and Field, with Deep CI/CD Integration
|
||||||
|
|
||||||
|
|
@ -35,15 +35,15 @@ With customizable issue states, we may address the issue with four states: open,
|
||||||
2. When a test build is created and deployed, the issue transits to test ready state automatically. QA will be notified and can check issue detail to know which environment the test build is deployed into.
|
2. When a test build is created and deployed, the issue transits to test ready state automatically. QA will be notified and can check issue detail to know which environment the test build is deployed into.
|
||||||
3. When test passes, and a release build is created, customers submitting the issue will be notified and they can check issue detail to see which release contains the fix.
|
3. When test passes, and a release build is created, customers submitting the issue will be notified and they can check issue detail to see which release contains the fix.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Service Desk to Create/Discuss Issues via Email
|
## Service Desk to Create/Discuss Issues via Email
|
||||||
|
|
||||||
Service desk allows your users to submit tickets via email without the need to have a OneDev account. These tickets can then be created in desired projects, and assigned to appropriate members in your team. All further discussions over the tickets can take place completely in email, with discussion contents posted to ticket as comments. User will also get notifications when there are any ticket activities, for instance, when a relevant release is created or deployed
|
Service desk allows your users to submit tickets via email without the need to have a OneDev account. These tickets can then be created in desired projects, and assigned to appropriate members in your team. All further discussions over the tickets can take place completely in email, with discussion contents posted to ticket as comments. User will also get notifications when there are any ticket activities, for instance, when a relevant release is created or deployed
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## A powerful and Intuitive Query Language
|
## A powerful and Intuitive Query Language
|
||||||
|
|
||||||
|
|
@ -51,7 +51,7 @@ Thanks to ANTLR again, OneDev ships sophisticated query languages for projects,
|
||||||
|
|
||||||
Queries can be saved and subscribed, so that you won't miss anything interested.
|
Queries can be saved and subscribed, so that you won't miss anything interested.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## A Full-fledge CI/CD Engine without Writing Yaml
|
## A Full-fledge CI/CD Engine without Writing Yaml
|
||||||
|
|
||||||
|
|
@ -59,17 +59,17 @@ OneDev ships with GUI to generate CI/CD Yaml. No need to google around for Yaml
|
||||||
|
|
||||||
Build pipeline, matrix jobs, typed parameters, parameter chaining, step templates, build promotions… too many neat features to elaborate…
|
Build pipeline, matrix jobs, typed parameters, parameter chaining, step templates, build promotions… too many neat features to elaborate…
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Flexible Pull Request Review Policy and Reviewer Suggestion
|
## Flexible Pull Request Review Policy and Reviewer Suggestion
|
||||||
|
|
||||||
Specify pull request review policy based on author, branch, and changed files. OneDev can leverage git change history to suggest most appropriate reviewers for pull requests touching certain files.
|
Specify pull request review policy based on author, branch, and changed files. OneDev can leverage git change history to suggest most appropriate reviewers for pull requests touching certain files.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Lightweight Review without Pull Request
|
## Lightweight Review without Pull Request
|
||||||
|
|
||||||
|
|
@ -77,15 +77,15 @@ Comment on any part of code or diff to start a lightweight review without openin
|
||||||
|
|
||||||
Each discussion is threaded so that you can easily know discussions with new comments/updates.
|
Each discussion is threaded so that you can easily know discussions with new comments/updates.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Command Palette to Access Features Quickly
|
## Command Palette to Access Features Quickly
|
||||||
|
|
||||||
Press cmd/ctrl-k to bring up command palette from anywhere. Search projects, files, issues, pull requests, builds, and various settings and jump to them without leaving your keyboard
|
Press cmd/ctrl-k to bring up command palette from anywhere. Search projects, files, issues, pull requests, builds, and various settings and jump to them without leaving your keyboard
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Write Markdown Pleasantly With a Smart Editor
|
## Write Markdown Pleasantly With a Smart Editor
|
||||||
|
|
||||||
|
|
@ -93,13 +93,13 @@ When embedding an image in a markdown file in GitHub/GitLab, you need to upload
|
||||||
|
|
||||||
OneDev tracks your cursor in edit window and scrolls the preview window as necessary so that you can always preview what you are typing.
|
OneDev tracks your cursor in edit window and scrolls the preview window as necessary so that you can always preview what you are typing.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## SLOC Trend By Language
|
## SLOC Trend By Language
|
||||||
|
|
||||||
OneDev inspects git history of main branch to calculate trend of source lines of code by language efficiently.
|
OneDev inspects git history of main branch to calculate trend of source lines of code by language efficiently.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Project Hierarchy to Facilitate Setting Inheritance
|
## Project Hierarchy to Facilitate Setting Inheritance
|
||||||
|
|
||||||
|
|
@ -111,7 +111,7 @@ OneDev is carefully designed with performance in mind. With a 2 core 2GB box, yo
|
||||||
It has been intensively used for more than 5 years, with battle-proven reliability. Fixing bugs is our highest priority, and there is
|
It has been intensively used for more than 5 years, with battle-proven reliability. Fixing bugs is our highest priority, and there is
|
||||||
normally few to no known bugs in the wild.
|
normally few to no known bugs in the wild.
|
||||||
|
|
||||||
----
|
---
|
||||||
|
|
||||||
# Special Thanks
|
# Special Thanks
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue
Block a user