17
edits
Note: Currently new registrations are closed, if you want an account Contact us
Difference between revisions of "Loomio"
Added details about current running instance and data migration process.
AkhilVarkey (talk | contribs) (Documentation for Loomio Setup and data migration.) |
AkhilVarkey (talk | contribs) (Added details about current running instance and data migration process.) |
||
| Line 1: | Line 1: | ||
[https://freesoftwareindia.org/ Loomio] instance at https://codema.in. Loomio is a '''co'''llaborative '''de'''cision-'''ma'''king platform (hence we're using the name '''codema''') where users can initiate discussions and put up proposals. | |||
== Hosting == | |||
We are now on a [https://www.scaleway.com/virtual-cloud-servers DEV1-S instance] virtual cloud server with the following specs: | |||
Moved to this server to consolidate all groups related to FSCI and Indian Pirates from loomio.org and codema.fsci.org.in to a single loomio instance. | |||
* 2 x86-64 bit Cores | |||
* 2 GB Memory | |||
* 20GB SSD Disk | |||
* 100 Mbit/s Bandwidth | |||
* 1 Reserved IP (v4) | |||
* €5.58/Month | |||
== Coordination == | |||
* Hangout with us in our Matrix room [https://matrix.to/#/#codema:poddery.com #codema:poddery.com] | |||
=== Server Access === | |||
Maintained in a private git repo at -> https://git.fosscommunity.in/community/access | |||
== History == | |||
Before moving the service to current server, we were on a [https://www.scaleway.com/virtual-cloud-servers DEV1-S instance] virtual cloud server with the following specs: | |||
* 2 x86-64 bit Cores | |||
* 2 GB Memory | |||
* 50GB SSD Disk | |||
* 200 Mbit/s Bandwidth | |||
* 1 Reserved IP (v4) | |||
* €3.99/Month | |||
We were initially on a [https://www.scaleway.com/virtual-cloud-servers VC1-S instance] virtual cloud server with the following specs until 31/01/2019. | |||
* 2 x86-64 bit Cores | |||
* 2GB Memory | |||
* 50GB SSD Disk | |||
* 1 Reserved Public IPv4 | |||
* 200Mbit/s Unmetered bandwidth | |||
* €3.99/Month | |||
On 01/02/2019 our server was taken down by [https://scaleway.com Scaleway] quoting payment issues. Payment was failing even after updating the credit card details and following that our server got deleted without proper notifications from Scaleway's side. Screenshot of the email from Scaleway attached below. Fortunately we were provided with a snapshot of the server from which we were able to recover codema to a new server. The service was moved to | |||
=== Loomio Deployment Reference === | |||
Initially loomio was deployed and updated on codema.fsci.org.in using this official guide - https://github.com/loomio/loomio-deploy. | |||
Currently loomio is deployed and updated on codema.in using the same official guide but differs on the fact that compose file uses [https://hub.docker.com/r/dannycarrera/nginx-proxy nginx-proxy] and additional parameter of VIRTUAL_HOST_ALIAS in the env file. The VIRTUAL_HOST_ALIAS is for redirecting www.codema.in queries to codema.in. We use the smtp server from nemo.libreinfra.org for sending outbound mails. | |||
=== Codema data migration process === | |||
For migration of loomio groups from both loomio.org and codema.fsci.org.in, the group data was exported using data export options provided by loomio. Changed the url links in the json data to point towards https://codema.in. The resulting json files was imported into the new codema instance after setting up the docker service as described [https://help.loomio.org/en/user_manual/groups/data_export/#import here]. | |||
=== Codema recovery process === | |||
''Here's a brief description of how codema was recovered after the server take down on 01/01/2019:'' | |||
Under 'Snapshots' tab in the Scaleway dashboard we were provided with the snapshot (backup) of our codema server. A system image was created from this snapshot and it was used to create a new server with similar specifications. We lost our public IP along with the old server, so a new IP was assigned to the server and then updated the DNS A record of codema.fsci.org.in to point to this new IP. Once the server was up loomio was restarted using the following commands from the loomio installation directory: | |||
docker-compose down | |||
docker-compose up -d | |||
The logs were checked for errors using the following command: | |||
docker-compose logs -f | |||
Loomio wasn't getting started saying the port 25 was already in use. So the application using that port (which was exim4 in this case) was killed and loomio was restarted again. | |||
[[Category: Services]] | |||