In my latest project I started using Trellis with Bedrock and I’m loving it!
Currently I’m not using Trellis (yet) for automatic deployments, since I don’t have SSH access to my production servers.
One problem I bumped into because of this, is my backup method. In the past I used BackupBuddy with satisfaction. However, since BackupBuddy only backs up files in the Wordpress root (which is the wp folder), the app folder is not included in the backup, which is the most important folder to backup.
I was wundering if someone else has come up with a workaround or uses a different plugin for backing up remote files?
Would love to hear any suggestions!
I already submitted a support ticket to iThemes, but I doubt they will add an option to include a one level higher folder in their backup method.
I think it does support that (because the wp folder is backed up correctly), but it expects that all the uploads, plugins and theme files are also in that subdirectory and not one level higher in the app folder…
Hi there. I’m using Infinitewp and I like it. VaultPress might be great, but it’s really expensive if you need to manage a bunch of websites. So I’m surprised this is being offered as the solution in this thread.
Infinitewp also doesn’t support backing up files outside the wp root folder, which I think is logical when thinking about security. They do advise to create symlinks to the folders you want backed up. To me it sounds like a proper solution.
Still I’d like to fully integrate it into the Capistrano process and I’m not too sure about that. I suspect I need to add it to deploy.rb as a task to run after deploy.
I need symlinks for all custom files:
shared web/app/uploads folder
the web/app folder of the current release
I’ve come up with something like this:
namespace :deploy do
desc 'Place correct symlinks for functional infinitewp backups'
task :symlink_config do
on roles(:app) do
execute 'ln -s /home/username/webapps/website.com/current/web/app /home/username/webapps/website.com/current/web/wp/'
execute 'ln -s /home/username/webapps/website.com/shared/web/app/uploads /home/username/webapps/website.com/current/web/wp/'
end
end
end
after 'deploy:publishing', 'deploy :linked_files'
The most important think I’m missing here – I think – is a way to use variables to construct the paths to the current release folder. It’s also very possible that I totally messed up the whole structure, since I’m not used to coding in Ruby. Any input would be great. Thanks!
Nope unfortunately not, but in retrospect I think BackupBuddy is possibly the worst plugin I ever purchased. I use it on several websites and I get errors all the time, it’s just not reliable. Their new BackupBuddy Stash Live feature even crashed my site (memory overload).
I tried Vaultpress on one of my websites and didn’t have one single error yet, but it is expensive though. If your hosting offers installatron you can make backups of your Wordpress with that.
The only bummer is that UpdraftPlus’ add-ons require their non wordpress.org version…and I personally haven’t worked out a great way of handling premium plugins with Composer.
I’m getting a security check error every time I try to save a setting in updraftplus. Have you run across that? Do I need some sort of special file permissions?
So I’ve asked the support and here is their response:
It looks like we are not able to discover and connect to your site due to the file structure - For example, your xmlrpc.php file (which is integral for Jetpack to work properly or for us to connect to your site to provide our services) shows up as missing due to this:
I would recommend reaching out to the developers behind Bedrock to see if they know common ways to connect Jetpack and VaultPress service through a Bedrock setup (I checked in our internal documentation and conversations and only saw one other instance of Bedrock in place, but we were not complete on finding out a solution ourselves).
Once you’ve spoken with the Bedrock folks, please let me know if there’s anything I can do from this side to help!
VaultPress pointed you to us? Tell VaultPress that they apparently don’t support WordPress installed in a subdirectory and they should figure out how to do so. The finger can’t be pointed at Bedrock at the end of the day.
I want to mark this as the solution but VaultPress isn’t necessarily the primary topic of this thread so I’m just gonna say thanks for posting that haha!
