Aggregate slime: move modules to staging dir #152
Conversation
| @@ -3,7 +3,7 @@ | |||
| MODS=${MODS:-"lazyload limiter plugin"} | |||
There was a problem hiding this comment.
We can traverse these modules through the file directory so that we don't have to list them explicitly. But this can be done later
| @@ -0,0 +1,27 @@ | |||
|
|
|||
There was a problem hiding this comment.
remove ths .gitignore file of modules
| WORKDIR / | ||
| COPY manager.exe ./manager | ||
|
|
||
| ENTRYPOINT ["/manager"] |
There was a problem hiding this comment.
no newline at the end of file
| message DomainAlias { | ||
| string pattern = 1; | ||
| repeated string templates = 2; | ||
| } |
|
|
||
| option go_package = "slime.io/slime/modules/lazyload/api/v1alpha1"; | ||
|
|
||
| // ServiceFence是在社区Sidecar资源之上的一层封装，其主要作用与Sidecar资源相同，可以隔绝服务 |
| map<string, Destinations> domains = 1; | ||
| map<string, string> metricStatus = 3; | ||
| map<string, bool> visitor = 2; | ||
| } |
|
|
||
| COPY manager.exe ./proxy-app | ||
|
|
||
| ENTRYPOINT ["/proxy-app"] |
| #!/usr/bin/env bash | ||
|
|
||
| export MOD=global-sidecar | ||
| ../../../slime/bin/publish.sh "$@" |
| image: | ||
| pullPolicy: Always | ||
| repository: docker.io/slimeio/slime-plugin | ||
| tag: v0.2.0_linux_amd64 |
| "slime.io/slime/modules/plugin/api/v1alpha1" | ||
| ) | ||
|
|
||
| type NeteaseType interface { |
| memory: 800Mi | ||
| image: | ||
| repository: docker.io/slimeio/pilot | ||
| tag: {{globalSidecarPilotTag}} |
| volumes: | ||
| - name: tmp | ||
| emptyDir: {} | ||
| --- |
| memory: 400Mi | ||
| image: | ||
| repository: docker.io/slimeio/slime-global-sidecar | ||
| tag: v0.2.0-1b93bf7 |
There was a problem hiding this comment.
use find . -type f -print0 | xargs -0 -L1 bash -c 'test "$(tail -c 1 "$0")" && echo "No new line at end of $0"' or pcregrep -LMr '\n\Z' . to find all files with no newline at the end
|
Will we periodically published to respective top-level slim.io repositories? Just like k8s |
Existing module repos should be retained, but not updated for now. It may be better to publish to respective repos regularly until slime community reaches a higher level. |
To aggregate Slime project, move all slime modules to slime main project. The specific path is
staging/src/slime.io/slime/modules.The main changes are as below:
staging/src/slime.io/slime/modulesslime.io/slime/framework => ... /... /... /... /... /... /framework... /... /... /... /... /... /bin/publish.sh "$@"We can develop all modules in single project to keep version consistency, ameanwhile they do not bother others in the future.