Check Infrastructure word document in moodle. (ask if you can not find)
Pick every recommended software from there and think how we could use those in EpicA
Think about web pages and Mautic software locations and data collected later from GoogleAnalytics or equivalent. Also think about your current work results location and also where Hiens's work should be located and how that data must be stored.
Also consider following: Hien's software could be run by CRON (timed runs, repeating once a week or so) how should data be ingested to system then
Ask preliminary review meeting before opening pull request.
Prepare a document to EpicA... folder under spec folder. Name of it: listOfSoftwareInfraEpicA.md
Check Infrastructure word document in moodle. (ask if you can not find) Pick every recommended software from there and think how we could use those in EpicA Think about web pages and Mautic software locations and data collected later from GoogleAnalytics or equivalent. Also think about your current work results location and also where Hiens's work should be located and how that data must be stored. Also consider following: Hien's software could be run by CRON (timed runs, repeating once a week or so) how should data be ingested to system then Ask preliminary review meeting before opening pull request. Prepare a document to EpicA... folder under spec folder. Name of it: listOfSoftwareInfraEpicA.md