=== natefinch-afk is now known as natefinch === zz_CyberJacob is now known as CyberJacob [10:42] aisrael: jose: marcoceppi: https://code.launchpad.net/~daniel-thewatkins/charms/trusty/ubuntu-repository-cache/add-rsync-timeout/+merge/261424 is approved and the dependent changes have been merged; could it get merged? [14:01] Odd_Bloke: merged! [14:01] aisrael: Thanks! === natefinch is now known as natefinch-afk === lathiat_ is now known as lathiat [14:44] * jose scratches head [14:45] I'll get to the review queue... once I finish organizing this conference (for today at least). been some busy weeks [15:32] I'm sorry I couldn't make it yesterday to the office hours. [15:33] I have a question. As this quassel machine is not my pet, I might lose it anytime. And if I lose it, I can redeploy it easily but the database with the channels I want to log in is lost, and it's a pain to rejoin all the channels. [15:33] what are my options for a back up? a snapshot? [15:33] elopio: by default it deploys w/ a sqlite database, thats a great idea for an action. to compress and stage that database for a backup. [15:34] lazyPower: and then the charm would have to be extended to receive a sqlite on the config, right? [15:34] i forget how the charm is setup, i thought that was default behavior. did you relate it w/ MySQL? [15:37] elopio: nah, its only sqlite. [15:37] elopio: and in order to restore from any backup, it should be a simple copy in place update. Treat the database as an atomic thing [15:37] lazyPower: quassel supports postgresql, which I wanted to use. But the charm doesn't support it yet. [15:37] uncompress backup, copy to location, recycle the qaussel-core service. [19:17] http://paste.ubuntu.com/11975185/ [19:18] anyone can help ? [19:28] ejat: i'm going to need a little more context, have you bootstrapped a juju environment? [19:30] ejat: also which version of juju are you using? juju --version === natefinch-afk is now known as natefinch [20:34] Hello. Would anyone be able to tell me "when" during deployment that a /etc/cron.d/ file be created? I am finding that adding cron entries into charm code seems to make the index.php become a blank white page (when accessed from browser). If I manually create a cron job after complete installation, it seems to be ok. Thanks.