regarding editors - I would recommend notepad++
Ray
-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Madonius
Gesendet: Dienstag, 17. September 2013 15:49
An: dev-general@lists.oxidforge.org
Betreff: [
Hi Roman, hi Madonius
you forgot to mention that you can have your own smarty-plugins inside the
"core/smarty/plugins"-folder. Having a custom loader is another topic too ;)
Having a whitelist can be a solution, but may be not the best (imagine the
situation you forgot "that one" location and y
hey guys,
if you use this GIT repo (e. g. with different branches dev/stage/master) for
deployment on all systems, you have to commit all files.
but some should be ignored: like /tmp, /log, /export and all config-files.
you can make automatic or manual commits on e. g. live system (article image
Hi Madonius,
i think you should ignore everything except the following directories:
- modules
- out/your_theme
because you should not change anything inside the core.
I would suggest you to create a checkout for every module and every
theme you are working on. Do not commit the OXID-scripts to
Dear fellow devs,
I am developing for our new oxid webshop and I am using git.
Everything works fine as it is a repository just for me. But now other
developers are to be included in the proces, are there common recipies
on terms of .gitignore, comitting policy etc.?
What are your experienc
