diff --git a/src/App.js b/src/App.js
index 1c641d2..6857d2a 100644
--- a/src/App.js
+++ b/src/App.js
@@ -143,6 +143,7 @@ function App() {
This project started as a local Python 2 script when it started, to only automate very specific settings. It later moved to USB drives and eventually to a VM on a network.
@@ -36,6 +38,8 @@ const ConfigAutomation = () => {Creating the release of this software had to be done by running a batch script to create a bundled set of Python files. These files were then uploaded to the VM located in a European distribution center in the Netherlands. This VM is then used to run the software from on a local network on which all configuration laptops were connected to. A WinSCP script would then sync the contents of all VM's in distribution centres located in Singapore, United States and China in 24 hours.
@@ -51,6 +55,8 @@ const ConfigAutomation = () => {The application generated log files with each configuration and then upload these back to the VM after configuration was complete or halted. These logs were sorted under product name and the order number. But quite often, I found it very productive to go to the configuration area and simply talk with the technician to figure out what went wrong. Depending on the severity of the problem, it would get documented in Gitlab issues. On a weekly basis, issues would get assigned among developers.
@@ -65,6 +71,8 @@ const ConfigAutomation = () => {Being a programmer, I was mostly concerned with the software. But it requires hardware to run on. When the software does not work because of differences in the platform the software run on, what is there to do? I eventually started managing around 40 configuration laptops, using Clonezilla to create identical machines.
diff --git a/src/Pages/Software/SoftwareMain.js b/src/Pages/Software/SoftwareMain.js index 820f3e8..802477c 100644 --- a/src/Pages/Software/SoftwareMain.js +++ b/src/Pages/Software/SoftwareMain.js @@ -27,14 +27,16 @@ const SoftwareMain = () => {