| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | big reorg: prepare for generalization | Pavel Raiskup | 2014-10-22 | 1 | -5/+0 |
| | | | | | | | | | | | | | Try to split into three separate components -> controller, tester, and 'tasks' (postgresql-tasks in our case). The controller component is the main part which is able to run the task remotely. Tester is more-like library for 'tasks' component (should be reusable on the raw git level). * controller: Almost separated component. * postgresql-tasks: Likewise. * tester: Likewise. | ||||
| * | gen-data: remote_generate added | Pavel Raiskup | 2014-10-17 | 1 | -0/+5 |
| Allow automatized generating of data structures on remote host. Run like ./remote_generate IP_ADDRESS. * gen-data/dist/dist: New file. Wrapper around tar to package important files for data generation. * gen-data/dist/dist.list: Include list for ^. * gen-data/dist/dist.exclude: Exclude list for ^. * gen-data/prep: Remote script to prepare everything for successful ./generate run. * gen-data/remote_generate: Wrapper running all the above. | |||||
