lab02 : Spring Boot and Heroku Hello World
num | ready? | description | assigned | due |
---|---|---|---|---|
lab02 | true | Spring Boot and Heroku Hello World | Wed 10/02 06:15PM | Wed 10/09 11:59PM |
This is an individual lab on the topic of Java web apps on Heroku.
You may cooperate with one or more pair partners from your team to help in debugging and understanding the lab, but each person should complete the lab separately for themselves.
Step 0: If you are working on your own machine
If you are working on CSIL, you can skip this step.
But if you are working on your own machine, you’ll need to install a few things before proceeding.
Here are some commands to let you be familiar with Maven in 5 mins! https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html
-
Install Maven. Instructions are here: https://maven.apache.org/index.html If you are a Mac user, try to install Maven using Homebrew. Type “brew install maven” in your Terminal. (Check if your mac have Homebrew installed firstly)
-
Install the Heroku CLI. Instructions are here: https://devcenter.heroku.com/articles/heroku-cli#download-and-install
Step 1: Understanding what we are trying to do
What are we trying to accomplish again in this lab?
- In this lab, we will create a basic “Hello, World” type web app in Java”
- A web app is a piece of Java code that takes HTTP request messages as input, and responds with HTTP response objects as output.
- Heroku is a platform where we can host a Java web app.
Why use Heroku?
- Web applications run on the “server” side of the web architecture, not the client side.
- So to test a web application, we need to set up a web server that can run Java code.
- Configuring a web server for Java is challenging. But, fortunately, we don’t have to.
- Heroku.com offers “platform as a service” cloud computing for Java web applications.
- We’ll use the “free plan” that they offer for folks just getting started with learning Heroku.
- This puts your application “on the web”, for real, so that anyone in the world can access it 24/7
Limitations of the free plan of Heroku
TL;DR: You should NOT need to enter a credit card into Heroku. If you are asked for one, something has gone wrong.
- If no-one has accessed your web app for a while, it “goes to sleep”, so to speak.
- The first time someone tries to access it after it has gone to sleep, there is a noticable delay in the response, perhaps several seconds or even up to a minute.
- If too many people try to access your service per hour, eventually, you’ll run out of “free resources”.
- That is very unlikely to happen unless you make a web app that somehow attracts the attention of a very large audience.
- I suggest you try to avoid doing that with the web apps you develop for this class.
- I suggest you avoid doing that in general, unless/until you have some plan for how to make money off your web app to pay for the server resources. (With a credit card, you can set up Heroku to have higher usage limits, and to keep your app running so that response time is fast. But you should NOT need that for this course.)
Web Apps vs. Static Web Pages
You may already have some experience with creating static web pages, and/or with creating web applications (e.g. using PHP, Python (Django or Flask) or Ruby on Rails.) If so, then the “Learn More” section will be basic review.
If you are new to writing software for the web, you are strongly encouaged to read the background information at the “learn more” link below.
What are we trying to accomplish again in this lab?
If you just did a deep dive into the article Web Pages vs. Web Apps, it may be helpful to again review what we are trying to accomplish in this lab:
- In this lab, we will create a basic “Hello, World” type web app in Java”
- To test that, we need to run that on a server somewhere.
- Configuring a web server for Java is challenging. But, fortunately, we don’t have to.
- Heroku.com offers “platform as a service” cloud computing for Java web applications.
- We’ll use the “free plan” that they offer for folks just getting started with learning Heroku.
- This puts your application “on the web”, for real, so that anyone in the world can access it 24/7
Disk Quota
IMPORTANT: if you are working on CSIL, and at some point things just “stop working”:
- You get odd error messages, especially “cannot write file”, or “disk quota exceeded”
- You cannot log in—it takes your user name and password on the machines in Phelps 3525 or CSIL, but then just logs you out immediately.
Then you probably have a disk quota problem.
- The best way to troubleshoot this, if you cannot log in, is to ask someone else that CAN log in to allow you to use a terminal window on their screen.
- Use
ssh yourusername@csil.cs.ucsb.edu
to get into your account from their terminal session.
- Use
- For troubleshooting tips, visit: CSIL Disk Quota Troubleshooting
Step 2: Create a Heroku Account
If you do not already have a Heroku account, navigate to https://www.heroku.com/ and click the “Sign up for Free” link.
You’ll be asked for:
- First Name
- Last Name
- Email (you may use any email address you like)
- Company (you may leave this blank).
- Preferred Development Language: We suggest you select “Java” if you are currently enrolled in CMPSC 56
- (Don’t worry; this doesn’t prevent you from using the account with other languages later.)
Step 3: Fork the tutorial repo
“Fork” the tutorial repo into a public copy under your own github account.
To “fork” a repo in Github:
- Look for the “fork” button in the upper right hand corner of the screen
- Click it
- You’ll get a copy of that repo under your own Github id
- Make a “public” fork.
The repo you are going to fork is here:
You’ll need Maven for this lab.
Assuming you are working on CSIL, you can use mvn
to run Maven.
- If you are working on your own machine, you’ll need to install Maven on your machine.
- We’ve collected advice on how to do that here.
Use mvn compile
and mvn exec:java
to try to run the code and get a web app running on localhost.
Note that in order to see this web app running, you’ll need to be in a web browser on the same host that you are running your program on.
- For example, if you are running on
csil-04.cs.ucsb.edu
, you’ll need to be running your web browser oncsil-04.cs.ucsb.edu
. - If you are working in Phelps 3525 on
cstl-07.cs.ucs.edu
, you’ll need to be running your web browser oncstl-07.cs.ucsb.edu
.
If you are not sitting in the CSIL or CSTL lab, i.e. you are using ssh on a laptop to access CSIL, then you might need to test your webapp using a command line web client such as curl
(curl stands for “C” the “URL”). For example, this command should show you the output from the /
route for your webapp:
curl http://localhost:4567
And
curl http://localhost:4567/hello
would show the output from the /hello
route.
This is not very satisfying.
- The web app is only runnning as long as your program is executing.
- As soon as you CTRL/C the program to interrupt it, the web app is no longer available.
- The web app is only available on the machine where you are running the program; not on the public internet.
To get the web app running on the public internet, we’ll need to use a cloud-computing platform such as Heroku.
Step 4: Create a new Heroku App using the Heroku CLI
Logged into CSIL (or one of the machines in the CSTL, i.e. Phelps 3525), use this command to login to Heroku at the command line:
heroku login
NOTE: If the
heroku login
command doesn’t work, you can instead create the Heroku App at the Heroku Dashboard by visiting https://dashboard.heroku.com/apps, clicking (at upper right): “New => Create New App” and then creating an app with the name heroku create cs56-f19-githubid-lab02 as explained in > the instructions below.
Then, use this command to create a new web app running on heroku. Substitute your github id in place of githubid
.
Note that you should convert your githubid to all lowercase; heroku web-app names do not permit uppercase letters.
heroku create cs56-f19-githubid-lab02
Notes:
- A reminder that this is an individual lab, so you should complete it for yourself, i.e. there is only one github id in the name, not a pair of github ids.
- Please do not literally put the letters githubid in your app name; you are meant to substitute your own github id there.
Step 5: Login to the Heroku Dashboard
Login to https://dashboard.heroku.com/apps and look for the create cs56-f19-githubid-lab02 app that you created.
You should find a place where you can connect your App to Github.
Click on this, and select your repo to connect the Github Repo to Heroku.
Then, click on “deploy branch”.
What if it doesn’t work?
If it doesn’t work, try these things before asking a mentor, TA, or instructor for help.
- Make sure you are logged into Heroku at CLI with
heroku login
. If you exited your CSIL shell (logged out) and logged back in again, you have to login to Heroku again. Then repeat the commands. - Try, try running
heroku apps
. Make sure the<appname>app-name-goes-here</appname>
element in theheroku-maven-plugin
section of yourpom.xml
matches the name of your heroku app exactly. - If it does, try
heroku logs --app appname
(substitute the name of your app where you seeappname
). You’ll see the log output of that app on Heroku.- You may find it helpful to open a second Terminal, login to CSIL and the Heroku CLI, and use
heroku logs --app appname --tail
, which keeps the log output running continously. - You can also see your logs in a web browser at: https://dashboard.heroku.com/apps/app-name/logs (note that you need to put your
app-name
in the URL instead ofapp-name
. - You can navigate to this from https://dashboard.heroku.com/ by selecting your app, clicking on it, selecting the
More
menu at upper right, and the selectingLogs
.
- You may find it helpful to open a second Terminal, login to CSIL and the Heroku CLI, and use
Step 6: Changing what is shown on the page
Go into the Java source code under src
and locate the file /src/main/java/hello/HelloController.java
In this file, locate the line of code that says:
@RequestMapping("/")
public String index() {
return "Greetings from Spring Boot!";
}
This method returns the contents of the home page ("/"
) for the webapp.
Change that code to the following. Be sure to replace mygithubid
with your own github id:
String html = "<h1>Hello World!</h1>\n" +
"<p>This web app is powered by \n" +
"<a href='https://github.com/mygithubid/spring-boot-minimal-webapp'>this github repo</a></p>\n";
return html;
Then:
- use
mvn compile
to make sure your code still compiles - (optional, but suggested in case you need to debug)
- use
mvn exec:java
to test locally, perhaps withcurl http://localhost:8081
- use
- Use git add, git commit, and git push to push your changes to github.
- Visit the Heroku Dashboard, and you should see that your changes are deploying to the web.
If it works, then the words “this github repo” should become clickable links.
- The words “this github repo” should link to your github repo
Ok, so far, we haven’t really done anything we couldn’t have done with a static web page. But we have gotten a working Java web app running on Heroku, so it’s start we can build on.
Step 7: The test cases
You’ll see that when you run “mvn test” that there are test cases, some of which are now failing.
The test cases are in these files:
src/test/java/hello/HelloControllerTest.java
(Unit Test)src/test/java/hello/HelloControllerIT.java
(Integration Test)
Run the tests and see them fail.
Then modify them so that they pass. Note that we are doing TDD “wrong” this time; to do it “the right way”, we should have modified the tests first, and then modified the code so that the tests pass. We’ll pivot to this style of working once we have a better grasp on all the moving parts here.
Step 8: Submitting your work for grading
When you have a running web app, visit https://gauchospace.ucsb.edu/courses/mod/assign/view.php?id=2672849 and make a submission.
In the text area, enter something like this, substituting your repo name and your Heroku app name:
repo name: https://github.com/chrislee123/spring-boot-minimal-webapp
on heroku: https://cs56-f19-chrislee123-lab02.herokuapp.com
Then, and this is super important, please make both of those URLs clickable urls.
The instructions for doing so are here: https://ucsb-cs56.github.io/topics/gauchospace_clickable_urls/
Grading Rubric:
- (20 pts) Having a repo that is a fork of https://github.com/pconrad/spring-boot-minimal-webapp
- (20 pts) Having a running web app at https://cs56-f19-githubid-lab02.herokuapp.com
- (20 pts) Running web app has the correct “new” content as specified in Step 6
- (20 pts) Test cases are updated for new content, and they pass (Step 7)
- (10 pts) There is a post on Gauchospace that has the correct content
- (10 pts) The links on Gauchospace are clickable links (to make it easier to test your app)