@amurray is spot on with this suggestion.
I do the same thing to set up all my Joomla installations. I start with the stock installation then add my regularly used extensions- like JCE, Akeeba Backup and Admin Tools, RSForms, etc. - and run a backup. The resulting .jpa file, along with Kickstart from Akeeba, make for an easy installation “package.”
Akeeba even makes reference to this in their documentation:
“ Template sites. Web professionals have used Akeeba Backup in order to create "template sites". This means that you can build a site on a local server, install every component you usually do on most clients' sites and back it up. You now have a canned site that can serve as a great template for future clients. Using the same method you can have a snapshot of all the sites you have built for your clients, without the need to have them installed on your local server.”
I do the same thing to set up all my Joomla installations. I start with the stock installation then add my regularly used extensions- like JCE, Akeeba Backup and Admin Tools, RSForms, etc. - and run a backup. The resulting .jpa file, along with Kickstart from Akeeba, make for an easy installation “package.”
Akeeba even makes reference to this in their documentation:
“ Template sites. Web professionals have used Akeeba Backup in order to create "template sites". This means that you can build a site on a local server, install every component you usually do on most clients' sites and back it up. You now have a canned site that can serve as a great template for future clients. Using the same method you can have a snapshot of all the sites you have built for your clients, without the need to have them installed on your local server.”
Statistics: Posted by gsmela — Sat Dec 21, 2024 1:59 pm