e28ad471f9
This is the results of sed -i -e 's|/etc/airtime-saas/|/etc/airtime/|' `grep -irl 'airtime-saas' airtime_mvc/ python_apps/` :P It might need more testing, the airtime-saas part never really made sense, zf1 has environments for that, ie you would create a saas env based on production for instance. I beleive legacy upstream was using this to share configuration between customers (ie. analyser runs only once and writes to a shared S3 bucket). I assume they mount the airtime-saas folder onto individual customers instances with a global config. Like I said, I don't feel that this makes sense since all it does is make hacking at the configs in airtime-saas a bit easier. A serious SaaS operation should be using something like puppet or ansible to achieve this. |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| airtime_analyzer.py | ||
| analyzer.py | ||
| analyzer_pipeline.py | ||
| cloud_storage_uploader.py | ||
| cloud_storage_uploader_libcloud.py | ||
| config_file.py | ||
| cuepoint_analyzer.py | ||
| filemover_analyzer.py | ||
| message_listener.py | ||
| metadata_analyzer.py | ||
| playability_analyzer.py | ||
| replaygain_analyzer.py | ||
| status_reporter.py | ||