简体   繁体   English

使用Git repo配置jhipster-registry v3.0.3

[英]Configuring jhipster-registry v3.0.3 with Git repo

I am trying to use the pre-packaged v3.0.3 war file for the jhipster-registry. 我正在尝试使用预先打包的v3.0.3 war文件用于jhipster-registry。 I am launching it with these command-line properties in an attempt to point it to my Git repo for configuration info: 我正在使用这些命令行属性启动它,试图将它指向我的Git仓库以获取配置信息:

jhipster-registry-3.0.3.war --spring.profiles.active=prod,cust1 \
--spring.cloud.config.server.git.uri=http://myserver/url/MyConfig \
--spring.cloud.config.server.git.username=user \
--spring.cloud.config.server.git.password=pass

It starts, but I always get this error: 它开始,但我总是得到这个错误:

Your JWT secret key is not set up, you will not be able to log into the JHipster

I've tried many combinations of how to setup the Git repo. 我已经尝试了很多如何设置Git repo的组合。 I'm using the sample application.yml file from https://github.com/jhipster/jhipster-registry-sample-config 我正在使用来自https://github.com/jhipster/jhipster-registry-sample-config的示例application.yml文件

Does the jhipster-registry itself not read any configuration files from Git? jhipster-registry本身是不是从Git读取任何配置文件?

If I want to configure the jhipster-registry properties, should I keep overriding things on the command-line, or put a yml file somewhere? 如果我想配置jhipster-registry属性,我应该在命令行上保留覆盖内容,还是将yml文件放在某处? It isn't clear to me the proper way to configure it when it is a pre-built war file and has embedded bootstrap/application yml files. 当它是一个预构建的war文件并且嵌入了bootstrap / application yml文件时,我不清楚配置它的正确方法。

Is there a way to turn on debug logging so I can see what is going on? 有没有办法打开调试日志记录,以便我可以看到发生了什么?

This is because your JWT token isn't configured in your Git repository. 这是因为您的Git存储库中未配置您的JWT令牌。 Have a look at our sample Git repository . 看看我们的示例Git存储库 The Registry will send this token to all configured applications, and thus will be able to connect to them. 注册表将此令牌发送到所有已配置的应用程序,因此将能够连接到它们。

Otherwise, it shows a warning as it knows this will be an issue later. 否则,它会显示警告,因为它知道这将是一个问题。

Please note that this is a difference from the "classical" Eureka and Spring Cloud Config servers, which are not secured by default. 请注意,这与“经典”Eureka和Spring Cloud Config服务器不同,默认情况下不受保护。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM