sintonia/python_apps
Lucas Bickel e28ad471f9 Rewrite config from /etc/airtime-saas to plain /etc/airtime
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.
2017-03-03 15:57:41 +01:00
..
airtime-celery Rewrite config from /etc/airtime-saas to plain /etc/airtime 2017-03-03 15:57:41 +01:00
airtime_analyzer Rewrite config from /etc/airtime-saas to plain /etc/airtime 2017-03-03 15:57:41 +01:00
api_clients Merge branch 'saas-dev' into saas-installer-albert 2015-06-02 15:40:57 -04:00
icecast2 Reverted commit mistakenly changing file modifiers to 755 2015-01-14 20:45:03 -05:00
media-monitor Run build from installer; add upstart files and templating back in 2015-06-30 12:16:31 -04:00
pypo Respawn liquidsoap and pypo indefinitely if they fail to launch. Throttled it though. 2015-12-04 15:56:06 -05:00
std_err_override CC-5990, CC-5991 - Python cleanup, removed need for /usr/lib/airtime 2015-01-27 18:43:36 -05:00