karl3 demo site (initial) at a SFU URL

[Paul Everitt]

The goal of this task is the initial steps needed get a URL that shows KARL3, behind a Six Feet Up URL, behind a Apache or nginx server.

Steps
=======

1) Get a writable checkout.

2) Follow the installation and startup instructions in the README.txt file.

3) Startup the server.

4) Get it proxied through some nginx virtual host and eliminate the port number.

Out of scope
============

Other LP tasks will include:

1) Scheduling cron jobs for processing mail, etc.

2) Setting up mailboxes.

3) Multiple Zope clients with load balancer.

4) wsgi

5) The expires+versionedURL trick for long-lived caching of static resources.

[Paul Everitt (paul-agendaless)]

I'm available for any questions on getting started.

[Paul Everitt (paul-agendaless)]

Triage to M8.

[LarsN (lars-sixfeetup)]

http://kdiaa.sixfeetup.com

is configured as a karl3 instance through nginx.

Clayton's buildout fix took care of my earlier problems.
and
Paul Everitt's toggle for the /static coupled with an nginx location directive took care of my last hiccup.

[Paul Everitt (paul-agendaless)]

Lars, I think we should hold off on closing this ticket until we fix
the virtual hosting issue. As it stands now, the demo site can't be
used.

--Paul

On Mar 30, 2009, at 12:42 PM, LarsN wrote:

> http://kdiaa.sixfeetup.com
>
> is configured as a karl3 instance through nginx.
>
> Clayton's buildout fix took care of my earlier problems.
> and
> Paul Everitt's toggle for the /static coupled with an nginx location
> directive took care of my last hiccup.
>
>
> ** Changed in: karl3
> Status: New => Fix Committed
>
> --
> karl3 demo site (initial) at a SFU URL
> https://bugs.launchpad.net/bugs/347502
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Porting KARL to a new architecture: Fix Committed
>
> Bug description:
> The goal of this task is the initial steps needed get a URL that
> shows KARL3, behind a Six Feet Up URL, behind a Apache or nginx
> server.
>
> Steps
> =======
>
> 1) Get a writable checkout.
>
> 2) Follow the installation and startup instructions in the
> README.txt file.
>
> 3) Startup the server.
>
> 4) Get it proxied through some nginx virtual host and eliminate the
> port number.
>
> Out of scope
> ============
>
> Other LP tasks will include:
>
> 1) Scheduling cron jobs for processing mail, etc.
>
> 2) Setting up mailboxes.
>
> 3) Multiple Zope clients with load balancer.
>
> 4) wsgi
>
> 5) The expires+versionedURL trick for long-lived caching of static
> resources.

[Paul Everitt (paul-agendaless)]

Moving back to in-progress, as the virtual hosting isn't in place yet.

[LarsN (lars-sixfeetup)]

Got repoze.vhm & nginx mostly working.
It's currently showing a // between the TLD & communities (as an example)

performance seems pretty impressive.

[LarsN (lars-sixfeetup)]

This ticket is fixed......

However Paul E., Clayton, and I are going to have to come up with a solution that isn't going to break every time we run an svn up && bin/buildout

There's some talk of perhaps not needing the repoze.vhm however we didn't look into that too deeply this week.

[Paul Everitt (paul-agendaless)]

Hi Lars. Here's what I usually do in a situation like this:

1) Make a new, smaller ticket saying something like "Eliminate need
for repoze.vhm in production buildout".

2) Slot that for next week (or later).

3) Close this bigger ticket.

If that sounds ok with you, I'll make the ticket.

--Paul

On Apr 3, 2009, at 9:48 PM, LarsN wrote:

