Ok, I am struggling with loading
EspoCRM into a normal ibay. I am hugely encouraged having been able to get it up-and-running in the Primary ibay (thanks mmccarn) but the normal ibay seems to need something more.
I am assuming that this has got to do with this software using an .htaccess file. I am presuming that as I am now installing to a regular Ibay (and not Primary) I will need to create a 'custom template fragment' to modify my htttpd.conf. Is this right, or am I barking up the wrong tree?
So I have created ibay, created database, chown and chmod the ibay, run the installer and get (as per my opening post):
API Error: EspoCRM API unavailable.
Possible problems: disabled "mod_rewrite" in Apache server or .htaccess support.
To enable .htaccess support add/edit the Server configuration settings inside your <VirtualHost> section (httpd.conf):
<Directory /PATH_TO_ESPO/>
AllowOverride All
</Directory>
Afterwards run this command in a Terminal:service apache2 restart
To enable "mod_rewrite" run those commands in a Terminal:"
a2enmod rewrite
service apache2 restart
When I run:
db accounts show crm
I get
crm=ibay
AllowOverride=All
AllowUrlfOpen=disabled
CgiBin=enabled
FollowSymLinks=enabled
Gid=5000
Group=shared
Indexes=enabled
MaxExecTime=disabled
MemoryLimit=disabled
ModDav=enabled
Name=CRM
PHPBaseDir=/home/e-smith/files/ibays/crm/:/tmp/
PasswordSet=no
PostMaxSize=disabled
PublicAccess=local
SSL=enabled
Uid=5000
UpMaxFileSize=disabled
UserAccess=wr-admin-rd-group
I assume the settings listed immediately above relate to the ibay overall and not to specific files and directories (.htaccess application). Are these settings applied via the httpd.conf also (like a 'custom template fragment'?).
I have no doubt that I can follow the instructions in
http://wiki.contribs.org/Htaccess but I don't really UNDERSTAND what I am doing?
Can anyone
(1) confirm that I need a 'custom template fragment' and that I am not simply doing something else simple wrong, and
(2) explain how the httpd.conf and the .htaccess access file are supposed to work together (or not).
Currently there is no .htaccess file present in /api/v1/<.htaccess not present> - I presume because the installer hasn't been able to create one.