Support

Akeeba Backup for Joomla!

#20497 Pushing Changes to Production Server...

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Tuesday, 15 July 2014 15:38 CDT

user84715
EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:

I have a feature request for akeeba joomla....
Push changes from dev server to production server.

Tweak on a mamp server locally. Then in akeeba hit update production server with changes.

Akeeba would use the site scan tool to scan for changes on the dev, then push changes though FTP and SQL.

Obviously there are a lot of othe features that could be easily imagined. Like push a clone to a dev, compair before updating, syncing sites both directional and so on....

But the basic push changes or push the whole site with one or two clicks would be very big!!!

Thanks for the time and consideration, dan!

nicholas
Akeeba Staff
Manager
You can already do that in four different ways:

1. Take a backup, upload it to the new site and restore (obviously, that's what Akeeba Backup was designed to do since day one)

2. Upload to Amazon S3 or a public web location, use Kickstart Professional on the remote server to pull in that backup archive and restore it.

3. Use the Upload to Remote FTP / Upload to Remote SFTP post processing engine to have Akeeba Backup automatically push the backup archive and, optionally, kickstart.php to the remote server when you take a backup. Then you just need to run Kickstart on the remote server and complete the restoration.

4. Use the DirectFTP or DirectSFTP archiver engines to transfer the entire site to the new server. That's something you can also set up using the Site Transfer Wizard. You still need to run the restoration script manually. Counter-intuitively, this is MUCH slowed than the aforementioned three methods and I do not recommend it.

5. BONUS! You can use a CRON job with Akeeba UNiTE on the remote server to automatically restore a backup archive. Combined with method #3 above you can automate the process. Take a backup, it is uploaded to the remote server. A few minutes later the CRON job kicks in and that backup is automatically restored. Once set up all you have to do, from your perspective, is login to the dev site, hit that backup button and wait.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!