> This ticket is fixed......
>
> However Paul E., Clayton, and I are going to have to come up with a
> solution that isn't going to break every time we run an svn up &&
> bin/buildout
>
> There's some talk of perhaps not needing the repoze.vhm however we
> didn't look into that too deeply this week.
>
> --
> karl3 demo site (initial) at a SFU URL
> https://bugs.launchpad.net/bugs/347502
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Porting KARL to a new architecture: In Progress
>
> Bug description:
> The goal of this task is the initial steps needed get a URL that
> shows KARL3, behind a Six Feet Up URL, behind a Apache or nginx
> server.
>
> Steps
> =======
>
> 1) Get a writable checkout.
>
> 2) Follow the installation and startup instructions in the
> README.txt file.
>
> 3) Startup the server.
>
> 4) Get it proxied through some nginx virtual host and eliminate the
> port number.
>
> Out of scope
> ============
>
> Other LP tasks will include:
>
> 1) Scheduling cron jobs for processing mail, etc.
>
> 2) Setting up mailboxes.
>
> 3) Multiple Zope clients with load balancer.
>
> 4) wsgi
>
> 5) The expires+versionedURL trick for long-lived caching of static
> resources.

[LarsN (lars-sixfeetup)]

Sounds fine with me.

Thanks for the brief lesson in LaunchPad.

--
Thanks, Lars
--
S i x F e e t U p , I n c . | http://www.sixfeetup.com
Phone: [phone] x609
<email address hidden>
ANNOUNCING the first Plone Immersive Training Experience | Sept.
10-11-12, 2009
http://sixfeetup.com/immerse

On Apr 4, 2009, at 8:39 AM, Paul Everitt wrote:

>
> Hi Lars. Here's what I usually do in a situation like this:
>
> 1) Make a new, smaller ticket saying something like "Eliminate need
> for repoze.vhm in production buildout".
>
> 2) Slot that for next week (or later).
>
> 3) Close this bigger ticket.
>
> If that sounds ok with you, I'll make the ticket.
>
> --Paul
>
> On Apr 3, 2009, at 9:48 PM, LarsN wrote:
>
>> This ticket is fixed......
>>
>> However Paul E., Clayton, and I are going to have to come up with a
>> solution that isn't going to break every time we run an svn up &&
>> bin/buildout
>>
>> There's some talk of perhaps not needing the repoze.vhm however we
>> didn't look into that too deeply this week.
>>
>> --
>> karl3 demo site (initial) at a SFU URL
>> https://bugs.launchpad.net/bugs/347502
>> You received this bug notification because you are a direct
>> subscriber
>> of the bug.
>>
>> Status in Porting KARL to a new architecture: In Progress
>>
>> Bug description:
>> The goal of this task is the initial steps needed get a URL that
>> shows KARL3, behind a Six Feet Up URL, behind a Apache or nginx
>> server.
>>
>> Steps
>> =======
>>
>> 1) Get a writable checkout.
>>
>> 2) Follow the installation and startup instructions in the
>> README.txt file.
>>
>> 3) Startup the server.
>>
>> 4) Get it proxied through some nginx virtual host and eliminate the
>> port number.
>>
>> Out of scope
>> ============
>>
>> Other LP tasks will include:
>>
>> 1) Scheduling cron jobs for processing mail, etc.
>>
>> 2) Setting up mailboxes.
>>
>> 3) Multiple Zope clients with load balancer.
>>
>> 4) wsgi
>>
>> 5) The expires+versionedURL trick for long-lived caching of static
>> resources.
>
> --
> karl3 demo site (initial) at a SFU URL
> https://bugs.launchpad.net/bugs/347502
> You received this bug notification because you are a bug assignee.
>
> Status in Porting KARL to a new architecture: In Progress
>
> Bug description:
> The goal of this task is the initial steps needed get a URL that
> shows KARL3, behind a Six Feet Up URL, behind a Apache or nginx
> server.
>
> Steps
> =======
>
> 1) Get a writable checkout.
>
> 2) Follow the installation and startup instructions in the
> README.txt file.
>
> 3) Startup the server.
>
> 4) Get it proxied through some nginx virtual host and eliminate the
> port number.
>
> Out of scope
> ============
>
> Other LP tasks will include:
>
> 1) Scheduling cron jobs for processing mail, etc.
>
> 2) Setting up mailboxes.
>
> 3) Multiple Zope clients with load balancer.
>
> 4) wsgi
>
> 5) The expires+versionedURL trick for long-lived caching of static
> resources.

[Paul Everitt (paul-agendaless)]

Closing with https://bugs.launchpad.net/karl3/+bug/356290 covering the balance.