Hi again,
Another question, as I'm not familiar with the limitations of most web
hosting providers. Can ODK Aggregate be made to work on a remotely
hosted server, such as one provided by a web hosting company?
Or would it make more sense to build a server and have it colocated at
a server farm?
My provider didn't seem familiar with the idea of installing Aggregate
on my business website. They said they can't host third party
software. Are there known capable web hosting companies that can host
ODK Aggregate?
Thank you again,
Mike
hi mike,
the fastest, easiest and cheapest way to get aggregate running
remotely is to deploy it on google app engine. even if you don't see
this is a permanent solution, i'd encourage you to try it first.
if you are uncomfortable with your data in the google cloud, the alpha
(unstable and unreleased) of aggregate will run any tomcat/mysql
backend (locally on a server you control, remotely on aws with a vm,
or remotely on any java hosting service).
yaw
···
On Tue, Mar 22, 2011 at 12:47, sketchy wrote:
> Hi again,
>
> Another question, as I'm not familiar with the limitations of most web
> hosting providers. Can ODK Aggregate be made to work on a remotely
> hosted server, such as one provided by a web hosting company?
>
> Or would it make more sense to build a server and have it colocated at
> a server farm?
>
> My provider didn't seem familiar with the idea of installing Aggregate
> on my business website. They said they can't host third party
> software. Are there known capable web hosting companies that can host
> ODK Aggregate?
>
> Thank you again,
>
>
> Mike
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
GAE is definitely the most directly supported server farm implementation for
Aggregate.
Aggregate 1.0 (still in alpha; unreleased) should run in any Java servlet
2.5
container. We test it only on Tomcat 6, and don't knowingly use anything
specific to Tomcat, so it should work on other containers (e.g., Jetty,
Glassfish).
We won't test and support other containers ourselves, but if you find a bug
and
have a fix, we would fold that into the source tree.
The servlet 2.5 container deployment does use background threads (sometimes
an issue with webfarms). That deployment also expects container support for
session management (session handles), which can make configuration of
multiple servers tricky. This last issue is why GAE is the preferred server
farm
implementation -- GAE infrastructure handles the maintenance of the session.
Mitch
···
On Tue, Mar 22, 2011 at 2:39 PM, Yaw Anokwa wrote:
hi mike,
the fastest, easiest and cheapest way to get aggregate running
remotely is to deploy it on google app engine. even if you don't see
this is a permanent solution, i'd encourage you to try it first.
if you are uncomfortable with your data in the google cloud, the alpha
(unstable and unreleased) of aggregate will run any tomcat/mysql
backend (locally on a server you control, remotely on aws with a vm,
or remotely on any java hosting service).
yaw
On Tue, Mar 22, 2011 at 12:47, sketchy inabahort@gmail.com wrote:
Hi again,
Another question, as I'm not familiar with the limitations of most web
hosting providers. Can ODK Aggregate be made to work on a remotely
hosted server, such as one provided by a web hosting company?
Or would it make more sense to build a server and have it colocated at
a server farm?
My provider didn't seem familiar with the idea of installing Aggregate
on my business website. They said they can't host third party
software. Are there known capable web hosting companies that can host
ODK Aggregate?
Thank you again,
Mike
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Mitch Sundt
Software Engineer
http://www.OpenDataKit.org
University of Washington
mitchellsundt@gmail.com
Until Aggregate 1.0 is officially released, there is really no other option
except Google App Engine. I tried a test deployment with the alpha code, and
it was going well, until my form required doubly nested repeating nodes. I
found a tremendous amount of data loss (correct number of rows for my
repeating nodes, but null values where data should have been). I am sure
this will be worked out with a final release, but for all practical purposes
App Engine is it for now.
Stuart
···
On Tue, Mar 22, 2011 at 4:27 PM, Mitch Sundt wrote:
GAE is definitely the most directly supported server farm implementation
for
Aggregate.
Aggregate 1.0 (still in alpha; unreleased) should run in any Java servlet
2.5
container. We test it only on Tomcat 6, and don't knowingly use anything
specific to Tomcat, so it should work on other containers (e.g., Jetty,
Glassfish).
We won't test and support other containers ourselves, but if you find a bug
and
have a fix, we would fold that into the source tree.
The servlet 2.5 container deployment does use background threads (sometimes
an issue with webfarms). That deployment also expects container support
for
session management (session handles), which can make configuration of
multiple servers tricky. This last issue is why GAE is the preferred
server farm
implementation -- GAE infrastructure handles the maintenance of the
session.
Mitch
On Tue, Mar 22, 2011 at 2:39 PM, Yaw Anokwa yanokwa@gmail.com wrote:
hi mike,
the fastest, easiest and cheapest way to get aggregate running
remotely is to deploy it on google app engine. even if you don't see
this is a permanent solution, i'd encourage you to try it first.
if you are uncomfortable with your data in the google cloud, the alpha
(unstable and unreleased) of aggregate will run any tomcat/mysql
backend (locally on a server you control, remotely on aws with a vm,
or remotely on any java hosting service).
yaw
On Tue, Mar 22, 2011 at 12:47, sketchy inabahort@gmail.com wrote:
Hi again,
Another question, as I'm not familiar with the limitations of most web
hosting providers. Can ODK Aggregate be made to work on a remotely
hosted server, such as one provided by a web hosting company?
Or would it make more sense to build a server and have it colocated at
a server farm?
My provider didn't seem familiar with the idea of installing Aggregate
on my business website. They said they can't host third party
software. Are there known capable web hosting companies that can host
ODK Aggregate?
Thank you again,
Mike
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Mitch Sundt
Software Engineer
http://www.OpenDataKit.org
University of Washington
mitchellsundt@gmail.com
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
Thanks all,
GAE is functioning well. I will need to protect the data a little better to
make it a good solution. As for convenience, GAE can't be beat. I'm a
complete newbie, but it gave me no trouble. (lots of reading and learning
though).
Mike
Until Aggregate 1.0 is officially released, there is really no other
option
except Google App Engine. I tried a test deployment with the alpha code,
and
it was going well, until my form required doubly nested repeating nodes. I
found a tremendous amount of data loss (correct number of rows for my
repeating nodes, but null values where data should have been). I am sure
this will be worked out with a final release, but for all practical
purposes
App Engine is it for now.
Stuart
GAE is definitely the most directly supported server farm implementation
for
Aggregate.
Aggregate 1.0 (still in alpha; unreleased) should run in any Java servlet
2.5
container. We test it only on Tomcat 6, and don't knowingly use anything
specific to Tomcat, so it should work on other containers (e.g., Jetty,
Glassfish).
We won't test and support other containers ourselves, but if you find a
bug
and
have a fix, we would fold that into the source tree.
The servlet 2.5 container deployment does use background threads
(sometimes
···
On Mar 22, 2011 3:45 PM, "Stuart Moffatt" wrote:
> On Tue, Mar 22, 2011 at 4:27 PM, Mitch Sundt > an issue with webfarms). That deployment also expects container support
>> for
>> session management (session handles), which can make configuration of
>> multiple servers tricky. This last issue is why GAE is the preferred
>> server farm
>> implementation -- GAE infrastructure handles the maintenance of the
>> session.
>>
>> Mitch
>>
>>
>> On Tue, Mar 22, 2011 at 2:39 PM, Yaw Anokwa wrote:
>>
>>> hi mike,
>>>
>>> the fastest, easiest and cheapest way to get aggregate running
>>> remotely is to deploy it on google app engine. even if you don't see
>>> this is a permanent solution, i'd encourage you to try it first.
>>>
>>> if you are uncomfortable with your data in the google cloud, the alpha
>>> (unstable and unreleased) of aggregate will run any tomcat/mysql
>>> backend (locally on a server you control, remotely on aws with a vm,
>>> or remotely on any java hosting service).
>>>
>>> yaw
>>>
>>> On Tue, Mar 22, 2011 at 12:47, sketchy wrote:
>>> > Hi again,
>>> >
>>> > Another question, as I'm not familiar with the limitations of most web
>>> > hosting providers. Can ODK Aggregate be made to work on a remotely
>>> > hosted server, such as one provided by a web hosting company?
>>> >
>>> > Or would it make more sense to build a server and have it colocated at
>>> > a server farm?
>>> >
>>> > My provider didn't seem familiar with the idea of installing Aggregate
>>> > on my business website. They said they can't host third party
>>> > software. Are there known capable web hosting companies that can host
>>> > ODK Aggregate?
>>> >
>>> > Thank you again,
>>> >
>>> >
>>> > Mike
>>> >
>>> > --
>>> > Post: opendatakit@googlegroups.com
>>> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>> > Options: http://groups.google.com/group/opendatakit?hl=en
>>> >
>>>
>>> --
>>> Post: opendatakit@googlegroups.com
>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>> Options: http://groups.google.com/group/opendatakit?hl=en
>>>
>>
>>
>>
>> --
>> Mitch Sundt
>> Software Engineer
>> http://www.OpenDataKit.org
>> University of Washington
>> mitchellsundt@gmail.com
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en