Loomio/Archive 1
Loomio instance at https://codema.fsci.org.in. Loomio is a collaborative decision-making platform (hence we're using the name codema) where users can initiate discussions and put up proposals.
Hosting
We were now on a START1-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
Coordination
- Hangout with us in our Matrix room #codema:poddery.com
Server Access
Maintained in a private git repo at -> https://git.fosscommunity.in/community/access
History
We were on a VC1S instance virtual cloud server with the following specs until 31/01/2019.
- 2 x86-64 bit Cores
- 2GB Memory
- 50GB SSD Disk
- 1 Flexible Public IPv4
- 200Mbit/s Unmetered bandwidth
- €2.99/Month
On 01/02/2019 our server was taken down by 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.
Loomio Deployment Reference
Loomio was deployed and updated on codema.fsci.org.in after following this Loomio Deployment Reference - https://github.com/loomio/loomio-deploy
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.