Is there a reason no to backup, say, /etc, /home, /srv and /var/www?

Maciej
28 maj 2014 18:38 "Brice Burgess" <briceb...@gmail.com> napisaƂ(a):

> On Wednesday, May 28, 2014 10:46:52 AM UTC-5, Michael DeHaan wrote:
>>
>>
>> Just put it in the configuration file for the backup tool/script.  No
>> need to sprinkle this throughout the playbook IMHO.
>>
>
>
>
> My backup role ensures the backup tools and remote storage points (via the
> s3ql service role). It then registers backup tasks with cron, one of which
> is meant to backup sites. The site backup script executes rsync, passing a
> list of site files/paths to backup via the --files-from argument. This list
> is contained in a file "rsync_sites.inc", and a variable named
> `backup_rsync_sites_file` in the backup role points to it.
>
> When sites are applied to the server, and if backups are enabled for the
> site via the SITE_ENABLE_BACKUP flag, then lines are added to the
> `backup_rsync_sites_file`. The lines added can be passed explicitly, or are
> inferred by the site type (e.g. if a wordpress site, then .htaccess,
> wp-config.php, and wp-content/uploads are backed up).
>
> Thus my role that applies sites needs to know the
> `backup_rsync_sites_file` variable, and that's defined in the backup role.
> Similarly, it also needs to know where to store SSL certificates (if
> flagged as an SSL site), and this path is stored as `httpd_ssl_dir` in the
> httpd role. And so the roles are intralinked -- and I'm thiking about using
> include_vars  versus including the backup role as a dependency to glean
> these variables.
>
> I'm sorry that I mentioned "ansible convention" in the OP. I meant that
> role dependencies are a convention, and that my skip_tasks hack was
> garbage, and wanted to discuss if include_vars for this was OK.
>
> ~ Brice
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/8669a164-7cf1-4477-9f4f-bed0839d3c0f%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/8669a164-7cf1-4477-9f4f-bed0839d3c0f%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAEnKK1yjm%3DYiSTroAuBc0nuHaiXcF6Of3poEBet9vwNfoQOXPw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to