Pre-Configuring options BEFORE install

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!

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.

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.

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...

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.

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.

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?

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

Great - will slot some time next week to give it a try...

Thanks for your help!

I do not know your details on the shops??

But operating many shops, order fufillment, tracking, accounting, etc. can become an ominus task.

There is a Multi-site 3rd Party module that might be of interest where by you operate multiple shops - served from one Database.

The directions are sparse to none but others have has success and this might be of interest to you

kobra:

I do not know your details on the shops??

But operating many shops, order fufillment, tracking, accounting, etc. can become an ominus task.

There is a Multi-site 3rd Party module that might be of interest where by you operate multiple shops - served from one Database.

The directions are sparse to none but others have has success and this might be of interest to you

We have considered running out of one database but had concerns about the database becoming too large, slower response times (maybe v2.0 will help with that). Also, not sure if there would be an issue with creating sitemaps larger than 50K products, db integrity (keeping it easily optimized, etc.) We also like the idea that we can move a shop easily to another server if the need arises...

But always interested in hearing options for efficiency - thanks!

BTW, how are you on creating cron jobs for Zen?

how are you on creating cron jobs for Zen?
Actually, ZenCart does not have cron capability, this is done at the linux level BUT can be for some shell script that acts upon ZenCart items.

What action is it you desire to be automated?

kobra:

I do not know your details on the shops??

But operating many shops, order fufillment, tracking, accounting, etc. can become an ominus task.

There is a Multi-site 3rd Party module that might be of interest where by you operate multiple shops - served from one Database.

The directions are sparse to none but others have has success and this might be of interest to you

kobra:

Actually, ZenCart does not have cron capability, this is done at the linux level BUT can be for some shell script that acts upon ZenCart items.

What action is it you desire to be automated?

In Store Manager (admin/store_manager.php) We'd like to set up a cron to:

1. "Empty Admin Activity Log table from the database" (.../admin/store_manager.php?action=clean_admin_activity_log)
2. "Optimize Database to remove wasted space from deleted records" (.../admin/store_manager.php?action=optimize_db)

Also, we have Easy Populate 1.2.5.4 installed - We want to:

1. Create Model/Price/Qty tab-delimited .txt file in temp dir (.../admin/easypopulate.php?download=tempfile&dltype=priceqty) - We'll then use a script to retrieve the file automatically from our temp folder, make our pricing changes, and then have a script send it back to the temp folder.
2. After #1 is done, we want the same text file imported back into the database (Import from Temp Dir (temp/) - Insert into db).

This will allow us to download the Model/Price/Qty tab-delimited .txt file, say on Monday, giving plenty of time to make our changes before having the file automatically uploaded say on Wednesday.

Thinking the upload portion may require something extra as EP creates a differently named .txt file with each download to the temp directory - so at a loss as how that would work - hmmmm.

Even considered testing macros to do this.

:)

Thanks for any suggestions you may have on this as well.

OK, I am "anal" about this but I did not see where you are making a DB backup???

I would highly suggest that you make DB backups BEFORE messing with anything in the DB automatically or manually.

kobra:

OK, I am "anal" about this but I did not see where you are making a DB backup???

I would highly suggest that you make DB backups BEFORE messing with anything in the DB automatically or manually.

D'oh - yes we backup the databases manually - another cron job is needed for that as well. That's on top of our dedicated servers retaining daily, weekly, monthly backups :)

For the download issues in EP I do not see any integrity issues and one would extract the php that excecutes this into another php file and then cron the excecution of this file...If you use cPanel it appends the hashbang otherwise you need to include it.

Yhe upload I see as problematic and troublesome that could lead to data integrity issues unless the shop is placed into maintenance mode before the upload and might suggest that one do this manually anyway.

As you have root access can you determine if you have mutt installed?
At the cmd line logged in as root enter

$ rpm -qa | grep mutt

If so I have a DB backup routine that can be cron'd
email me through the profile details here