Previously, apache would fail when the ssl site was enabled. It appears that this is an issue with the SSL certificates in the FTSW data pack (possible) or the way that I am adding them to the machine (more likely). Apache is happy to use the default SSL certificates so we now do that.
Fixing SSL exposed a new bug: emma wasn't romance publishing its models. Without emma publishing its models every attempt to access a mia route would result in a NameError exception. The handling of that exception would result in the user being logged out of both emma and mia. In short clicking on mia links would log the user out.
Emma uses a background job (delayed_job) to romance publish its models. The init.d script for delayed_job is now added to the build.
The FTSW setup.sh script has been updated to configure apache for HTTPS access only, and the hack allowing sign in over HTTP has been removed.
Previously, apache would fail when the
sslsite was enabled. It appears that this is an issue with the SSL certificates in the FTSW data pack (possible) or the way that I am adding them to the machine (more likely). Apache is happy to use the default SSL certificates so we now do that.Fixing SSL exposed a new bug: emma wasn't romance publishing its models. Without
emmapublishing its models every attempt to access amiaroute would result in aNameErrorexception. The handling of that exception would result in the user being logged out of bothemmaandmia. In short clicking onmialinks would log the user out.Emma uses a background job (
delayed_job) to romance publish its models. Theinit.dscript fordelayed_jobis now added to the build.The FTSW
setup.shscript has been updated to configure apache for HTTPS access only, and the hack allowing sign in over HTTP has been removed.