[OGo-Users] OGo and what client to use.

[Adam Tauno Williams]

--=-44P20tDStGrXwJkSdric
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

> > I'll see what i can do to get them to upgrade, too.
> I setup a test-OGo system in a VMWare server image.
> If you want, I can setup a user for you (or more) to test this out with=20
> lightning or else...
> I just upgraded OGo yesterday to latest debian SVN built packages - I=20
> try to keep that install up to date for the lightning dev team as a=20
> testing ground.

My recommendation:
(a) Always run the server(s) in VMware, unless you are running a
fire-breathing ultra-busy database server there isn't any reason not to.
(b) Run two servers, or at least two servers.  Pull down newer builds on
one for testing, and if everything is OK, slide that version over to the
production instance.  You can keep the testing instance on the same
physical box if you are resource constrained,  just leave it shutdown
when you aren't using it and it is out-of-the-way.
(c) You can always snapshot at update and roll-back if it turns out
there is a problem.  This works best if you keep your actual data on a
SAN or NAS, or just on another virtual server.

It is a wonderful way to operate and the vmware-server free addition is
more than adequate for small sites.

--=-44P20tDStGrXwJkSdric
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQBHTskoLRePpNle04MRAgq8AJ0QDF303RC3zQiGW+XvbKpxN6QJwACeJO7G
NUN+nlo6OwGX96atadNq20M=
=r/0u
-----END PGP SIGNATURE-----

--=-44P20tDStGrXwJkSdric--