harbor/make/common/templates/core/env

LOG_LEVEL=info
CONFIG_PATH=/etc/core/app.conf
CORE_SECRET=$core_secret
JOBSERVICE_SECRET=$jobservice_secret
UAA_CA_ROOT=/etc/core/certificates/uaa_ca.pem
_REDIS_URL=$redis_host:$redis_port,100,$redis_password
SYNC_REGISTRY=false
CHART_CACHE_DRIVER=$chart_cache_driver
_REDIS_URL_REG=$redis_url_reg
Update harbor default log level to info (#4639) 2018-04-12 13:04:44 +02:00			`LOG_LEVEL=info`
Rename harbor-ui to harbor-core 1. Update the nginx.conf 2. Update Makefile 3. Update docker-compose 4. Update image name 5. Rename folder ui to core 6. Change the harbor-ui's package name to core 7. Remove unused static file on harbor-core 8. Remove unused code for harbor-portal Signed-off-by: Qian Deng <dengq@vmware.com> 2018-09-12 08:38:29 +02:00			`CONFIG_PATH=/etc/core/app.conf`
			`CORE_SECRET=$core_secret`
using different secret to mark himself when communicates with other components 2017-02-23 11:02:19 +01:00			`JOBSERVICE_SECRET=$jobservice_secret`
Rename harbor-ui to harbor-core 1. Update the nginx.conf 2. Update Makefile 3. Update docker-compose 4. Update image name 5. Rename folder ui to core 6. Change the harbor-ui's package name to core 7. Remove unused static file on harbor-core 8. Remove unused code for harbor-portal Signed-off-by: Qian Deng <dengq@vmware.com> 2018-09-12 08:38:29 +02:00			`UAA_CA_ROOT=/etc/core/certificates/uaa_ca.pem`
Unify redis configuration for harbor components (#5564) this commit is to specrate the redis_url into host,port,pwd and index for different components, and make it possible to set external redis server. 2018-08-09 09:27:46 +02:00			`_REDIS_URL=$redis_host:$redis_port,100,$redis_password`
add sync registry env (#5294) By default Harbor will call catalog API of registry and sync the result to DB, this becomes problematic when registry is configured to custom storage service, there maybe inconsistent result and the whole process may be very time consuming. So in this commit a env var SYNC_REGISTRY is introduced if user want Harbor to sync the repo when it starts up, by default it's false. 2018-07-13 05:15:41 +02:00			`SYNC_REGISTRY=false`
Keep the chart server related configurations in adminserver append chart server related config options to the supporting list of adminserver provide chart server related config access method in the API layer update prepare script and ui env template file to enable cache driver config for chart server API append flag info in the systeminfo API to indicate if chart server is deployed with Harbor refactor the response rewriting logic to return structual error object add api init method to initilizing objects required in API handlers chage owner of the storage folder update offline/online package scripts in Harbor-Util.robot 2018-07-19 17:50:25 +02:00			`CHART_CACHE_DRIVER=$chart_cache_driver`
Signed-off-by: wangyan <wangyan@vmware.com> Add clean registry cache to gc job To workaround the issue: https://github.com/docker/distribution/issues/2094 GC needs to clean cache before to call the docker reigstry api to delete blobs. Otherwise, the following docker push will not be performed as docker registry does not clean cache in GC, it thinks the image is still there, and the new blobs will be uploaded. 2018-08-09 13:04:35 +02:00			`_REDIS_URL_REG=$redis_url_reg`