You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: spring-boot-project/spring-boot-docs/src/docs/asciidoc/deployment/cloud.adoc
+11-11
Original file line number
Diff line number
Diff line change
@@ -310,25 +310,25 @@ There is a https://exampledriven.wordpress.com/2017/01/09/spring-boot-aws-elasti
310
310
311
311
312
312
[[deployment.cloud.boxfuse]]
313
-
=== Boxfuse and Amazon Web Services
314
-
https://boxfuse.com/[Boxfuse] works by turning your Spring Boot executable jar or war into a minimal VM image that can be deployed unchanged either on VirtualBox or on AWS.
315
-
Boxfuse comes with deep integration for Spring Boot and uses the information from your Spring Boot configuration file to automatically configure ports and health check URLs.
316
-
Boxfuse leverages this information both for the images it produces as well as for all the resources it provisions (instances, security groups, elastic load balancers, and so on).
313
+
=== CloudCaptain and Amazon Web Services
314
+
https://cloudcaptain.sh/[CloudCaptain] works by turning your Spring Boot executable jar or war into a minimal VM image that can be deployed unchanged either on VirtualBox or on AWS.
315
+
CloudCaptain comes with deep integration for Spring Boot and uses the information from your Spring Boot configuration file to automatically configure ports and health check URLs.
316
+
CloudCaptain leverages this information both for the images it produces as well as for all the resources it provisions (instances, security groups, elastic load balancers, and so on).
317
317
318
-
Once you have created a https://console.boxfuse.com[Boxfuse account], connected it to your AWS account, installed the latest version of the Boxfuse Client, and ensured that the application has been built by Maven or Gradle (by using, for example, `mvn clean package`), you can deploy your Spring Boot application to AWS with a command similar to the following:
318
+
Once you have created a https://console.cloudcaptain.sh[CloudCaptain account], connected it to your AWS account, installed the latest version of the CloudCaptain Client, and ensured that the application has been built by Maven or Gradle (by using, for example, `mvn clean package`), you can deploy your Spring Boot application to AWS with a command similar to the following:
319
319
320
320
[source,shell,indent=0,subs="verbatim"]
321
321
----
322
322
$ boxfuse run myapp-1.0.jar -env=prod
323
323
----
324
324
325
-
See the https://boxfuse.com/docs/commandline/run.html[`boxfuse run` documentation] for more options.
326
-
If there is a https://boxfuse.com/docs/commandline/#configuration[`boxfuse.conf`] file present in the current directory, it is considered.
325
+
See the https://cloudcaptain.sh/docs/commandline/run.html[`boxfuse run` documentation] for more options.
326
+
If there is a https://cloudcaptain.sh/docs/commandline/#configuration[`boxfuse.conf`] file present in the current directory, it is considered.
327
327
328
-
TIP: By default, Boxfuse activates a Spring profile named `boxfuse` on startup.
329
-
If your executable jar or war contains an https://boxfuse.com/docs/payloads/springboot.html#configuration[`application-boxfuse.properties`] file, Boxfuse bases its configuration on the properties it contains.
328
+
TIP: By default, CloudCaptain activates a Spring profile named `boxfuse` on startup.
329
+
If your executable jar or war contains an https://cloudcaptain.sh/docs/payloads/springboot.html#configuration[`application-boxfuse.properties`] file, CloudCaptain bases its configuration on the properties it contains.
330
330
331
-
At this point, `boxfuse` creates an image for your application, uploads it, and configures and starts the necessary resources on AWS, resulting in output similar to the following example:
331
+
At this point, CloudCaptain creates an image for your application, uploads it, and configures and starts the necessary resources on AWS, resulting in output similar to the following example:
332
332
333
333
[indent=0,subs="verbatim"]
334
334
----
@@ -353,7 +353,7 @@ At this point, `boxfuse` creates an image for your application, uploads it, and
353
353
354
354
Your application should now be up and running on AWS.
355
355
356
-
See the blog post on https://boxfuse.com/blog/spring-boot-ec2.html[deploying Spring Boot apps on EC2] as well as the https://boxfuse.com/docs/payloads/springboot.html[documentation for the Boxfuse Spring Boot integration] to get started with a Maven build to run the app.
356
+
See the blog post on https://cloudcaptain.sh/blog/spring-boot-ec2.html[deploying Spring Boot apps on EC2] as well as the https://cloudcaptain.sh/docs/payloads/springboot.html[documentation for the CloudCaptain Spring Boot integration] to get started with a Maven build to run the app.
0 commit comments