Changes between Version 14 and Version 15 of UnifiedLogger


Ignore:
Timestamp:
09/01/2022 01:33:30 PM (4 years ago)
Author:
jdalbey
Comment:

Update Packaging section

Legend:

Unmodified
Added
Removed
Modified

  • UnifiedLogger

    v14 v15  
    3030ActivityLogSummaryFilename = data_summary.json 
    3131}}} 
    32 The `UnifiedLogPath` option is to specify the path to the folder in which the `CADcomments.log` input file exists, and the output CSV file is to be created.  ''Perhaps this isn't necessary; I can't think of a situation where this would change.''  Similarly, the `ActivityLogPath` specifies the path to the folder in which the Activity Log ("data.json") file exists. (This is "activitylog" on production system.)   When deployed to the web server, this path will be different than when testing on a local server.  The `Files` section specifies the filenames of the activity log files, as they are produced by Neil's Activity Log. 
     32The `UnifiedLogPath` option is to specify the path to the folder in which the `CADcomments.log` input file exists, and the output CSV file is to be created.  ''Perhaps this isn't necessary; I can't think of a situation where this would change.''  Similarly, the `ActivityLogPath` specifies the path to the folder in which the Activity Log ("data.json") file exists. (This is "activitylog" on production system.)   When deployed to the web server, this path will be different than when testing on a local server.  The `Files` section specifies the filenames of the activity log files, as they are produced by Neil's Activity Log. 
    3333 
    3434Optionally, `application_properties.cfg` can be placed in `config` folder.  For example, 
    … …  
    4747 
    4848=== Packaging === 
    49 The source code is in the `src/python/unifiedlogger` folder. The `package.sh` script found in that folder should be run to package the source files into a zip file and place it in the `deploy` folder.  (Update 2022.9.1:  `package.sh` is missing.) 
     49The source code is in the `src/python/unifiedlogger` folder.  Use the script in `trunk/bin/mkunifiedloggerzip.sh` to package the source files into a zip file and place it in the `deploy` folder.  
    5050 
    5151=== Testing === 
    … …  
    8686 
    8787=== Deploying on Apache Server === 
    88 Copy `unifiedlogger.zip` and `unifiedlogmonitor.html` to `webapps` folder on `W:` drive.[[BR]] Copy `loggingservice.cfg` and `application_properties.cfg` to `config` folder (at same level as `webapps` folder).[[BR]] Start the application: `python webapps/unifiedlogger.zip` 
     88Copy `unifiedlogger.zip` and `unifiedlogmonitor.html` to `webapps` folder on `W:` drive. 
     89 
     90Modify the entry in `logging_service.cfg` to reflect the location of activity log files on the production webserver, probably: `ActivityLogPath = activitylog` 
     91 
     92Copy `logging_service.cfg` and `application_properties.cfg` to `config` folder (at same level as `webapps` folder).[[BR]] From the webserver home directory, start the application: `python webapps/unifiedlogger.zip` 
    8993 
    9094=== Running as a background service ===