I work in the IT staff of a research organization working for the sustainable development.
We would like to use your kobotoolbox with some of our project.
But our policies require us to host the data.
1-We would like to change the web server port (8000 to 80). I have tried
to do it but I was not successful, how can I do that?
2-We want to backup the system on our library system, is there a way to
create a consistent backup of the application?
3-Currently, the VM is based on an Ubuntu system. We are mainly using
Centos. Do you know if it is possible to run your application on Centos,
do you have any documentation and do you “support” it?
4-I wonder how future update can be performed on our system, do you have
any documentation?
5-If I made the good configuration using my own smtp server can the
“self account creation” work?
Hi, Thomas. I’ll preface this by mentioning that we’re going to be moving away from Vagrant and migrating our virtualization approach to Docker in the coming weeks, so depending on your timeline, that might be something to consider.
I just made some updates to the setup to make this easier. To do so, put something like the following in env/env.sh:
export KOBO_SERVER_IP=192.168.1.113
export KOBOFORM_SERVER_PORT=80
Due to a known race condition with syncing the filesystems, you’ll have to vagrant reload your VM twice for the change to take effect. Also, note that to use ports less than 1024, you’ll have to run Vagrant as a privileged user
You could try SSHing in and doing a Postgres dump like:
sudo -u postgres bash -c “pg_dump "$KOBO_PSQL_DB_NAME" | xz” > my_backup.sql.xz
No. We develop primarily on Ubuntu flavors and Vagrant (soon Docker) is our way of supporting alternative environments.
On Thursday, August 6, 2015 at 3:20:06 AM UTC-4, doll...@gmail.com wrote:
Hello kobotoolbox team,
I work in the IT staff of a research organization working for the sustainable development.
We would like to use your kobotoolbox with some of our project.
But our policies require us to host the data.
1-We would like to change the web server port (8000 to 80). I have tried
to do it but I was not successful, how can I do that?
2-We want to backup the system on our library system, is there a way to
create a consistent backup of the application?
3-Currently, the VM is based on an Ubuntu system. We are mainly using
Centos. Do you know if it is possible to run your application on Centos,
do you have any documentation and do you “support” it?
4-I wonder how future update can be performed on our system, do you have
any documentation?
5-If I made the good configuration using my own smtp server can the
“self account creation” work?
Ok I can see the idea, but to be sure, that mean that all data are in the database ?
OK. Do you know when the release with docker will be available ?
OK. If we do something like backup all data base , redeploy the VM and import the backuped database. Is this going to work ?
OK I will try.
Best regards
Thomas
···
Le mercredi 2 septembre 2015 00:04:09 UTC+2, Esmail Fadae a écrit :
Hi, Thomas. I’ll preface this by mentioning that we’re going to be moving away from Vagrant and migrating our virtualization approach to Docker in the coming weeks, so depending on your timeline, that might be something to consider.
I just made some updates to the setup to make this easier. To do so, put something like the following in env/env.sh:
export KOBO_SERVER_IP=192.168.1.113
export KOBOFORM_SERVER_PORT=80
Due to a known race condition with syncing the filesystems, you’ll have to vagrant reload your VM twice for the change to take effect. Also, note that to use ports less than 1024, you’ll have to run Vagrant as a privileged user
You could try SSHing in and doing a Postgres dump like:
sudo -u postgres bash -c “pg_dump "$KOBO_PSQL_DB_NAME" | xz” > my_backup.sql.xz
No. We develop primarily on Ubuntu flavors and Vagrant (soon Docker) is our way of supporting alternative environments.
On Thursday, August 6, 2015 at 3:20:06 AM UTC-4, doll...@gmail.com wrote:
Hello kobotoolbox team,
I work in the IT staff of a research organization working for the sustainable development.
We would like to use your kobotoolbox with some of our project.
But our policies require us to host the data.
1-We would like to change the web server port (8000 to 80). I have tried
to do it but I was not successful, how can I do that?
2-We want to backup the system on our library system, is there a way to
create a consistent backup of the application?
3-Currently, the VM is based on an Ubuntu system. We are mainly using
Centos. Do you know if it is possible to run your application on Centos,
do you have any documentation and do you “support” it?
4-I wonder how future update can be performed on our system, do you have
any documentation?
5-If I made the good configuration using my own smtp server can the
“self account creation” work?
Any updates to this? I’m looking to update my instance from vagrant to docker but I am worried that I’ll lose my data!
···
On Monday, September 14, 2015 at 7:14:18 AM UTC-5, doll...@gmail.com wrote:
Hi Esmail,
Thank you for your answer.
You can find my comment below
Great I wil test it .
Ok I can see the idea, but to be sure, that mean that all data are in the database ?
OK. Do you know when the release with docker will be available ?
OK. If we do something like backup all data base , redeploy the VM and import the backuped database. Is this going to work ?
OK I will try.
Best regards
Thomas
Le mercredi 2 septembre 2015 00:04:09 UTC+2, Esmail Fadae a écrit :
Hi, Thomas. I’ll preface this by mentioning that we’re going to be moving away from Vagrant and migrating our virtualization approach to Docker in the coming weeks, so depending on your timeline, that might be something to consider.
I just made some updates to the setup to make this easier. To do so, put something like the following in env/env.sh:
export KOBO_SERVER_IP=192.168.1.113
export KOBOFORM_SERVER_PORT=80
Due to a known race condition with syncing the filesystems, you’ll have to vagrant reload your VM twice for the change to take effect. Also, note that to use ports less than 1024, you’ll have to run Vagrant as a privileged user
You could try SSHing in and doing a Postgres dump like:
sudo -u postgres bash -c “pg_dump "$KOBO_PSQL_DB_NAME" | xz” > my_backup.sql.xz
No. We develop primarily on Ubuntu flavors and Vagrant (soon Docker) is our way of supporting alternative environments.
On Thursday, August 6, 2015 at 3:20:06 AM UTC-4, doll...@gmail.com wrote:
Hello kobotoolbox team,
I work in the IT staff of a research organization working for the sustainable development.
We would like to use your kobotoolbox with some of our project.
But our policies require us to host the data.
1-We would like to change the web server port (8000 to 80). I have tried
to do it but I was not successful, how can I do that?
2-We want to backup the system on our library system, is there a way to
create a consistent backup of the application?
3-Currently, the VM is based on an Ubuntu system. We are mainly using
Centos. Do you know if it is possible to run your application on Centos,
do you have any documentation and do you “support” it?
4-I wonder how future update can be performed on our system, do you have
any documentation?
5-If I made the good configuration using my own smtp server can the
“self account creation” work?
Hi, Ben. Apologies for the delay in getting back to you. I’m currently in the process of the related work of setting up automated backups to use with our Docker environment (). If you’re comfortable doing so, replicating the steps taken in the backup_*.bash scripts should be sufficient to get you backups of your KoBoCAT media, Mongo DB, and Postgres DB (no Redis DB yet). I’m still figuring out how to approach restoring backups in kobo-docker, but in the meantime maybe we could just step through the process together.
Any updates to this? I'm looking to update my instance from vagrant to docker but I am worried that I'll lose my data!
On Monday, September 14, 2015 at 7:14:18 AM UTC-5, wrote:
–
You received this message because you are subscribed to the Google Groups "KoBo Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kobo-develope...@googlegroups.com.
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
Thank you for your answer.
You can find my comment below
1. Great I wil test it .
2. Ok I can see the idea, but to be sure, that mean that all data are in the database ?
3. OK. Do you know when the release with docker will be available ?
4. OK. If we do something like backup all data base , redeploy the VM and import the backuped database. Is this going to work ?
5. OK I will try.
Best regards
Thomas
Le mercredi 2 septembre 2015 00:04:09 UTC+2, Esmail Fadae a écrit :
Hi, Thomas. I'll preface this by mentioning that we're going to be moving away from Vagrant and migrating our virtualization approach to Docker in the coming weeks, so depending on your timeline, that might be something to consider.
1. I just made some updates to the setup to make this easier. To do so, put something like the following in `env/env.sh`:
export KOBO_SERVER_IP=192.168.1.113
export KOBOFORM_SERVER_PORT=80
Due to a known race condition with syncing the filesystems, you'll have to `vagrant reload` your VM twice for the change to take effect. Also, note that to use ports less than 1024, you'll have to run Vagrant as a privileged user
2. You could try SSHing in and doing a Postgres dump like:
sudo -u postgres bash -c "pg_dump \"$KOBO_PSQL_DB_NAME\" | xz" > my_backup.sql.xz
3. No. We develop primarily on Ubuntu flavors and Vagrant (soon Docker) is our way of supporting alternative environments.
4. We don't currently have an easy way to update the VMs. For clues on updating the system, you can check out the Fabric files we use to update our production servers:
[https://github.com/kobotoolbox/dkobo/blob/master/fabfile.py#L54-L90](https://github.com/kobotoolbox/dkobo/blob/master/fabfile.py#L54-L90)
[https://github.com/kobotoolbox/kobocat/blob/master/fabfile.py#L83-L118](https://github.com/kobotoolbox/kobocat/blob/master/fabfile.py#L83-L118)
(Check [https://github.com/kobotoolbox/enketo-express](https://github.com/kobotoolbox/enketo-express)
for instructions on updating Enketo).
5. We haven't tried that on a VM, but presumably the usual Django e-mail setup will work: [https://docs.djangoproject.com/en/1.6/topics/email/](https://docs.djangoproject.com/en/1.6/topics/email/).
On Thursday, August 6, 2015 at 3:20:06 AM UTC-4, doll...@gmail.com wrote:
Hello kobotoolbox team,
I work in the IT staff of a research organization working for the sustainable development.
We would like to use your kobotoolbox with some of our project.
But our policies require us to host the data.
I have already install kobotoolbox on my computer. (following this
documentation :
[http://support.kobotoolbox.org/customer/portal/articles/1691105-installing-and-using-kobotoolbox-on-your-computer](http://support.kobotoolbox.org/customer/portal/articles/1691105-installing-and-using-kobotoolbox-on-your-computer)
and then transform the virtualbox file to an vmware file ).
We have the following questions:
1-We would like to change the web server port (8000 to 80). I have tried
to do it but I was not successful, how can I do that?
2-We want to backup the system on our library system, is there a way to
create a consistent backup of the application?
3-Currently, the VM is based on an Ubuntu system. We are mainly using
Centos. Do you know if it is possible to run your application on Centos,
do you have any documentation and do you "support" it?
4-I wonder how future update can be performed on our system, do you have
any documentation?
5-If I made the good configuration using my own smtp server can the
"self account creation" work?
Thank you in advance for your reply
Best regards
Thomas
On Wednesday, November 2, 2016 at 7:32:20 AM UTC-6, Ben Brown wrote:
Any updates to this? I’m looking to update my instance from vagrant to docker but I am worried that I’ll lose my data!
On Monday, September 14, 2015 at 7:14:18 AM UTC-5, doll...@gmail.com wrote:
Hi Esmail,
Thank you for your answer.
You can find my comment below
Great I wil test it .
Ok I can see the idea, but to be sure, that mean that all data are in the database ?
OK. Do you know when the release with docker will be available ?
OK. If we do something like backup all data base , redeploy the VM and import the backuped database. Is this going to work ?
OK I will try.
Best regards
Thomas
Le mercredi 2 septembre 2015 00:04:09 UTC+2, Esmail Fadae a écrit :
Hi, Thomas. I’ll preface this by mentioning that we’re going to be moving away from Vagrant and migrating our virtualization approach to Docker in the coming weeks, so depending on your timeline, that might be something to consider.
I just made some updates to the setup to make this easier. To do so, put something like the following in env/env.sh:
export KOBO_SERVER_IP=192.168.1.113
export KOBOFORM_SERVER_PORT=80
Due to a known race condition with syncing the filesystems, you’ll have to vagrant reload your VM twice for the change to take effect. Also, note that to use ports less than 1024, you’ll have to run Vagrant as a privileged user
You could try SSHing in and doing a Postgres dump like:
sudo -u postgres bash -c “pg_dump "$KOBO_PSQL_DB_NAME" | xz” > my_backup.sql.xz
No. We develop primarily on Ubuntu flavors and Vagrant (soon Docker) is our way of supporting alternative environments.
On Thursday, August 6, 2015 at 3:20:06 AM UTC-4, doll...@gmail.com wrote:
Hello kobotoolbox team,
I work in the IT staff of a research organization working for the sustainable development.
We would like to use your kobotoolbox with some of our project.
But our policies require us to host the data.
1-We would like to change the web server port (8000 to 80). I have tried
to do it but I was not successful, how can I do that?
2-We want to backup the system on our library system, is there a way to
create a consistent backup of the application?
3-Currently, the VM is based on an Ubuntu system. We are mainly using
Centos. Do you know if it is possible to run your application on Centos,
do you have any documentation and do you “support” it?
4-I wonder how future update can be performed on our system, do you have
any documentation?
5-If I made the good configuration using my own smtp server can the
“self account creation” work?
