devdocs/todo.txt

@@ -29,6 +29,10 @@ IMMEDIATE ITEMS:
 
 Go through the TOOLS.txt file VUE section and install
 
+Look into / will I need the following bits that work with vue:
+	- Router: https://router.vuejs.org/
+	- VUEX: https://vuex.vuejs.org/
+	- BABEL: https://babeljs.io/
 
 Do some tutorials to get a feel, read all the following 
 	- think about appearance material? bootstrap?, review these options directly supported in vscode/veture:

devdocs/tools.txt

@@ -1,52 +1,4 @@
-MSBUILD reference for csproj file
+## FRONT END DEV TOOLS
-https://docs.microsoft.com/en-us/visualstudio/msbuild/msbuild#BKMK_ProjectFile
-
-
-Quickly generate large files in windows: http://tweaks.com/windows/62755/quickly-generate-large-test-files-in-windows/
-
-Never download another 100mb test file or waste time searching for a large file.  Sometimes you need a large file fast to test data transfers or disk performance. Windows includes a utility that allows you to quickly generate a file of any size instantly. 
-
-Open an administrative level command prompt. 
-
-Run the following command:
-
-fsutil file createnew <file> <size in bytes>
-
-For example, this command will create a 1GB file called 1gb.test on my desktop:
-
-fsutil file createnew c:\users\steve\desktop\1gb.test 1073741824
-
-The key is to input the size of the file in bytes so here are some common file sizes to save you from math:
-
-1 MB = 1048576 bytes
-
-100 MB = 104857600 bytes
-
-1 GB = 1073741824 bytes
-
-10 GB = 10737418240 bytes
-
-100 GB =107374182400 bytes
-
-1 TB = 1099511627776 bytes
-
-10 TB =10995116277760 bytes
-
-=-=-=-=-=-=-=-=-=-=-
-
-
-After a reboot of dev machine the containers are stopped and need to be restarted on reboot with this command:
-docker start dock-pg10 dock-pgadmin
-
-**USE PGADMIN**
-Browse to localhost 5050
-
-Can view the status of all containers with 
-docker ps -a
-
-
-
-## FRONT END
 
 UI FRAMEWORK = VUE.JS
 =-=-=-=-=-=-=-=-=-=
@@ -81,11 +33,28 @@ Not sure how much unit testing I'll be doing as I'm more interested in the end t
 where you don't write the test, just capture the output and that gets made into a test, if it changes or breaks then the test will fail.
 This sounds ideal to me.
 
+E2E TESTING = CYPRESS
+=-=-=-=-=-=-=-=-=-=-=
+Did a quick look, seems to be the best option, there is also Nightwatch but it's older and relies on a lot of tools where cypress is all built in supposedly
 
-## BUNDLING AND MINIFICATION
+LINTER = ESLINT+PRETTIER CONFIG
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
+VSCODE will use prettier to prettify my js, eslint will complain about some of it so using eslint with prettier config means 
+they won't conflict and eslint will focus on errors, not style so much that is handled by prettier
+
+
+
+
+
+(NOT CONFIRMED YET, MAY BE DRIVEN BY VUE CLI TOOLS ANYWAY) ## BUNDLING AND MINIFICATION
 - https://docs.microsoft.com/en-us/aspnet/core/client-side/bundling-and-minification?tabs=visual-studio%2Caspnetcore2x
 - Gulp seems best for me: https://docs.microsoft.com/en-us/aspnet/core/client-side/using-gulp
 
+
+
+
+
+
 ## DEPLOYMENT
 
 ### DEPLOY TO DIGITAL OCEAN TEST SERVER
@@ -230,13 +199,6 @@ ubuntu.16.04-x64  //<--- ends up being the same size as portable linux 64 so not
 - DATA SEEDING: https://github.com/bchavez/Bogus (a port of faker.js)
 
 
-**DEVELOPMENT TOOLS**
-- TASK RUNNER - npm scripts 
-- CODE CHECK (linter) ??
-- TEST unit / integration: Mocha
-- Subversion 
-
-
 ### DOCKER NGINX LETS ENCRYPT CERTBOT
      - https://www.humankode.com/ssl/how-to-set-up-free-ssl-certificates-from-lets-encrypt-using-docker-and-nginx
      - https://github.com/humankode/letsencrypt-docker-nginx/blob/master/src/production/production.conf
@@ -335,4 +297,54 @@ docker run -d \
   Dashboard for Grafana and app.metrics:
   - https://grafana.com/dashboards/2125
 
-  
+  
+  MSBUILD reference for csproj file
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
+https://docs.microsoft.com/en-us/visualstudio/msbuild/msbuild#BKMK_ProjectFile
+
+
+LARGE FILE GENERATION
+=-=-=-=-=-=-=-=-=-=-=
+Quickly generate large files in windows: http://tweaks.com/windows/62755/quickly-generate-large-test-files-in-windows/
+
+Never download another 100mb test file or waste time searching for a large file.  Sometimes you need a large file fast to test data transfers or disk performance. Windows includes a utility that allows you to quickly generate a file of any size instantly. 
+
+Open an administrative level command prompt. 
+
+Run the following command:
+
+fsutil file createnew <file> <size in bytes>
+
+For example, this command will create a 1GB file called 1gb.test on my desktop:
+
+fsutil file createnew c:\users\steve\desktop\1gb.test 1073741824
+
+The key is to input the size of the file in bytes so here are some common file sizes to save you from math:
+
+1 MB = 1048576 bytes
+
+100 MB = 104857600 bytes
+
+1 GB = 1073741824 bytes
+
+10 GB = 10737418240 bytes
+
+100 GB =107374182400 bytes
+
+1 TB = 1099511627776 bytes
+
+10 TB =10995116277760 bytes
+
+=-=-=-=-=-=-=-=-=-=-
+
+DOCKER DEV 
+=-=-=-=-=-=-
+After a reboot of dev machine the containers are stopped and need to be restarted on reboot with this command:
+docker start dock-pg10 dock-pgadmin
+
+**USE PGADMIN**
+Browse to localhost 5050
+
+Can view the status of all containers with 
+docker ps -a
+