Changeset 6258
- Timestamp:
- 06/01/15 14:16:23 (9 years ago)
- Location:
- vlo/trunk
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
vlo/trunk/DEPLOY-README.txt
r6102 r6258 204 204 ./vlo_solr_importer.sh 205 205 206 script in the vlo/bin directory. Messages are logged to the console. Because 207 meta data is not static, it is recommended to run the importer a couple of 208 times a week. Please note that, given the current (04.2014) set of data, a 209 run typically takes between two and four hours. 206 script in the vlo/bin directory. Messages are logged to the a log file. 207 Because meta data is not static, it is recommended to run the importer a 208 couple of times a week. Please note that, given the current (04.2014) set of 209 data, a run typically takes between two and four hours. 210 211 More information about running the importer can be found in the README.txt 212 file. 213 -
vlo/trunk/README.txt
r6101 r6258 1 = Table of Contents = 2 - What is the VLO? 3 - What should I read? 4 - Setting up 5 - Preparing for release 6 - Using the VLO 7 - Running an import 8 1 9 = What is the VLO? = 2 10 … … 26 34 Some general development notes. 27 35 28 = = Setting up ==36 = Setting up = 29 37 30 38 Follow the instructions in DEPLOY-README to set up a development environment. … … 82 90 files. 83 91 92 = Using the VLO = 93 94 After a successful deployment and configuration, you should be able to browse to 95 the VLO web app and browse the imported records. 96 97 If the VLO is empty, you will need to run an import first. 98 99 == Running an import == 100 101 To run an import, go the 'bin' child directory of the VLO application directory 102 and run 103 104 ./vlo_solr_importer.sh 105 106 as the appropriate user (e.g. 'vlouser'). 107 108 It's advisable to run this in a detached background process (for example using 109 "screen") because an import can take quite a long time depending on the amount 110 of records to be imported. 111 112 Some progress information is logged to a file 'log/vlo-importer.log'. It gets 113 rotated automatically by the import process.
Note: See TracChangeset
for help on using the changeset viewer.