Checkpoint on deploying to iOS and CF

DEMO.md

@@ -1,214 +0,0 @@
-# Spring Boot, Ionic, and Stormpath
-
-This demo script shows pre-recorded IntelliJ Live Template shortcuts to build an Ionic and Spring Boot app. **Prerequisites**: Java 8, Node.js, Maven, a [Stormpath Account](https://api.stormpath.com/register), and an `apiKey.properties` file in `~/stormpath/`.
-
-## Spring Boot API
-
-Create your Spring Boot API project using [start.spring.io](https://start.spring.io).
-
-```
-http https://start.spring.io/starter.zip \
-dependencies==data-jpa,data-rest,h2,web,devtools,security,stormpath -d
-```
-
-1. Run the application with `./mvnw spring-boot:run`. Create a `Beer` entity class in `src/main/java/com/example/beer`. → **boot-entity**
-2. Create a JPA Repository to manage the `Beer` entity (tip: `@RepositoryRestResource`). → **boot-repository**
-3. Create a CommandLineRunner to populate the database. → **boot-command**
-4. Add default data in the `run()` method. → **boot-add**
-5. Create a `BeerController` for your REST API. Add some business logic that results in a `/good-beers` endpoint. → **boot-controller**
-6. Add a `/get-beers` mapping that filters out beers that aren't great. → **boot-good**
-
-Access the API using `http localhost:8080/good-beers --auth <user>:<password>`.
-
-## Create Ionic App
-
-Install Ionic and Cordova: 
-
-```
-yarn global add cordova ionic
-```
-
-From a terminal window, create a new application using the following command:
-
-```
-ionic start ionic-beer --v2
-cd ionic-beer
-ionic serve
-```
-
-## Upgrade to Angular 2.3
-
-```json
-"dependencies": {
-  "@angular/common": "2.3.1"
-```
-
-Run `yarn` to update to these versions.
-
-## Install Ionic Pages for Stormpath
-
-Install [Ionic pages for Stormpath](https://github.com/stormpath/stormpath-sdk-angular-ionic):
-
-```
-yarn add angular-stormpath-ionic
-```
-
-Modify `src/app/app.module.ts` to define a `stormpathConfig` function that configures the `endpointPrefix` to point to `http://localhost:8080`. Import `StormpathModule`, `StormpathIonicModule`, and override the provider of `StormpathConfiguration`. You’ll also need to append Stormpath's pre-built Ionic pages to `entryComponents`. → **stormpath-config**
-
-To render a login page before users can view the application, modify `src/app/app.component.ts` to use the `Stormpath` service and navigate to Stormpath's `LoginPage` if the user is not authenticated. → **io-app**
-
-```typescript
-stormpath.user$.subscribe(user => {
-  if (!user) {
-    this.rootPage = LoginPage;
-  } else {
-    this.rootPage = TabsPage;
-  }
-});
-```
-
-If you run `ionic serve`, you’ll likely see a CORS error in your browser’s console. To fix this, open your Spring Boot application's `src/main/resources/application.properties` and add the following line.
-
-```
-stormpath.web.cors.allowed.originUris = http://localhost:8100,file://
-```
-
-Restart Spring Boot and your Ionic app. 
-
-In `src/pages/home.html`, add a logout link to the header and a paragraph in the content section that shows the currently logged in user. → **io-logout** and **io-username**
-
-Change the body of `home.ts` to retrieve `user$` from the `Stormpath` service and define the `logout()` method. → **io-home**
-
-If you’re logged in, you should see a screen with a logout button and the name of the currently logged in user.
-
-The `LoginPage` tries to auto-focus onto the `email` field when it loads. Tell Cordova it’s OK to display the keyboard without user interaction by adding the following to `config.xml` in the root directory. → **io-keyboard**
-
-```xml
-<preference name="KeyboardDisplayRequiresUserAction" value="false"/>
-```
-
-Check your changes into Git.
-
-```
-git add .
-git commit -m "Add Stormpath"
-```
-
-## Build a Good Beers UI
-
-1. Run `ionic generate page beer` to create a component and a template to display the list of good beers. 
-2. Add `BeerPage` to the `declarations` and `entryComponent` lists in `app.module.ts`.
-3. Run `ionic generate provider beer-service` to create a service to fetch the beer list from the Spring Boot API.
-4. Change `src/providers/beer-service.ts` to use have a `getGoodBeers()` method. → **io-beer-service**
-5. Modify `beer.html` to show the list of beers. → **io-beer-list**
-6. Update `beer.ts` to import `BeerService` and add as a provider. Call the `getGoodBeers()` method in the `ionViewDidLoad()` lifecycle method. → **io-get-good-beers**
-7. To expose this page on the tab bar, add it to `tabs.ts`. Update `tabs.html` too!
-
-Add some fun with Giphy! Run `ionic generate provider giphy-service`. → **ng-giphy-service**
-
-Update `beer.ts` to take advantage of `GiphyService`. → **ng-giphy-foreach**
-
-Update `beer.html` to display the image retrieved. → **io-avatar**
-
-If everything works as expected, you should see a page with a list of beers and images.
-
-### Add a Modal for Editing
-
-Change the header in `beer.html` to have a button that opens a modal to add a new beer. → **io-open-modal**
-
-In this same file, change `<ion-item>` to have a click handler for opening the modal for the current item.
-
-```html
-<ion-item (click)="openModal({id: beer.id})">
-```
-
-Add `ModalController` as a dependency in `BeerPage` and add an `openModal()` method. → **io-open-modal-ts**
-
-This won't compile because `BeerModalPage` doesn't exist. Create `beer-modal.ts` in the same directory. → **io-beer-modal**
-
-Create `beer-modal.html` as a template for this page. → **io-beer-modal-html**
-
-Add `BeerModalPage` to the `declarations` and `entryComponent` lists in `app.module.ts`.
-
-You'll also need to modify `beer-service.ts` to have `get()` and `save()` methods. → **io-get-save**
-
-### Add Swipe to Delete
-
-To add swipe-to-delete functionality on the list of beers, open `beer.html` and make it so `<ion-item-sliding>` wraps `<ion-item>` and contains the `*ngFor`. → **io-swipe**
-
-Add a `remove()` method to `beer.ts`. → **io-remove**
-
-Add `toastCtrl: ToastController` as a dependency in the constructor so everything compiles.
-
-After making these additions, you should be able to add, edit and delete beers.
-
-## PWAs with Ionic
-
-Run the [Lighthouse Chrome extension](https://developers.google.com/web/tools/lighthouse/) on this application. To register a service worker, and improve the app’s score, uncomment the `serviceWorker` block in `index.html`.
-
-After making this change, the score should improve. In my tests, it increased to 69/100.  
-
-If you refresh the app and Chrome doesn’t prompt you to install the app (a PWA feature), you probably need to turn on a couple of features. 
-
-```
-chrome://flags/#bypass-app-banner-engagement-checks
-chrome://flags/#enable-add-to-shelf
-```
-
-After enabling these flags, you’ll see an error in your browser’s console about `assets/imgs/logo.png` not being found. This files is referenced in `src/manifest.json`. You can fix this by copying a 512x512 PNG into this location or by modifying `manifest.json` accordingly.
-
-## Deploy to a Mobile Device
-
-To see how your application will look on different devices you can run `ionic serve --lab`. The `--lab` flag opens opens a page in your browser that lets you see how your app looks on different devices. 
-
-### iOS
-
-To emulate or deploy to an iOS device, you’ll need a Mac and a fresh installation of [Xcode](https://developer.apple.com/xcode/). If you’d like to build iOS apps on Windows, Ionic offers an [Ionic Package](http://ionic.io/cloud#packaging) service.
-
-```
-ionic platform add ios
-```
-
-You’ll need to run `ionic emulate ios` to open your app in Simulator.
-
-The biggest problem I found when running the app in Simulator was that it was difficult to get the keyboard to popup. To workaround this, I used Edit > Hardware > Keyboard > Toggle Software Keyboard when I needed to type text in a field.
-
-To deploy the app to an iPhone, start by plugging your iOS device into your computer. Then run the following commands to install ios-deploy/ios-sim, build the app, and run it on your device.
-
-```
-npm install -g ios-deploy ios-sim
-ionic build ios
-cd platforms/ios/
-open ionic-beer.xcodeproj
-```
-
-Select your phone as the target in Xcode and click the play button to run your app. 
-
-### Android
-
-To deploy to the Android emulator, add support for it to the ionic-beer project using the `ionic` command.
-
-```
-ionic platform add android
-```
-
-If you run `ionic emulate android` you’ll get instructions from about how to create an emulator image.
-
-```
-Error: No emulator images (avds) found.
-1. Download desired System Image by running: /Users/mraible/Library/Android/sdk/tools/android sdk
-2. Create an AVD by running: /Users/mraible/Library/Android/sdk/tools/android avd
-HINT: For a faster emulator, use an Intel System Image and install the HAXM device driver
-```
-
-Run the first suggestion and download your desired system image. Then  run the second command and created an AVD with the following settings:
-
-```
-AVD Name: TestPhone
-Device: Nexus 5
-Target: Android 7.1.1
-CPU/ABI: Google APIs Intel Axom (x86_64)
-Skin: Skin with dynamic hardware controls
-```
-
-After performing these steps, you should be able to run `ionic emulate android` and see your app running in the AVD.

LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2017 Okta, Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

TUTORIAL.md

@@ -725,7 +725,7 @@ if ('serviceWorker' in navigator) {
 
 After making this change, the score should improve. In my tests, it increased to 66/100. The remaining issues were:
 
-* A couple -1’s in performance for "Cannot read property 'ts' of undefined”.
+* A couple -1’s in performance for "Cannot read property 'ts' of undefined".
 * Site is not progressively enhanced (page should contain some content when JavaScript is not available). This could likely be solved with [Angular’s app-shell directives](https://www.npmjs.com/package/@angular/app-shell).
 * Site is not on HTTPS and does not redirect HTTP to HTTPS.
 
@@ -752,17 +752,30 @@ To emulate or deploy to an iOS device, you’ll need a Mac and a fresh installat
 
 Make sure to open Xcode to complete the installation.
 
-To make your app iOS-capable, add support for it using the following command.
+Ionic 3.0 generates iOS-enabled applications by default. If you're using a version that didn't generate a `platforms/ios` directory, add support for it using the following command.
 
 ```
 ionic platform add ios
 ```
 
-You’ll need to run `ionic emulate ios` to open your app in Simulator.
+Then run `ionic emulate ios` to open your app in Simulator.
 
 The biggest problem I found when running the app in Simulator was that it was difficult to get the keyboard to popup. To workaround this, I used Edit > Hardware > Keyboard > Toggle Software Keyboard when I needed to type text in a field.
 
-To deploy the app to an iPhone, start by plugging your iOS device into your computer. Then run the following commands to install ios-deploy/ios-sim, build the app, and run it on your device. If you've
+Deploying to your phone will likely fail because it won't be able to connect to `http://localhost:8080`. To fix this, you can deploy your Spring Boot app to the internet, or use your computer's IP address (if you're on the same network). 
+
+<div style="padding: 5px; background: #eee; border: 1px solid silver; margin-bottom: 10px">
+<p>To deploy to Cloud Foundry, copy <a href="https://github.com/oktadeveloper/spring-boot-ionic-example/blob/master/deploy.sh">this deploy script</a> to your hard drive. It expects to be in a directory above your apps (e.g. <code>spring-boot-ionic-example</code>). It also expects your apps to be named <code>ionic-beer</code> and <code>server</code>.
+</p>
+<p>
+If you don't have a Cloud Foundry account, you'll need to <a href="https://account.run.pivotal.io/z/uaa/sign-up">create one</a>. Then install its command line tools for this script to work.
+</p>
+<pre style="margin-bottom: 0">
+brew tap cloudfoundry/tap && brew install cf-cli
+</pre>
+</div>
+
+To deploy the app to an iPhone, start by plugging it into your computer. Then run the following commands to install ios-deploy/ios-sim, build the app, and run it on your device. 
 
 ```
 npm install -g ios-deploy ios-sim
@@ -771,15 +784,9 @@ cd platforms/ios/
 open ionic-beer.xcodeproj
 ```
 
-Select your phone as the target in Xcode and click the play button to run your app. The first time you do this, Xcode may spin for a while with a “Processing symbol files” message at the top.
-
-Deploying to your phone will likely fail because it won't be able to connect to `http://localhost:8080`. To fix this, copy [this script](./deploy.sh) to your hard drive. It expects to be in a directory above your apps. It also expects your apps to be named `ionic-beer` and `server`.
+Select your phone as the target in Xcode and click the play button to run your app. The first time you do this, Xcode may spin for a while with a "Processing symbol files" message at the top.
 
-If you don't have a Cloud Foundry account, you'll need to [create one](https://account.run.pivotal.io/z/uaa/sign-up) and install its command line tools for this script to work.
-
-```
-brew tap cloudfoundry/tap && brew install cf-cli
-```
+**NOTE:** If you run into code signing issues, see [Ionic's deployment documentation](http://ionicframework.com/docs/intro/deploying/#ios-devices) to see how to solve.
 
 Once you’re configured your phone, computer, and Apple ID to work, you should be able to open the app and see the beer list you created. Below is how it looks on my iPhone 6s Plus.
 

deploy.sh

@@ -50,12 +50,12 @@ serverUri=https://`app_domain ionic-server`
 cd $r/ionic-beer
 npm run clean
 # replace the server URL in the client
-sed -i -e "s|http://localhost:8080|$serverUri|g" src/app/app.module.ts
-npm install && ionic build ios
+sed -i -e "s|http://localhost:8080|$serverUri|g" src/providers/beer-service.ts
+npm install
 
 # deploy client to phone
-ionic run ios
+ionic run ios --device
 
 # cleanup changed files
 git checkout $r/ionic-beer
-rm $r/ionic-beer/src/app/app.module.ts-e
+rm $r/ionic-beer/src/providers/beer-service.ts-e