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
This command will create a new REST application in the `getting-started-with-heroku` directory.
56
+
57
+
Let's make this application a Git repository:
58
+
59
+
1. Change to the application directory: `cd getting-started-with-heroku`.
60
+
2. Initialize a new Git repository: `git init -b main`.
61
+
3. Add all files to the repository: `git add .`.
62
+
4. Commit the files: `git commit -a -m 'Initial copy of getting-started'`.
53
63
54
64
Heroku can react on changes in your repository, run CI and redeploy your application when your code changes.
55
65
Therefore, we start with a valid repository already.
@@ -110,25 +120,39 @@ git add Procfile
110
120
git commit -am "Add a Procfile."
111
121
----
112
122
113
-
Your application should already be runnable via `heroku local web`.
123
+
Your application should already be runnable via `heroku local web` from the repository root directory. You need to have run `mvn package` before to create the runnable jar for this to succeed.
114
124
115
-
Let's create an application in your account and deploy that repository to it:
125
+
Now let's create an application in your account and deploy that repository to it:
116
126
117
127
[source,bash]
118
128
----
119
129
heroku create
120
-
git push heroku master
121
-
heroku open
122
130
----
123
131
124
-
The application will have a generated name and the terminal should output that. `heroku open` opens your default browser to access your new application.
132
+
This will create a remote repository in your Heroku account, and it should have also added a heroku remote url to your local repository which you can view using `git remote -v`:
Now you can push your application to Heroku and open it in your browser.
141
+
[source,bash]
142
+
----
143
+
git push heroku main
144
+
heroku open hello
145
+
----
146
+
147
+
The application will have a generated URL and the terminal should output that. `heroku open hello` opens your default browser to access your new application using the '/hello' context. That page should output the text 'hello'.
125
148
126
-
To access the REST endpoint via curl, run:
149
+
To access the REST endpoint via curl, get the app URL from the heroku info command:
127
150
128
151
[source,bash]
129
152
----
130
-
APP_NAME=`heroku info | grep "=== .*" |sed "s/=== //"`
131
-
curl $APP_NAME.herokuapp.com/hello
153
+
heroku info | grep "Web URL:"
154
+
APP_NAME=<https url info>
155
+
curl $APP_NAME/hello
132
156
----
133
157
134
158
Of course, you can use the Heroku CLI to connect this repo to your GitHub account, too, but this is out of scope for this guide.
@@ -137,18 +161,23 @@ Of course, you can use the Heroku CLI to connect this repo to your GitHub accoun
137
161
138
162
The advantage of pushing a whole container is that we are in complete control over its content and maybe even choose to deploy a container with a native executable running on GraalVM.
139
163
164
+
140
165
First, login to Heroku's container registry:
141
166
142
167
[source,bash]
143
168
-----
144
169
heroku container:login
145
170
-----
146
171
147
-
We need to add an extension to our project to build container images via the Quarkus Maven plugin:
172
+
We need to add an extension to our project to add the capability to build container images:
Copy file name to clipboardExpand all lines: _versions/main/guides/maven-tooling.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -652,7 +652,7 @@ Uber-Jar's final name is configurable via a Maven's build settings `finalName` o
652
652
653
653
==== Uber-Jar file name suffix
654
654
655
-
By default the generated uber JAR file name will have the `-runner` suffix, unless it was overridden by configuring a custom one with `quarkus.package.runner-suffix` configuration option.
655
+
By default the generated uber JAR file name will have the `-runner` suffix, unless it was overridden by configuring a custom one with `quarkus.package.jar.runner-suffix` configuration option.
656
656
If the runner suffix is not desired, it can be disabled by setting `quarkus.package.jar.add-runner-suffix` configuration option to `false`, in which case the uber JAR will replace the original JAR
657
657
file generated by `maven-jar-plugin` for the application module.
The link:https://smallrye.io/docs/smallrye-fault-tolerance/6.7.1/reference/programmatic-api.html[programmatic API] is present and integrated with the declarative, annotation-based API.
611
+
The link:https://smallrye.io/docs/smallrye-fault-tolerance/6.7.2/reference/programmatic-api.html[programmatic API] is present and integrated with the declarative, annotation-based API.
612
612
You can use the `Guard`, `TypedGuard` and `@ApplyGuard` APIs out of the box.
613
613
614
614
Support for Kotlin is present (assuming you use the Quarkus extension for Kotlin), so you can guard your `suspend` functions with fault tolerance annotations.
0 commit comments