Spring/spring-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Polish "Use HTTPS for external links wherever possible"

Browse Source 
See gh-16316
This commit is contained in:
Andy Wilkinson
2019-03-27 11:36:27 +00:00
parent e401d02ced
commit 9be96c49e2
16 changed files with 34 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
spring-boot-docs/src/main/asciidoc/appendix-executable-jar-format.adoc
View File

@@ -279,6 +279,6 @@ alternatives could be considered:
* https://maven.apache.org/plugins/maven-shade-plugin/[Maven Shade Plugin]
* http://www.jdotsoft.com/JarClassLoader.php[JarClassLoader]
* http://one-jar.sourceforge.net[OneJar]
* https://sourceforge.net/projects/one-jar/[OneJar]

4
spring-boot-docs/src/main/asciidoc/deployment.adoc
View File

@@ -340,8 +340,8 @@ and then configure and start the necessary resources on AWS:
Creating security group boxfuse-sg_axelfontaine/myapp:1.0 ...
Launching t2.micro instance of axelfontaine/myapp:1.0 (ami-d23f38cf) in eu-central-1 ...
Instance launched in 00:30.306s -> i-92ef9f53
Waiting for AWS to boot Instance i-92ef9f53 and Payload to start at http://52.28.235.61/ ...
Payload started in 00:29.266s -> http://52.28.235.61/
Waiting for AWS to boot Instance i-92ef9f53 and Payload to start at https://52.28.235.61/ ...
Payload started in 00:29.266s -> https://52.28.235.61/
Remapping Elastic IP 52.28.233.167 to i-92ef9f53 ...
Waiting 15s for AWS to complete Elastic IP Zero Downtime transition ...
Deployment completed successfully. axelfontaine/myapp:1.0 is up and running at https://myapp-axelfontaine.boxfuse.io/

6
spring-boot-docs/src/main/asciidoc/getting-started.adoc
View File

@@ -262,8 +262,8 @@ endif::release[]
[[getting-started-installing-the-cli]]
=== Installing the Spring Boot CLI
The Spring Boot CLI is a command line tool that can be used if you want to quickly
prototype with Spring. It allows you to run https://groovy.codehaus.org/[Groovy] scripts,
which means that you have a familiar Java-like syntax, without so much boilerplate code.
prototype with Spring. It allows you to run http://groovy-lang.org[Groovy] scripts, which
means that you have a familiar Java-like syntax, without so much boilerplate code.
You don't need to use the CLI to work with Spring Boot but it's definitely the quickest
way to get a Spring application off the ground.
@@ -370,7 +370,7 @@ install the Spring Boot CLI is:
[[getting-started-cli-command-line-completion]]
==== Command-line completion
Spring Boot CLI ships with scripts that provide command completion for
https://en.wikipedia.org/wiki/Bash_%2528Unix_shell%2529[BASH] and
https://en.wikipedia.org/wiki/Bash_%28Unix_shell%29[BASH] and
https://en.wikipedia.org/wiki/Zsh[zsh] shells. You can `source` the script (also named
`spring`) in any shell, or put it in your personal or system-wide bash completion
initialization. On a Debian system the system-wide scripts are in `/shell-completion/bash`

4
spring-boot-docs/src/main/asciidoc/production-ready-features.adoc
View File

@@ -1191,8 +1191,8 @@ recommendations.
[[production-ready-metric-writers-export-to-open-tsdb]]
==== Example: Export to Open TSDB
If you provide a `@Bean` of type `OpenTsdbGaugeWriter` and mark it
`@ExportMetricWriter` metrics are exported to http://opentsdb.net/[Open TSDB] for
aggregation. The `OpenTsdbGaugeWriter` has a `url` property that you need to set
`@ExportMetricWriter` metrics are exported to https://github.com/OpenTSDB/opentsdb[Open
TSDB] for aggregation. The `OpenTsdbGaugeWriter` has a `url` property that you need to set
to the Open TSDB "`/put`" endpoint, e.g. `http://localhost:4242/api/put`). It also has a
`namingStrategy` that you can customize or configure to make the metrics match the data
structure you need on the server. By default it just passes through the metric name as an

16
spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
View File

@@ -558,10 +558,10 @@ For example, the following YAML document:
----
environments:
dev:
url: https://dev.bar.com
url: http://dev.example.com
name: Developer Setup
prod:
url: https://foo.bar.com
url: http://another.example.com
name: My Cool App
----
@@ -569,9 +569,9 @@ Would be transformed into these properties:
[source,properties,indent=0]
----
environments.dev.url=https://dev.bar.com
environments.dev.url=http://dev.example.com
environments.dev.name=Developer Setup
environments.prod.url=https://foo.bar.com
environments.prod.url=http://another.example.com
environments.prod.name=My Cool App
----
@@ -582,16 +582,16 @@ for example this YAML:
----
my:
servers:
- dev.bar.com
- foo.bar.com
- dev.example.com
- another.example.com
----
Would be transformed into these properties:
[source,properties,indent=0]
----
my.servers[0]=dev.bar.com
my.servers[1]=foo.bar.com
my.servers[0]=dev.example.com
my.servers[1]=another.example.com
----
To bind to properties like that using the Spring `DataBinder` utilities (which is what