Akeeba Backup for Joomla!

Tuesday, 12 July 2022 05:09 CDT

wd5mush

I am currently developing a new site on my own PC using xampp. In the past, when I have done this I use Akeeba Backup and Kickstart to copy the developed site from my PC and install it site on the public hosting server. From that point I do any further tweaking on the public site.

On this occasion I have been asked if it would be possible to upload the partially developed site to the hosting server so that colleagues can review progress to date.

If I were to do this, I would want to take the site down immediately after the review period so that I could continue development on my xampp installation. ( We would not want the development site to be in the public domain any longer than necessary).

I can think of a number of options, but all have potential associated problems. I wonder if you have a suggestion on the most straightforward way of doing this.

Many thanks

Edited by wd5mush on 2022-07-12 05:10 CDT

Tuesday, 12 July 2022 05:16 CDT

tampe125

Hello,

if possible, I'd suggest to create a subdomain with the test site, protect the whole site with password authentication (usually you can do that in your hosting control panel) and let your colleagues review the site.

When you're done, you can tear down everything.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Wednesday, 13 July 2022 12:36 CDT

wd5mush

Thanks Davide,

I sort of get the idea, but not sure how to achieve it.

Presumably I install Joomla on the sub-domain, but wonder what the benefit is as opposed to the root directory Also, when it comes to 'tearing it down' do I need to delete the database as well as the Joomla files, or will they all be overwritten when I next kickstart?

Alan

Thursday, 14 July 2022 02:02 CDT

nicholas

Technically speaking, none of that is necessary. However, for your sanity's sake, here's what we recommend: create a subdomain with its root outside of your main site's web root, a new database and a new database user.

Having the subdomain with its root outside the main site's root means that the .htaccess file of the main site does not interfere with your subdomain. Moreover, all your links will be relative to / instead of a subfolder (like /joomla4) which reduces the probability of a mistake when replacing the main site with this new site.

Having a separate database means you are unlikely to make a mistake which accidentally trashes the main site's database. Moreover, it means that once you are done with the development site you can simply remove the subdomain, database and database user.

According to our experience, spending 5' extra setting up a development site can save hours to weeks of frustration down the line, not to mention the cost of any mistakes which may affect the main site. Think of it as a seatbelt. Takes very little time to set it up, you won't need it in the vast majority of cases but when you do need it it can save your life.

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!

Sunday, 17 July 2022 09:17 CDT

wd5mush

Thanks NIcholas,

I will take your advice. Just had xampp die on me so need to recover from backups anyway.

Alan

Support