I wish everyone a pleasant new 2015!
May your business flourish, your apps find new users and your customer forget the number of your technical hotline.
Besides, if you should ever happen to work with 1C-Bitrix framework here are some hints how to befriend it with git. If you just try to plain start developing a Bitrix app under git you may encounter few uncomfortable things – since Bitrix is huge (more than 18000 files) ever commit will take long. In most cases I received plain errors instead of pleasant working.
So here what you should do:
First, add this to your local git config
git config --local pack.windowmemory=100m git config --local pack.sizelimit=100m git config --local pack.threads=1
You may want to play around with the numbers, just keep in mind following:
Larger window sizes may allow your system to process a smaller number of large pack files more quickly. Smaller window sizes will negatively affect performance due to increased calls to the operating system’s memory manager, but may improve performance when accessing a large number of large pack files.
So now which files to exclude from bitrix using rather .gitignore or /.git/info/exclude? Of course I can’t tell you where to put your development files, but it is a good practice not to touch those:
bitrix/backup/ bitrix/admin/ bitrix/cache/ bitrix/components/bitrix/ bitrix/fonts/ bitrix/gadgets/ bitrix/image_uploader/ bitrix/images/ bitrix/panel/ bitrix/sounds/ bitrix/themes/ bitrix/tmp/ bitrix/tools/ bitrix/updates/ bitrix/wizards/ bitrix/managed_cache/ upload
Meaning ignoring them is generally a good idea. This will save you a lot of time! Happy coding. (For the record – we’re using GitLab instead of GitHub for reasons of security, however commands are just the same for both of them)
Next book sneak peak
The next one, “The Software Development Edge” by Joe Marasco is finally done. Since I’m continuing my more “scientific” approach on book summarizations this time it turned out to be really extensive. I guess it will take a while to write everything important down.
[readolog_blockquote ]One of the main reasons for Joe being able to deliver software in time was his effort to understand every detail of development, every problem occuring, thus, leading to knowledge where you can make right decisions for the whole project movement. This effort is not based upon some kind of magic, but simply upon investing a lot of time in talking with developers.[/readolog_blockquote]