Friday, July 30, 2010
   
Text Size
Walkthroughs for Akeeba Backup and JoomlaPack tasks
Walkthroughs

Walkthroughs

This section contains user submitted stories of successful Akeeba Backup and JoomlaPack use and walkthroughs, that is detailed instructions on how to get specific tasks done with JoomlaPack software.

If you have a story to share, don't hesitate to drop us a line on our support forum!


Saturday, 10 July 2010 10:37

Setting up a CRON job for Akeeba Backup in cPanel

Written by Nicholas K. Dionysopoulos

This walkthrough will guide you in successfully creating a CRON job for automating Akeeba Backup Professional in cPanel-powered hosts. It uses the alternate CRON script (altbackup.php) and is courtesy of Alex Walker.

Published in Walkthroughs
Read more...
Monday, 15 February 2010 09:36

How to set up a JoomlaPack 2.3.3+ CRON job using cPanel

Written by Akeeba Backup Team
Most of us are visual creatures and hate reading instructions. Alex has prepared a comprehensive video tutorial on the subject as well!
  1. Enable the Frontend of JoomlaPack
    • Go to Configuration >
    • Click on Frontend
    • Set Enable Front-end backup to Yes
    • Enter Secret word (Secret Key)
    • Click on Save
  2. Go to CRON Scripts Manager in JoomlaPack
  3. Click on CRON Scripts Manager
  4. Click on New or Edit existing CRON job
    • Enter Secret Key (the same secret ‘word’ entered in the Frontend of JoomlaPack)
    • Operation after backup – Leave as Nothing if you do not want the backup to be emailed
    • Enter FTP Host
    • Enter FTP User
    • Enter FTP Password
    • Click on the Test FTP Connection
    • Connection Successful message should appear ! If not review FTP details!
  5. Now COPY the CRON script in the box:
    php /home/yoursitename/public_html/administrator/components/com_joomlapack/assets/scripts/cron1.php
  6. Go to cPanel > Advanced > Cron jobs
  7. Click on Cron jobs
    • In the Command Box Paste the CRON script code from JoomlaPack:
      php /home/sitename/public_html/administrator/components/com_joomlapack/assets/scripts/cron1.php
    • Set the Common Settings to the frequency of the Backup. To initially try the script set it to every 5 minutes. Once you know it is working, you can then go in and change the frequency.
  8. Click on Add New Cron Job
  9. Once the Backup is completed you should receive an email stating:
    X-Powered-By: PHP/5.2.9
    Content-type: text/html
    JoomlaPack JSON CRON Helper
    Done backing up in 84 steps.
    JoomlaPack JSON CRON Helper has finished successfully!
  10. If you want the email to attach the backup file then you must edit the Cron script in JoomlaPack (6). Where it says Operation after backup change to Send to Email address below and enter email address there.

Alex Walker
www.alexwalker.co.uk
February 2010

Published in Walkthroughs
Read more...
Saturday, 28 February 2009 18:37

Move from a Godaddy Website Hosting account to GoDaddy Virtual Dedicated Server Account

Written by Brian Hurley

