10 replies to this topic

[RMD27]

This has probably been covered before but I couldn't find anything.

I want to create an OSC install that I can use over and over again for new shops.

So I want OSC 2.3 but with certain contributions pre installed.

I can install 2.3 and I can add the contributions.

What I don't know how to do it to save this install with the contributions already installed so I can use it again on other shops.

If you know what I mean?

How do I create a zip file of 2.3 with the contributions I like already installed?

Is it easy to do?

It needs to be otherwise I won't be able to do it.

If someone has a link or info they would like to share?

[multimixer]

RMD27, on 26 March 2012 - 02:37 PM, said:

I want to create an OSC install that I can use over and over again for new shops.
[...]
Is it easy to do?

Good news: I would say it is easy

2 things to do
- Make a copy of all files
- Take a backup of the database

Store everything somewhere on your computer

[Juto]

Hi George, and then...  I.e how do you install it? Is it as easy as replacing the vanilla systems files and raw DB? Or, do the install.php have some special requirements wich would make unusable?

Sara

By the way I have had a look at your mini template system, marvelous!

[RMD27]

@Juto - Yeah, that template system looks amazing

@multimixer, cc:Juto - I think I get you. Make a backup like normal. And just restore it but to a new domain? Surely it cant be that easy?

Ill probably have to create the database manually first or will everything take care of itself when I click the restore button?????

[multimixer]

During installation, there are 2 things happening
- Writing into the 2 configuration files
- import of the stock database

This 2 things you will need to do manually when restoring a backed up store to a new server, that mean
- Manually change the 2 configuration files
- Manually import the new database

Additional to this, you will need to take care of the .htaccess file in folder /admin/, so it would be better not to have any htaccess added to the "base" store you have (I guess you will develop this locally)

Other possible issues field, a htaccess files added by SEO urls, you will need to change the rewrite base there

[RMD27]

ill give it shot and share with the community how it goes for an amateur.

im in the process of restoring a back up now.

im doing an ftp upload of the back up files now. (they are too big to do it from my computer)

then im going to use the webdisk as the source for the restore function.

fingers crossed there will be you and others about ready to lend a hand when things go pear shaped.....

[Juto]

Thanks George, I have read in the bug report something about UTF-8, poste by Gergely. I haven't looked deeper into it, since I don't have any issues with it. It will be interesting to see Ricardo's result.

Sara

[RMD27]

Okay,

I knew things would go pear shaped, luckily I did not have to wait too long.

The webdisk is refusing to co-operate and the browser locks up in sympathy.

As per usual in these situations I am getting my excellent hosting company involved.

I think the size of the site is outside the bounds of what the cpanel can deal with. I think is has to be done with WHM which is foreign territory for me.

I will let you know what they say.

@Juto - for what it's worth, I would try the normal cpanel restore function (if your site is not too big) and do the changes multimixer suggested. Should probably work out. Multimixer's advice is usually top drawer.

[multimixer]

The only reason for a website to be huge (from the files side) is a huge images folder, so you can either skip this, or download it separately

In any case, I wonder, how it comes that the store is on the server but you don't have a copy of it locally?

[RMD27]

Okay I spoke to them. They gave me a detailed explanation, none of which I understood

Something to do with user names and passwords having to be changed before the database is created (I think) and a load of other stuff.

I think they were saying if the user name and password is the same on all three shops then changes to one will effect all the others (Im on a VPS). The database user names and password have to be different.

About not having a backup locally. I do. Except it does not work with the cpanel restore wizard because its so big.

Its a gig compressed. The image folder? You are one hundred percent correct, it is a third of the size. I have a temp folder from Easy Populate which is another third. I did not realise.

Temp folder emptied.

The "home" back up option in cpanel > back up/restore wizard. I can make my own "home" back up file by simply selecting the files I want from file manager, right clicking compress and job done? This is how I make a back up of the "home" directory while excluding the images? Is that what you meant?

If so, maybe it will work like you say, ie without images.

I am still none the wiser about the whole transfer process cause nothing I have done has worked. It looks like the restore function in cpanel is not designed to be transferring files from one domain to another?

I am assuming the hosts have software that allows them to make mirrors of sites easily?

Anyway, they say it will be done tomorrow and then I have the other things you highlighted to sort out.

About the .htaccess.

You say "you will need to take care of the .htaccess file in folder /admin/, so it would be better not to have any htaccess added to the "base" store you have (I guess you will develop this locally)"

The only changes needed are to change the references to the old domain right??

[RMD27]

To finish up.

In my case at least, mirroring the store caused more problems than it solved so I went with a fresh install of 2.3

With regards to setting up a version of 2.3 with the required contributions already installed. I suppose the easiest way to do this would be to download 2.3 from the osC site.

Extract it.

Make the file changes off line before you install it.

The sql changes would still need to be done manually after you install osC but that is the easiest way I can see of making a loaded install of 2.3

I stand to be corrected.