Hi all,
I'm interested in keeping a repository of our site so we can track changes more conveniently. I have some idea of what I want to do but I'm still kind of a cs cart noob. What are some approaches that have been working for you?
Hi all,
I'm interested in keeping a repository of our site so we can track changes more conveniently. I have some idea of what I want to do but I'm still kind of a cs cart noob. What are some approaches that have been working for you?
Hi all,
I'm interested in keeping a repository of our site so we can track changes more conveniently. I have some idea of what I want to do but I'm still kind of a cs cart noob. What are some approaches that have been working for you?
Hi,
Our team is at your service. Feel free to contact us.
Best regards, Alt-team.
Hello sitmgreg,
You can also contact support@webkul.com .
We will surely find best way to implement your idea.
Thank you-
Himanshu
Just ask your hosting administrator to install and configure Git on your server. Then learn main commands, it is not quite complex
Ok I should be more specific here. I am fairly experienced with git. What I am asking is like, what does a "good" cscart .gitignore look like in your opinion.
So for example, is there anything in var/ you feel is worth having checked, or is it simply adequate to have app/ alone under version control.
The only thing I can think of that you might want to check in /var/ is the themes_repository. It's only used for restoring default templates so it's basically your call.
Cool, thanks, sounds good.
I would preserve:
robots.txt .htaccess config.local.php init.php config.php js local.conf.php php.ini app design var/themes_repository var/files var/downloads var/langs var/snapshots var/upgrade
Note that some of the var files may not exist on your site as well as local_conf.php.