app/ayanova/package-lock.json

@@ -14872,6 +14872,11 @@
       "integrity": "sha1-hnrHTjhkGHsdPUfZlqeOxciDB3c=",
       "dev": true
     },
+    "typeface-roboto": {
+      "version": "0.0.54",
+      "resolved": "https://registry.npmjs.org/typeface-roboto/-/typeface-roboto-0.0.54.tgz",
+      "integrity": "sha512-sOFA1FXgP0gOgBYlS6irwq6hHYA370KE3dPlgYEJHL3PJd5X8gQE0RmL79ONif6fL5JZuGDj+rtOrFeOqz5IZQ=="
+    },
     "uglify-es": {
       "version": "3.3.9",
       "resolved": "https://registry.npmjs.org/uglify-es/-/uglify-es-3.3.9.tgz",

app/ayanova/package.json

@@ -14,6 +14,7 @@
     "jwt-decode": "^2.2.0",
     "nprogress": "^0.2.0",
     "register-service-worker": "^1.0.0",
+    "typeface-roboto": "0.0.54",
     "vue": "^2.5.17",
     "vue-router": "^3.0.1",
     "vuetify": "^1.3.0",

app/ayanova/public/index.html

@@ -6,10 +6,10 @@
     <meta name="viewport" content="width=device-width,initial-scale=1.0" />
     <link rel="icon" href="<%= BASE_URL %>favicon.ico" />
     <title>ayanova</title>
-    <link
+    <!-- <link
       rel="stylesheet"
       href="https://fonts.googleapis.com/css?family=Roboto:100,300,400,500,700,900"
-    />
+    /> -->
 
     <!--
       <link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.4.2/css/all.css" integrity="sha384-/rXc/GQVaYpyDdyxK+ecHPVYJSN9bmVFBvjA/9eOB+pb3F2w2N6fc5qB9Ew5yIns" crossorigin="anonymous">

app/ayanova/src/main.js

@@ -1,5 +1,6 @@
 import "@babel/polyfill";
 import "@fortawesome/fontawesome-free/css/all.css";
+import "typeface-roboto/index.css";
 import Vue from "vue";
 import "./plugins/vuetify";
 import App from "./App.vue";

devdocs/todo.txt

@@ -5,19 +5,8 @@ Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOiIxNTQyNjY5Njc3IiwiZXhwIjoi
 
 ## IMMEDIATE ITEMS
 
-DEVOPS 
-	- Wipe the server, create new at v 18 (or try the upgrade first just for kicks)
-		- Upgrade in place process: https://www.digitalocean.com/community/tutorials/how-to-upgrade-to-ubuntu-18-04
-	- Make devops AyaNova barebones without docker?
-		- Look into pros and cons because ultimately we'll want to run a bunch, maybe on demand, how to do that automatically?
-		- initially probably manuall set up so really not an affect either way as will just need to dedicate a port to each one regardless if dockerized or not
-		- We do want fastest perf though and no aggravation or cross exposure
-	- Dist to devops and test on devices
-		- Need workbox local 
-	
-		- Need roboto font local css and fonts ** ASked on stackoverflow
-			- then redist wwwroot again
 
+	
 
 
 INITIAL TESTING NOTES:
@@ -37,10 +26,14 @@ INITIAL TESTING NOTES:
 		- maybe a vertical menu button instead of the separate delete and edit to save space.
 		- Kind of weird to scroll to the right to edit and you forget which record you are looking at maybe as the name dissappears
 		- Alt background slight gray and white (but not to interfere with selected current or selected row grayness) TTM?!
-
+	- Need workbox local 
-
+	- Need roboto font local css and fonts ** ASked on stackoverflow
-
+			- then redist wwwroot again
-
+		- Make the copyright banner at bottom left aligned, right now it seems weird in small iPhone size when it breaks to two lines (make text smaller?)
+	- Change server api page favicon to look like a SERVER version of the AyaNova logo, not the same one as the client uses
+	- Local roboto font hosting 
+	- Local workbox hosting
+	
 
 
 
@@ -65,25 +58,15 @@ INITIAL TESTING NOTES:
 	- Widget crud component that works with real data
 		- Dirty form check and prevent route leave: https://router.vuejs.org/guide/advanced/navigation-guards.html#in-component-guards
 		- broken rule display 
+
+
+
+
 	
-	- Release an internal test version to the DEVOPS server
-		- Scrap running it in Docker and go bare metal copying config for running .net apps from ayanova.com server?  
-		- Document the release procedure while doing the next step:
-		- Test with all our devices and note what works and what doesn't and adjust accordingly
-		- Test initial shell and dummy input form on all devices including a simple e2e test of some kind to get a start on that aspect
-			- Test as PWA on all devices
 
 
 
 
-UI TODO ITEMS
-	- Make the copyright banner at bottom left aligned, right now it seems weird in small iPhone size when it breaks to two lines (make text smaller?)
-	- Change server api page favicon to look like a SERVER version of the AyaNova logo, not the same one as the client uses
-	- Local roboto font hosting 
-	- Local workbox hosting
-	- Localize welcome to ayanova
-	
-
 - Stage 2 AFTER POSTED TEST ROUND COMPLETED		
 	- Error handling at client (log? display?)
 	- Notification of some kind (bell / toast)				
@@ -129,6 +112,28 @@ UI TODO ITEMS
 	- Customer demo!!
 
 
+
+
+DEVOPS 
+	- Right now all that really matters is being able to test it and I can do that so the rest can be bumped.
+		- Wipe the server, create new at v 18 (or try the upgrade first just for kicks)
+			- Upgrade in place process: https://www.digitalocean.com/community/tutorials/how-to-upgrade-to-ubuntu-18-04
+		- Make devops AyaNova barebones without docker?
+			- Look into pros and cons because ultimately we'll want to run a bunch, maybe on demand, how to do that automatically? (Cadillac problem)
+				- Actually, won't they just be separate droplets?  So really what I want is a very efficient droplet that I can clone?
+				- But then people want to just sign up and start working, not rent a whole server etc, it's up to us where we put the droplets or apps, but they don't want to see that
+				- Several scenarios: 
+					- User signs up and starts working immediately, all through a subdomain, i.e. https://abcelectric.ayanova.com 
+					- User wants to host it themselves on their equipment (nothing for us to do but sell the license)
+					- User wants their own host and domain i.e. https://abcelectric.com
+					- User wants to run it all locally on their own computer, docker image?  Do we really want a windows installer route or...?
+
+			- initially probably manually set up so really not an affect either way as will just need to dedicate a port to each one regardless if dockerized or not
+			- We do want fastest perf though and no aggravation or cross exposure
+
+
+
+
 =-=-=-
 some shit I probably don't need anymore: