microservice
Here are 4,829 public repositories matching this topic...
Do you want to request a feature or report a bug?
Documentation improvement
In digestAuth documentation, Kubernetes section does not contain any useful example explaining how to put credentials into a file. The given example is same as users(using base
Summary
Currently Kong supports writing configuration in a file, in YAML or JSON.
To provide a more flexible configuration, especially for those running Kong in different environments (dev, staging, production), an option to write configuration in lua can be very useful.
Additional Details
There are many use-cases that come to mind:
- Using environment variables inside the d
Currently at 43.2%.
Issue Description
I updated echo in one of my projects. After that my static configuration didn't work without changes. Before it automatically resolved to an existing index.html. After that I had to point to that file.
My code was something like that:
docsGroup := e.Group("")
docsGroup.Static("/", "docs")
In docs is an index.html which was delivered when no path was given
Why you need it?
Is your feature request related to a problem? Please describe in details
increase rm-datasource module test coverage
How it could be?
A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.
Other related information
Add any other context or screenshots about the feature request here.
Hi all, our bug scanner has reported some NPE bugs.
1.The first one is at FileInJarReadableDataSource.java#L99 since the variable inputStream may be null.
2.The second one is at [SimpleHttpClient.java#L1
i find the root cause of this issue
see config/Docker.file
HEALTHCHECK --interval=10s --timeout=3s CMD curl -f http://localhost:8888/actuator/health || exit 1
values of 10s for interval and 3s for connect timeout is both too small, when the docker machine have a bit lo
在2.3 使用 tarscloud/framework 部署框架中
- 启动框架从节点
如果希望多节点部署, 则在不同机器上执行 docker run ...即可, 注意参数设置!
最新版本:
docker run -d \ --name=tars-framework-slave \ --net=tars \ -e MYSQL_HOST="172.25.0.2" \ -e MYSQL_ROOT_PASSWORD="123456" \ -e MYSQL_USER=root \ -e MYSQL_PORT=3306 \ -e REBUILD=false \ -e INET=eth0 \ -e
If I were to deploy cube.js using AWS serverless architecture, is athena required?
The docs https://cube.dev/docs/deployment#serverless do not mention whether Athena is optional or required. But when reading it, I assume it is required because there are athena keys in the serverless.yml config. I'm evaluating the idea of using Postgres RDS as the sole datasource for cubejs.
Prerequisites
- I am running the latest version. (
up upgrade) - I searched to see if the issue already exists.
- I inspected the verbose debug output with the
-v, --verboseflag. - Are you an Up Pro subscriber?
Description
It would be great to add regex capabilities to redirects like so:
redirects: {
"/folder/:slug(regexhere)": {
"location": "https
[E2E] Fix Makefile to allow 'make test-e2e-all' to work on Windows + Minikube + MinGW + GitBash
Current behavior
Issue: Windows + minikube + MinGW + GitBash + make (gets stuck)
asouza@ASOUZA-DESKTOP MINGW64 /c/Code/dapr/dapr (master)
$ make test-e2e-all
DAPR_TEST_NAMESPACE=dapr-tests DAPR_TEST_TAG=dev DAPR_TEST_REGISTRY=docker.io/artursouza DAPR_TEST_MINIKUBE_IP= go test -v -tags=e2e ./tests/e2e/...Workaround: see how I had to manually run the same command but set t
-
Updated
Jun 12, 2020
集合类功能可以实现高阶消息吗?
-
Updated
Jun 10, 2020 - Go
-
Updated
Jul 18, 2019
Describe the feature
I'd like to be able to document multiple different APIs separately in the same Javalin application. I.e. have 3 handlers go to doc A, and have another 3 handlers go to doc B.
Additional context
The purpose of this feature request is API versioning; I'd like to version my API, and have separate docs for each version.
-
Updated
Jun 12, 2020 - C#
-
Updated
Jun 12, 2020 - Makefile
Prerequisites
- I am running the latest version
- I checked the documentation and found no answer
- I checked to make sure that this issue has not already been filed
- I'm reporting the issue to the correct repository
Current Behavior
Using the approach [documented in Datadog's docs](https://docs.datadoghq.com/tracing/connect_
Hi,
I went through the documentation and couldn't find anything about using imgproxy with a SPA framework like vue. Are there any examples or guides on this?
If I understand correctly imgproxy is ment to be used serverside because of the encryption aspect. Would love to know about any best practices on how to implement it in a SPA scenario.
Thank you
-
Updated
Jun 12, 2020 - Go
-
Updated
Mar 29, 2020 - Java
$ docker run --rm -p 9000:9000 h2non/imaginary -enable-url-source
$ curl http://localhost:9000/smartcrop?width=31&height=31&type=webp&url=https://camo.githubusercontent.com/bcb3b2bd343c3c85aaf6094e51c6178bbe239a32/687474703a2f2f7331342e706f7374696d672e6f72672f3874683731613230312f696d6167696e6172795f776f726c642e6a7067
{"message":"Error while processing the image: shrink: parameter vshrin-
Updated
Jun 7, 2020 - Java
Thanks to Gabor Horvath for suggesting this feature:
Is the Rendering API documentation feature mandatory for starting up AES? If not, maybe there should be an option offered to disable it. For our use case, an option to disable it and as a result of that disabling calling home to GitHub would be useful.
Add a config option to specify host:post.
Currently one can only set the port via config option Port just for krakend to use this value as a string.
func NewServer(cfg config.ServiceConfig, handler http.Handler) *http.Server {
return &http.Server{
Addr: fmt.Sprintf(":%d", cfg.Port),
...
}
}
Issue Description
Type: feature request
Describe what happened (or what feature you want)
chaosblade是一款覆盖面很广的故障注入测试工具,因此我希望引入此软件对 K8s Paas平台进行测试,但是发现只能针对特定的pod进行故障注入(delete pod或者pod cpu负载等),没有其他针对Paas 的chaos工具(Powerfulseal、Chaos-mesh等)拥有在规定时间内随机等delete 规定分区下的po
Improve this page
Add a description, image, and links to the microservice topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the microservice topic, visit your repo's landing page and select "manage topics."

I have created a serverless project for python on AWS, which works fine... until I try to re-use the project directly after checkout. Any CLI command exits with the following error: