Team minutes Build - nordquip/sousms GitHub Wiki

• ReInitialize the database using src/database/sousmsInit.sql (Done, last init 11/19)
• Setup feed engine in build script (Works, appears to pull/save datas) -- delay 2 to let feed stop (Done, delay is 10 due to hanging processes)
• Add calls to trade engine looper start and stop script (Done)
• Test that $_SERVER['DOCUMENT_ROOT']/service/ConfigFile will find the config file when php called from bash shell when you run ParseFeedInsertData. (Jeff has adjusted his script, no longer needed)
• If successful, create issue for Jeff fix DBConn to use this technique. (Not Needed)
• Finish Version info file creation routine, so file is 'correctly' written. Note, we are now planning to write the version into a txt file and open this file and echo its contents with a php that can be included by either the web or mobile teams to display the version number. (Done)
• Enter issue for web team to read this file (Done)
• Clean up what gets copied to /var/www/html
  • Mobile team -- copy only /mobile/html
  • Trade engine -- don't copy anything in /te
  • determine what other repository directories are not needed

• Nick is building up a virtual CentOS box for testing.

• rework sousmsInit -- add note that all storedProc sourcing done from shared/DeclareSgtoreProcs
• Need to pull secret key from config file
• Need sp_getUserIDFor(token)

• Create /var/git/sousmsconfig file containing xml holding: secret key, mysql user name, mysql password, mysql database name (Done)
• Publish xml tag names for each data in doc/build/configFileFormat.md (Done)
• Open an issue that the sousmsConfig is ready for usage by other teams. (Done: three issues total.)
• Initialized the database after script is debugged (Cole has closed his issue). (Done)
• Add run of src/shared/sousmsDeclareStoredProcs.sql to hourly build (Done, runs through cron; not included in build due to password within execution string.)

• run src/database/sousmsInit.sql one time on the server to initialize the db -- DONE: failed to run
• Add run of src/shared/sousmsDeclareStoredProcs.sql to hourly build -- NOT DONE:
• Set read config file and use to set environment vars in script (export) -- NOT DONE: Couldn't get environment variables visible to php pages served by apache on the server
• Determine how to make environment variables available to php pages -- DONE: Works on our local vm, but not on server
• In build script, read config file and set appropriate environment variables, so they are available to both: -- DONE on Ryan's VM -- see above.
  • programs the build script starts,
  • php pages
• add java guide to build instructions -- DONE

• I couldn't resist. I added SOUSMSSecretKey to windows system environment variables, logged out and back in, started apache, and my new variable showed up when I pointed my browswer at t.php, which was executing phpinfo(). I think all we have to do is add a small script to /etc/profile.d that sets SOUSMS from what is in the config file then one-time edit /etc/profile to source in this new script.

• Jeremy: Add link for CentOS to instructions (DONE)
• install Java on server (DONE: Installed OpenJDK 1.7.0.9; works; need to test compilation -- Have guide, will follow.)
• Create config file to hold passwords and Jeff's key on the server DONE:(File created, needs formatting and defined usage. Lives alongside the build and boot scripts on disk.)
• Modify build script to use this config file -- NOT DONE -- ?how are we going to pass them: 1. export variables and have build script call, 2. Set Apache variables, so php can read them
• database backup - test: (NOT DONE, but found straightforward tutorial on MySQL dump and will test.)
  • make small DB,
  • copying mysql internal files out,
  • dropping DB,
  • copy mysql files back in.
• Use this experience to decide on copying mysql internal files or use SQL to create backup tables (Simply copying the db files will not work, according to several sites. SQL commands not complicated, just MySQL dump to a file.)
• implement a first draft of the technique you decide on (Not Yet Done)
• Jeremy: use build script to build your product on your CentOS server -- DONE!

• Outstanding security team fork, and dismissal of pull request? -- DONE - dismissed
• Creating a web folder for mobile team -- can do... do we? -- DONE /var/www/htmlmobile/html
• Modifying build script to make log entries, add branching & logic. -- Yes, can do

• Modify Jeff's php example to read the secret key out of the config file

• Implement first draft of cron job that starts a 'bootBuild' bash script, which pulls the repository then calls the build-team doBuild bash script (see below) -- DONE -- running once an hour
• Add the bootBuild bash script to the repository as a build-team src file -- DONE
• Create doBuild bash script to do the actions shown in '121018 Notes' section below -- DONE
• Add doBuild bash script to the repository as a build-team src file -- DONE
• Jeremy - On own VM, open port 80 and port forward the port 80 traffic to your VM machine, so you can access your web site from another machine. (DONE)
• Jeremy - Create md file containing procedure for building the server -- start from state it was in when given to us by IT (DONE) -- yeah
• install Java on server -- NOT DONE - 1.7 is difficult to put on.

• Create PHP file that can call the feed and successfully retrieve xml
• Test a DB backup strategy

• Jeremy - Use Ryan's instructions to duplicate the server on your VM -- NOT QUITE DONE: Needs port 80 opened and needs a IP address for the VM, so it can receive and respond to http requests
• Jeremy - Create md file containing procedure for building the server -- start from state it was in when given to us by IT -- DONE: have the doc, but not yet in the repository
• Jeremy - put this file in the repository -- NOT DONE:
• Ryan - Continue to police the repository and help groups that need it. -- DONE: helped mobile team
• Rewrite git instructions for how individual contributors update their team fork repository -- NOT DONE
• Implement first draft of cron job, which will pull the repository with xml version number -- NOT DONE
• add www folder to nordquip/sousms/src -- DONE.

• doBuild (bash script) should: produce version number file, shutdown services, rename existing production directories, mv temp directories to production, restart services. I guess the 'restart services' step will be our smoke test for now. If the services restart successfully, we have passed the smoke test.
• discussion on how to backup the database. Might be able to copy the internal files, but we might look for best known methods (BKMs) on the web. This is really a DB group task, but if we have time, we can help.

• Publish instructions for how to push a team fork to SOUSMS (Done)
• Install CentOS on your VM (Done)
• Do short search for easiest LAMP stack (Done: Easiest to simply install manually through package manager.)
• Try to install lamp stack iso on CentOS on own VM (Done: Worked like a charm)
• Install lamp stack on build machine (Done)

Stretch:

• Install Git on server (Done)
• start on automation cron job for pulling changes to the build machine (Not Done: Got bored of the server and moved to other problems. Not an urgent task.)

Notes: The cron job will need to extract some identifier (possibly time stamp) from git as it pulls the copy of the repository and insert this identifier onto the home page, so groups have a way to identify which version caused a particular behavior.