# 19/08/21

## 08:30 - 09:30
- Planning out the day
- I need to edit the build.js file to take the binaries from one folder to another.
- then copy the project files into the destination
- Then I need to test the bat file to provide the process.argv in prod.
- So my bat file works with the new arguments being added to the bat.
- I checked by console logging the process.argv.
- Successfully creeated a command line prompt for build.js
- This copies the binaries over to the path destination if the path exists.
-

## 09:30 - 10:30
- I have successfully create the script which copies the binaries to a seperate directory and copies the project into resources.
- Now need to copy over the .env file into the root of the binaries as well as the deploy.bat
-

## 10:30 - 11:30
- currently still trying to copy over .env and deploy.bat
- finally able to copy the deploy and the .env file to the main part of the directory.
- now just testing.
- A folder of your choice must be present.
- The process I have come up with is:
- run the build file
- npm install in resources/app
- npm build in resources/app
- run build.bat in root of new directory
- all seems to be working now!
- script done, cmd file done.
- what next?
-

## 11:30 - 12:00
- prep for huddle
- I think I can show the full setup for the manually distribution.

## 12:00 - 12:50
- huddle
- These files are extra:
- gNLMPC.cmd
- gNLMPC.config.json
- create an es folder
- the folder can be bin for now
- when we open the target the above will be in it:
- later on use rust or c to generate a small exe file
- we use a an exe file that has all of our config
- change the icon programmatically
- is there any way to protect the asar.
- encryption for asar.

## 12:55 - 13:55
- lunch

## 14:00 - 15:00
- currently working on the asar conversion

## 15:00 - 16:00
- so I managed to convert the package but the asar file is not finding the workbench for some reason.
- I am going to try and install @gdap/ workbench
- Even with the install it doesn't work.
- I am going to try the asar without the npm and build packages
- Ok good gives the same error if I had not installed the npm packages when not using asar.
- I am just trying a clean npm install followed by a build
- I may have to put a bunch of console.logs to find out where the issue is coming from.
-

## 16:00 - 16:30
- It seems that the asar can't find the main part of the application at the moment.
-
-