Submitted by Brian Hurley - www.purplejunction.comIf you are using GoDaddy Website Hosting, you may want to upgrade to the more flexible GoDaddy Virtual Dedicated Server (VDS) service. The following steps are intended to provide guidance to how to use JoomlaPack to simplify the transfer.

  • Prepare a backup of the shared hosting site to be moved using JoomlaPack

  • In the VDS Master cPanel, configure and compile PHP to match the needs of your website applications, e.g. Multi-byte String Handling

  • In the VDS Master cPanel, create a new account (new virtual server) with the associated domain name <vdstargetdomainname>

  • If possible, if you have a xxxx.com domain, get another xxxx.net, xxxx.info of the same name and use that as the domain for the target VDS virtual server so you can keep the other site active while you do the transfer, then you can change the DNS records to point the old domain to the domain of the target VDS virtual server (and you can park the domain on top of the target VDS virtual server using the VDS Master cPanel) the old domain name once the transferred site is up and running

  • In the VDS Master cPanel, ensure the target VDS server's root account <vdsrootuser> has "wheel" authorization to allow su for chown functions

  • On the target VDS virtual server make a .htaccess file with "Options All -Indexes" to turn off directory browsing by anyone while you are doing the install

  • Connect to the target VDS virtual server using SSH and use ftp to transfer the JoomlaPack backup archive to the target VDS virtual server public_html folder from the shared website hosting account

  • Upload kickstart.php to the target VDS virtual server into the public_html folder

  • In the target VDS cPanel, create the Joomla databases and associated database user/password, create any 3rd party databases and associated database users/passwords

  • Open your webbrowser http://<www.vdstargetdomain.xxx>/kickstart.php and restore files and databases per JoomlaPack restore instructions

  • SSH into the target VDS virtual server and “su”.
    • Update the owner and group of the files "chown –Rf <vdsrootuser>:nobody public_html"
    • Update permissions to 775 (or 755 if you apps will take it) using “chmod -R 0775 public_html”
    • Selectively change permissions of folders according to the recommended Joomla security guidelines and as required by any installed Joomla 3rd party extensions
      • If you are using the JSN Imageshow Pro extension, you will need to ensure that WRITABLE (CHMOD 777) {joomla_root_folder}/modules/mod_jsn_imageshow_pro /jsn_imageshow_pro

  • Connect via webserver to the Joomla administrator back-end of the target VDS virtual server :

    • Update hard file paths in configurations of various Joomla extensions such a JoomlaPack and DOCMan

    • For non-Joomla applications, ensure you go to their configuration files (e.g. config.php) to change database name, database login info, root directories

    • Update any Joomla 3rd party extension license files that are linked to IP address

  • Check the target VDS virtual server php.ini configuration to ensure settings for upload_max_filesize match configuration needs for any Joomla 3rd party extensions such as DOCMan, e.g. upload_max_filesize = 8M

  • If you had SSL certificates on the original hosted shared site you will need to revoke the GoDaddy SSL certificate and generate a new one for the Master VDS cPanel.  Also note that if you want to use https on the target VDS virtual server you will need to use a dedicated IP address for that VDS virtual server (rather then a shared IP with multiple hosted domains)

  • In the Master VDS cPanel, remove “wheel” privileges from your target VDS virtual server <vdsrootuser> account

Published in Walkthroughs
Read more...

Go Professional!

Now, is the best time to go Professional!

go_pro_sidebar

Sponsored Links

Support Unavailability

Enhanced Support will experience reduced or no availability during the dates marked in red on the calendar below. If you file a support ticket during this period, we might take longer to get back to you.

Calendar shown in Athens timezone
See the full calendar
Copyright ©2006-2010 Nicholas K. Dionysopoulos / Akeeba Developers. All Legal Rights Reserved.
Joomla! Hosting by Rochen Host.
Unless otherwise stated, our software is availalble under the terms of the GNU General Public License, version 2 or – at your option – any later version.

This project and Akeeba Backup (formerly JoomlaPack) software products are not affiliated with or endorsed by the Joomla! Project. They are not supported or warranted by the Joomla! Project or Open Source Matters. The Joomla! logo is used under a limited license granted by Open Source Matters, the trademark holder in the United States and other countries.

Disclaimer: Web site content is provided on an as-is basis. No claims are made about the accuracy of this content. User submitted content such as third party video tutorials and forum posts is not endorsed by the Akeeba Developers team and doesn't necessarily reflect the views and opinions of the project leadership, any team member in particular, or the team as a whole. The team reserves the right to modify or remove content which is deemed profane, abusive, innapropriate or innacurate from all public areas of this website. Content submitted in private areas of the site, such as the Ticket System or Personal Messages system, is treated as confidential.