Changes between Version 2 and Version 3 of projects/crm_review/report


Ignore:
Timestamp:
Jun 25, 2008, 4:46:45 PM (17 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • projects/crm_review/report

    v2 v3  
     1[[PageOutline]]
    12= MFPL/PTP CRM Review project Report =
    23
     
    1718All in all - a very easy installation.
    1819
     20=== vtiger ===
     21
     22My first decision is whether I want the [http://www.vtiger.com/index.php?option=com_content&task=view&id=30&Itemid=57 binary or source]. Hm. I'm going with source because I'd rather not execute a binary that I know nothing about. The version I'm using is 5.0.4.
     23
     24vtiger makes the sugarcrm requirement of 40M seem downright negligible. The biggy is a requirement of php5 - many commercial hosting provider are still running PHP4. In addition, vtiger [http://wiki.vtiger.com/index.php/Vtiger_CRM_5.0.4_-_Installation_Manual_for_Linux#System_Requirements wants]:
     25
     26Directives that are enabled by default in debian already - no change needed:
     27
     28{{{
     29safe_mode = Off
     30display_errors = On
     31file_uploads = On
     32register_globals = Off
     33log_errors = Off
     34short_open_tag= On
     35}}}
     36
     37Directives that need to be changed:
     38
     39{{{
     40max_execution_time = 600 (default on debian: 30)
     41memory_limit  = 64M  (default on debian: 16M)
     42}}}
     43
     44Directives that need to be changed that I don't want to change
     45
     46{{{
     47error_reporting=E_WARNING& ~E_NOTICE (default on debian: E_ALL & ~E_NOTICE)
     48output_buffering = On (default on debian: Off)
     49}}}
     50
     51They want less errors to be reported. Keeping the debian default should be fine.
     52
     53As for output buffering, the comments in the php.ini file says:
     54
     55{{{
     56; Output buffering allows you to send header lines (including cookies) even
     57; after you send body content, at the price of slowing PHP's output layer a
     58; bit.  You can enable output buffering during runtime by calling the output
     59; buffering functions.  You can also enable output buffering for all files by
     60; setting this directive to On.  If you wish to limit the size of the buffer
     61; to a certain size - you can use a maximum number of bytes instead of 'On', as
     62; a value for this directive (e.g., output_buffering=4096).
     63}}}
     64
     65I'm going to try to run vtiger with this turned off and see if it works anyway.