Thanks, yah those don't really need to be there. I included them to
illustrate multiple deployment configurations.
For example, if you duplicate the beta configuration for the linux
build target, you can set the FROTH_HOST and FROTH_IDENTITY to
separate hosts (or the same), then in the Index-Linux.plist/
Index.plist set up a froth_host_[configuration name] froth_root_* and
froth_port_* to correspond with the deployment name.
The froth_host_* Info.plist key can be a domain name as well as an ip.
It's value is either a plain domain or a regular expression allowing
for multiple domains/subdomains per app instance. For example for a
typical www.example.com and example.com domain, the value should be "@
(www.|^)example\.org". Whenever regex is used, the statement must
begin with '@'.
On Jan 13, 8:37 am, aarontait <aaront...@gmail.com> wrote:
> I also noticed the Info-Linux.plist in this video is slightly
> different than the one that is created with the FrothKit DP1 Xcode
> Template. Be sure to remove the froth_host_staging,
> froth_port_staging, and froth_root_staging keys. Also, make sure the
> froth_host_beta value is set to the IP address of your EC2 instance.
> On Jan 12, 7:12 pm, Allan <al...@dejumble.com> wrote:
> > Their is a commented our line that shouldn't be in the Linux target's
> > 'Deploy Script' build phase.
> > #ssh -i ${FROTH_IDENTITY} root@${FROTH_HOST} "/usr/froth/bin/fmtool -i
> > ${PRODUCT_NAME} ${CONFIGURATION}; /etc/init.d/lighttpd restart"
> > Shouldn't have the leading #
