Installing SugarCRM: Difference between revisions

Line 9:

# Download SugarCE-5.0.0e.zip (production release) or the later available production release (getting only the application).

# Visit the recommended "Installation" instructions page at http://www.sugarforge.org/content/installation/

# Install SugarCRM according to the instructions. ~~Note:~~ I ~~immediately ran into trouble because~~ the ~~instructions did say~~ to ~~chmod 766 all files~~ that ~~needed~~ to be ~~writable by~~ the ~~web_user~~. ~~This command renders~~ the ~~directories non-executable which manifests in include errors because the web user (www-data) can not see into those directories (~~to ~~find includes)~~. ~~The following snippet is a fix:~~

# Install SugarCRM according to the instructions.

## The short version is to extract the zip to a place in your webroot <source lang="bash">unzip -d /var/www/ SugarCE-5.1.0a.zip</source>

## I typically use a symbolic link to make the application home at a friendly URL and easier to manage <source lang="bash">ln -s SugarCE-5.1.0a crm</source>

# There are a number of directories that Sugar expects to have write access to, but they won't be from the unzip. There are also a couple of configuration files that the installer needs to be able to write to; namely config.php and .htaccess

# Execute this simple command to prepare your web directory

# ~~find~~ directories in ~~the ./crm path and~~ change the ~~mode on them so that all users can execute (see into) the directory~~

# recursively change ownership on the directories and set the sticky bit

~~find~~ .~~/crm/~~ -~~type d |xargs chmod a+~~x

for x in cache custom data modules; do sudo chown -R www-data:www-data $x; sudo chmod -R +t $x; done

</source>

# change ownership of the configuration files

for x in config.php .htaccess; do sudo chown www-data:www-data $x; done

</source>

~~There is one more 'gotcha' that I ran into with~~ the ~~installation. The application wants to create a .htaccess file (which doesn't exist in the distribution and would not necessarily be writable to the web user.) As a failsafe~~, the .htaccess content is printed to the screen in the installer. However it doesn't properly display (lacking newline characters) so the content is not suitable for copy and paste into the file. I resorted to the source ~~which generates the~~ .~~htaccess content, and used that. An alternative is to simply touch and chmod 777 a~~ .htaccess ~~file '''prior''' to running the installer; and then chmod'ing it go=r after install.~~

After the install, secure your configuration files with <source lang="bash">

chmod go -rwx config.php .htaccess

</source>

@@ Line 9: / Line 9: @@
 # Download SugarCE-5.0.0e.zip (production release) or the later available production release (getting only the application).
 # Visit the recommended "Installation" instructions page at http://www.sugarforge.org/content/installation/
-# Install SugarCRM according to the instructions.  Note: I immediately ran into trouble because the instructions did say to chmod 766 all files that needed to be writable by the web_user. This command renders the directories non-executable which manifests in include errors because the web user (www-data) can not see into those directories (to find includes).  The following snippet is a fix:
+# Install SugarCRM according to the instructions.
+## The short version is to extract the zip to a place in your webroot <source lang="bash">unzip -d /var/www/ SugarCE-5.1.0a.zip</source>
+## I typically use a symbolic link to make the application home at a friendly URL and easier to manage <source lang="bash">ln -s SugarCE-5.1.0a crm</source>
+# There are a number of directories that Sugar expects to have write access to, but they won't be from the unzip.  There are also a couple of configuration files that the installer needs to be able to write to; namely config.php and .htaccess
+# Execute this simple command to prepare your web directory
 <source lang="bash">
-# find directories in the ./crm path and change the mode on them so that all users can execute (see into) the directory
+# recursively change ownership on the directories and set the sticky bit
-find ./crm/ -type d |xargs chmod a+x
+for x in cache custom data modules; do sudo chown -R www-data:www-data $x; sudo chmod -R +t $x; done
-</source>
+# change ownership of the configuration files
+for x in config.php .htaccess; do sudo chown www-data:www-data $x; done
+</source>
-There is one more 'gotcha' that I ran into with the installation.  The application wants to create a .htaccess file (which doesn't exist in the distribution and would not necessarily be writable to the web user.)  As a failsafe, the .htaccess content is printed to the screen in the installer.  However it doesn't properly display (lacking newline characters) so the content is not suitable for copy and paste into the file.  I resorted to the source which generates the .htaccess content, and used that.  An alternative is to simply touch and chmod 777 a .htaccess file '''prior''' to running the installer; and then chmod'ing it go=r after install.
+After the install, secure your configuration files with <source lang="bash">
+chmod go -rwx config.php .htaccess
+</source>