So, as we mull over putting ODK Aggregate in a Docker container, I have
this question:
If I put my ODK Aggregate war in a Tomcat container running against MySQL
or Postgres and upload some forms and form instance data, then the Tomcat
container explodes in a horrible flaming meltdown, and I reinstall ODK
Aggregate from scratch to a new Tomcat container and point it back at the
same database, will all the data be preserved? Or are there files created
on the application side that reside only in the Tomcat container?
Thanks,
Caden
The Tomcat container is read-only. Nothing is stored on disk.
The web app is completely disposable.
I.e., it is ideal for running in a docker container.
From an systems architecture standpoint, it would be best to have the
webapp in its own docker container so that N of them could be spun up, and
then have the database in a separate container that mounts a disk share for
holding the data, and that share is persistent (e.g., a partition /
directory tree on the host OS).
···
On Thu, Mar 2, 2017 at 1:18 PM, C. Howell wrote:
So, as we mull over putting ODK Aggregate in a Docker container, I have
this question:
If I put my ODK Aggregate war in a Tomcat container running against MySQL
or Postgres and upload some forms and form instance data, then the Tomcat
container explodes in a horrible flaming meltdown, and I reinstall ODK
Aggregate from scratch to a new Tomcat container and point it back at the
same database, will all the data be preserved? Or are there files created
on the application side that reside only in the Tomcat container?
Thanks,
Caden
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
(Then you could put all N of them behind a load balancer)
···
On Thu, Mar 2, 2017 at 1:34 PM, Mitch Sundt wrote:
The Tomcat container is read-only. Nothing is stored on disk.
The web app is completely disposable.
I.e., it is ideal for running in a docker container.
From an systems architecture standpoint, it would be best to have the
webapp in its own docker container so that N of them could be spun up, and
then have the database in a separate container that mounts a disk share for
holding the data, and that share is persistent (e.g., a partition /
directory tree on the host OS).
On Thu, Mar 2, 2017 at 1:18 PM, C. Howell caden@cadenconsulting.com wrote:
So, as we mull over putting ODK Aggregate in a Docker container, I have
this question:
If I put my ODK Aggregate war in a Tomcat container running against MySQL
or Postgres and upload some forms and form instance data, then the Tomcat
container explodes in a horrible flaming meltdown, and I reinstall ODK
Aggregate from scratch to a new Tomcat container and point it back at the
same database, will all the data be preserved? Or are there files created
on the application side that reside only in the Tomcat container?
Thanks,
Caden
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com