Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit945733d

Browse files
Fixed broken images
1 parent1005ac2 commit945733d

30 files changed

+38
-38
lines changed

‎_docs/example-catalog/ci-examples/django.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -68,8 +68,8 @@ Creating a CI/CD pipeline for Django is very easy if you already have the Docker
6868

6969
{% include image.html
7070
lightbox="true"
71-
file="/images/learn-by-example/python/python-build-test.png"
72-
url="/images/learn-by-example/python/python-build-test.png"
71+
file="/images/examples/python/python-build-test.png"
72+
url="/images/examples/python/python-build-test.png"
7373
alt="Creating a Docker image for Python"
7474
caption="Creating a Docker image for Python"
7575
max-width="80%"
@@ -122,8 +122,8 @@ Sometimes if you have a complex application you might want to run integration te
122122

123123
{% include image.html
124124
lightbox="true"
125-
file="/images/learn-by-example/python/python-test-build.png"
126-
url="/images/learn-by-example/python/python-test-build.png"
125+
file="/images/examples/python/python-test-build.png"
126+
url="/images/examples/python/python-test-build.png"
127127
alt="Building the image after tests have run"
128128
caption="Building the image after tests have run"
129129
max-width="80%"

‎_docs/example-catalog/ci-examples/goreleaser.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -91,8 +91,8 @@ It also possible to pass a GITHUB_TOKEN directly in the pipeline, if you don't w
9191

9292
{% include image.html
9393
lightbox="true"
94-
file="/images/learn-by-example/golang/github-token.png"
95-
url="/images/learn-by-example/golang/github-token.png"
94+
file="/images/examples/golang/github-token.png"
95+
url="/images/examples/golang/github-token.png"
9696
alt="Passing a specific github token in the pipeline"
9797
caption="Passing a specific github token in the pipeline"
9898
max-width="70%"
@@ -104,8 +104,8 @@ Regardless of the way you choose to pass the GitHub token, the final step is to
104104

105105
{% include image.html
106106
lightbox="true"
107-
file="/images/learn-by-example/golang/tags-only-trigger.png"
108-
url="/images/learn-by-example/golang/tags-only-trigger.png"
107+
file="/images/examples/golang/tags-only-trigger.png"
108+
url="/images/examples/golang/tags-only-trigger.png"
109109
alt="Run pipeline only on tag creation"
110110
caption="Run pipeline only on tag creation"
111111
max-width="80%"

‎_docs/example-catalog/ci-examples/gradle.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -96,8 +96,8 @@ This will compile/test/package the Gradle application and create a Docker image.
9696

9797
{% include image.html
9898
lightbox="true"
99-
file="/images/learn-by-example/java/gradle-multistage.png"
100-
url="/images/learn-by-example/java/gradle-multistage.png"
99+
file="/images/examples/java/gradle-multistage.png"
100+
url="/images/examples/java/gradle-multistage.png"
101101
alt="Gradle Multi-stage Docker build"
102102
caption="Gradle Multi-stage Docker build"
103103
max-width="80%"
@@ -182,8 +182,8 @@ The pipeline starts by checking out the code using a [git clone step]({{site.bas
182182

183183
{% include image.html
184184
lightbox="true"
185-
file="/images/learn-by-example/java/gradle-ci-pipeline.png"
186-
url="/images/learn-by-example/java/gradle-ci-pipeline.png"
185+
file="/images/examples/java/gradle-ci-pipeline.png"
186+
url="/images/examples/java/gradle-ci-pipeline.png"
187187
alt="Gradle pipeline"
188188
caption="Gradle pipeline"
189189
max-width="80%"

‎_docs/example-catalog/ci-examples/lets-chat.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,8 @@ Creating a CI/CD pipeline for NodeJS is very easy, because Codefresh has built-i
2323

2424
{% include image.html
2525
lightbox="true"
26-
file="/images/learn-by-example/nodejs/nodejs-pipeline.png"
27-
url="/images/learn-by-example/nodejs/nodejs-pipeline.png"
26+
file="/images/examples/nodejs/nodejs-pipeline.png"
27+
url="/images/examples/nodejs/nodejs-pipeline.png"
2828
alt="Building and testing a Node.js application"
2929
caption="Building and testing a Node.js application"
3030
max-width="100%"

‎_docs/example-catalog/ci-examples/php.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -75,8 +75,8 @@ Once you run this pipeline Codefresh will create a Docker image for the Php appl
7575

7676
{% include image.html
7777
lightbox="true"
78-
file="/images/learn-by-example/php/php-cicd-pipeline.png"
79-
url="/images/learn-by-example/php/php-cicd-pipeline.png"
78+
file="/images/examples/php/php-cicd-pipeline.png"
79+
url="/images/examples/php/php-cicd-pipeline.png"
8080
alt="Creating a docker image for php"
8181
caption="Creating a docker image for php"
8282
max-width="80%"
@@ -95,8 +95,8 @@ First find your images in the [Docker image dashboard]({{site.baseurl}}/docs/doc
9595

9696
{% include image.html
9797
lightbox="true"
98-
file="/images/learn-by-example/php/launch-docker-image.png"
99-
url="/images/learn-by-example/php/launch-docker-image.png"
98+
file="/images/examples/php/launch-docker-image.png"
99+
url="/images/examples/php/launch-docker-image.png"
100100
alt="Launching a Docker image"
101101
caption="Launching a Docker image"
102102
max-width="80%"
@@ -106,8 +106,8 @@ Click on the launch button and a new pipeline will run for deployment:
106106

107107
{% include image.html
108108
lightbox="true"
109-
file="/images/learn-by-example/php/test-environment-url.png"
110-
url="/images/learn-by-example/php/test-environment-url.png"
109+
file="/images/examples/php/test-environment-url.png"
110+
url="/images/examples/php/test-environment-url.png"
111111
alt="Getting the environment url"
112112
caption="Getting the environment url"
113113
max-width="80%"
@@ -118,8 +118,8 @@ and you will see the result.
118118

119119
{% include image.html
120120
lightbox="true"
121-
file="/images/learn-by-example/php/test-environment.png"
122-
url="/images/learn-by-example/php/test-environment.png"
121+
file="/images/examples/php/test-environment.png"
122+
url="/images/examples/php/test-environment.png"
123123
alt="Application preview"
124124
caption="Application preview"
125125
max-width="80%"

‎_docs/example-catalog/ci-examples/publish-jar.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -25,8 +25,8 @@ We use Nexus for this example. To upload the Jar manually first edit the `pom.xm
2525

2626
{% include image.html
2727
lightbox="true"
28-
file="/images/learn-by-example/java/nexus-browser.png"
29-
url="/images/learn-by-example/java/nexus-browser.png"
28+
file="/images/examples/java/nexus-browser.png"
29+
url="/images/examples/java/nexus-browser.png"
3030
alt="The Nexus package manager"
3131
caption="The Nexus package manager"
3232
max-width="80%"
@@ -46,8 +46,8 @@ If you then visit Nexus you should see your JAR file in the snapshots repository
4646

4747
{% include image.html
4848
lightbox="true"
49-
file="/images/learn-by-example/java/nexus-credentials.png"
50-
url="/images/learn-by-example/java/nexus-credentials.png"
49+
file="/images/examples/java/nexus-credentials.png"
50+
url="/images/examples/java/nexus-credentials.png"
5151
alt="Parameters for Nexus"
5252
caption="Parameters for Nexus"
5353
max-width="50%"
@@ -82,8 +82,8 @@ You can define the version of Maven/JDK you want to use by picking the appropria
8282
Note the use of the two user-defined environment variables passed to`server.password` and`server.username`. You will need to define those yourself. See the documentation on[User Procided Variables]({{site.baseurl}}/docs/pipelines/variables/#user-provided-variables).
8383
{% include image.html
8484
lightbox="true"
85-
file="/images/learn-by-example/java/publish-jar-pipeline.png"
86-
url="/images/learn-by-example/java/publish-jar-pipeline.png"
85+
file="/images/examples/java/publish-jar-pipeline.png"
86+
url="/images/examples/java/publish-jar-pipeline.png"
8787
alt="Publish JAR pipeline"
8888
caption="Publish JAR pipeline"
8989
max-width="100%"
@@ -93,8 +93,8 @@ Once the pipeline has finished you should see the JAR file in the Nexus browser
9393

9494
{% include image.html
9595
lightbox="true"
96-
file="/images/learn-by-example/java/nexus-upload.png"
97-
url="/images/learn-by-example/java/nexus-upload.png"
96+
file="/images/examples/java/nexus-upload.png"
97+
url="/images/examples/java/nexus-upload.png"
9898
alt="Upload finished"
9999
caption="Upload finished"
100100
max-width="70%"

‎_docs/example-catalog/ci-examples/react.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -63,8 +63,8 @@ Creating a CI/CD pipeline for React is very easy, because Codefresh can run any
6363

6464
{% include image.html
6565
lightbox="true"
66-
file="/images/learn-by-example/nodejs/react-pipeline-docker.png"
67-
url="/images/learn-by-example/nodejs/react-pipeline-docker.png"
66+
file="/images/examples/nodejs/react-pipeline-docker.png"
67+
url="/images/examples/nodejs/react-pipeline-docker.png"
6868
alt="Creating a Docker image for react.js"
6969
caption="Creating a Docker image for react.js"
7070
max-width="80%"
@@ -120,8 +120,8 @@ If your application is not dockerized yet, you can still create a pipeline that
120120

121121
{% include image.html
122122
lightbox="true"
123-
file="/images/learn-by-example/nodejs/react-pipeline-build.png"
124-
url="/images/learn-by-example/nodejs/react-pipeline-build.png"
123+
file="/images/examples/nodejs/react-pipeline-build.png"
124+
url="/images/examples/nodejs/react-pipeline-build.png"
125125
alt="Building a Reach.js application"
126126
caption="Building a Reach.js application"
127127
max-width="80%"

‎_docs/example-catalog/ci-examples/spring-boot-2.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -112,8 +112,8 @@ step that uses [service containers]({{site.baseurl}}/docs/pipelines/service-cont
112112

113113
{% include image.html
114114
lightbox="true"
115-
file="/images/learn-by-example/java/spring-boot-steps.png"
116-
url="/images/learn-by-example/java/spring-boot-steps.png"
115+
file="/images/examples/java/spring-boot-steps.png"
116+
url="/images/examples/java/spring-boot-steps.png"
117117
alt="Spring boot pipeline"
118118
caption="Spring boot pipeline"
119119
max-width="80%"
@@ -129,8 +129,8 @@ The next step is a Docker build. We name our image **spring-boot-2-sample-app**
129129

130130
{% include image.html
131131
lightbox="true"
132-
file="/images/learn-by-example/java/spring-boot-docker-image.png"
133-
url="/images/learn-by-example/java/spring-boot-docker-image.png"
132+
file="/images/examples/java/spring-boot-docker-image.png"
133+
url="/images/examples/java/spring-boot-docker-image.png"
134134
alt="Spring Boot Docker image"
135135
caption="Spring Boot Docker image"
136136
max-width="80%"
19.4 KB
Loading
22 KB
Loading

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp