Pre-Configuring options BEFORE install

[Convergence]

Greetings All!

We have a specific configuration that we use for all our stores. We want to create new stores with the same configuration of all our previous installs.

Question: Is there a way to PRE-CONFIGURE an install so we do not have to go through the multitude of steps to get our store configured after the install.

Thanks!

[kobra]

Hey Brighton, CO!!

Create a configured install with a custom template to include all layout boxes settings attached to the template and all addon modules. This can be sans any products. You can then use this DB and template name for all other installs - adding products etc and after installed, one can alter the template graphics independantly.

[Convergence]

Hey Brighton, CO!!

Create a configured install with a custom template to include all layout boxes settings attached to the template and all addon modules. This can be sans any products. You can then use this DB and template name for all other installs - adding products etc and after installed, one can alter the template graphics independantly.

Thanks for your reply Kobra -

But you've lost us :) - is there a tutorial or "cheat sheet" to do this?

Side Note: Waiting for the snow out here in Brighton - South Denver was getting snow, Airport was getting snow - just a good steady rain here...

[kobra]

Unfortunately, there is not a tutorial that "directly" addresses this but parts of moving to a new server/host are applicable and the basis for what I have proffered.

Basically, install a development install(call it what you like) of ZenCart with no products or a minimal one or two test items if this assists in configuring the things you need.

As configuration settings are held in the DB and many associated with the active template, you also create a "custom" template and make adjustments to all settings. This same template name will be used across all of your installs.
Note: The name is the same to maintain DB associated settings. The graphics can be fully unique.

Add any 3rd party modules and these can consist of files and DB tables and/or sql changes. Most modules utilize the override system and the files will be placed into appropriate folders named for your template name. Some have core file replacements.

Once this dev install has been configured as you want - tar.gz the complete set of cart files and make a DB copy of same.

Now you have a complete copy of the pre-configured base install to be moved to another domain name/server. Use the steps in the tutorial on moving to relocate these files and DB. Now it is ready for graphics and product.

This assumes your shops all have a unique complement of products.

[Convergence]

Unfortunately, there is not a tutorial that "directly" addresses this but parts of moving to a new server/host are applicable and the basis for what I have proffered.

Basically, install a development install(call it what you like) of ZenCart with no products or a minimal one or two test items if this assists in configuring the things you need.

As configuration settings are held in the DB and many associated with the active template, you also create a "custom" template and make adjustments to all settings. This same template name will be used across all of your installs.
Note: The name is the same to maintain DB associated settings. The graphics can be fully unique.

Add any 3rd party modules and these can consist of files and DB tables and/or sql changes. Most modules utilize the override system and the files will be placed into appropriate folders named for your template name. Some have core file replacements.

Once this dev install has been configured as you want - tar.gz the complete set of cart files and make a DB copy of same.

Now you have a complete copy of the pre-configured base install to be moved to another domain name/server. Use the steps in the tutorial on moving to relocate these files and DB. Now it is ready for graphics and product.

This assumes your shops all have a unique complement of products.

Thanks Kobra - becoming much clearer now.

So moving the "dev install" is pretty much the same thing as creating a shop on a "production domain" and then moving it to it's own / new domain?

[kobra]

Is there a way to PRE-CONFIGURE an install so we do not have to go through the multitude of steps to get our store configured after the install.

So moving the "dev install" is pretty much the same thing as creating a shop on a "production domain" and then moving it to it's own / new domain?

Yes, the dev install becomes your "Pre-configured" install with only a few items that must be altered versus many