Bureaucrats, confirmed, Administrators
4,558
edits
Changes
Jump to navigation
Jump to search
There is one more 'gotcha' that I ran into with After 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 failsafeinstall, 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 secure your configuration files with <source which generates the lang="bash">chmod go -rwx config.htaccess content, and used that. An alternative is to simply touch and chmod 777 a php .htaccess file '''prior''' to running the installer; and then chmod'ing it go=r after install.</source>
updated instructions
# 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: ## 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 immediately ran into trouble because typically use a symbolic link to make the instructions did say application home at a friendly URL and easier to chmod 766 all files manage <source lang="bash">ln -s SugarCE-5.1.0a crm</source># There are a number of directories that needed Sugar expects to have write access to, but they won't be writable by from the web_userunzip. This command renders There are also a couple of configuration files that the directories non-executable which manifests in include errors because the web user (www-data) can not see into those directories (installer needs to be able to write to find includes); namely config. The following snippet is a fix:php and .htaccess# Execute this simple command to prepare your web directory
<source lang="bash">
# find recursively change ownership on the directories and set the sticky bitfor x in the ./crm path and cache custom data modules; do sudo chown -R www-data:www-data $x; sudo chmod -R +t $x; done# change ownership of the mode on them so that all users can execute (see into) the directory configuration filesfind for x in config.php ./crm/ htaccess; do sudo chown www-data:www-type d |xargs chmod a+data $x ; done</source>
