Just checked on https://twitter.com/gitlabstatus
The update is that data transfer is very slow and they are just 42% into
the backup.
I am now completely sure that we will not have it up at least today.
This brings me to a very important discussion.
Just had a talk with Ishan, Ravi and a few others here in the lab.
This is not the first time such an issue has happened, although
previusly it was not a major problem.
We had several downtime periods on gitlab off late.
After today's disaster, I strongly believe that we must host our own
gitlab repository and have the control with us.
The advantage is that we will not have to be dependent on some third
party to give us that service.
The flip side of this is that some one from GNUKhata team must
administer the server.
This is not a big problem though because every thing these days is just
few clicks away and is automated.
And we don't need to do admin every day.
I wish to know views of all of you on this.
Happy hacking.
Krishnakant.
On Wednesday 01 February 2017 11:37 AM, Krishnakant wrote:
I am in touch with them on twitter.
You can check #kkmane for my handle.
What happened is that some one by mistake ran the rm command at the wrong place and so that has resulted in data deletion of production grade.
It is really a very bad news.
Happy hacking.
Krishnakant.
On Wednesday 01 February 2017 11:15 AM, Ramnarayan.K wrote:
Terrible to hear
Are they saying the data is lost, or just that the servers are down and hence not accessible.
Hope things work out
ram
On 1 February 2017 at 11:02, abhijith <abhijithb21@xxxxxxxxxxxxxxx <mailto:abhijithb21@xxxxxxxxxxxxxxx>> wrote:
You can follow their twitter page to stay updated.
https://twitter.com/gitlabstatus ;<https://twitter.com/gitlabstatus>
On Wednesday 01 February 2017 07:41 AM, Krishnakant wrote:
> Dear all,
>
> This is some calamity.
>
> Gitlab servers where our project source is hosted is down and
as per
> their twitter account (which you can get from the gitlab.com
<http://gitlab.com> page )
> they have accidentally deleted some production data.
>
> While our project source is save, the major data regarding
releases,
> merge requests and overall connectivity is absolutely lost.
>
> As a result we are neither able to issue the release note with
final
> changes, nor update the live demo.
>
> We won't be able to make installer ready either. So we will have to
> just wait and see by want time they get the servers up and running.
>
> I will post any update on this issue as soon as I get any
further news.
>
> Let's hope that this is sorted by today evening.
>
> Happy hacking.
>
> Krishnakant.
>
>
>
>
> On Tuesday 31 January 2017 06:05 PM, Krishnakant wrote:
>> Dear users and developers.
>>
>> As you are aware we are about to release an update for version 3.5
>> series.
>>
>> We are trying to release by today night, however we are currently
>> facing technical problem on our servers. As a result we may
have to
>> postpone the release to tomorrow (1 Feb 2017) although work gets
>> complete today.
>>
>> Kindly bare with us for a day and sorry for the delay.
>>
>> Happy hacking.
>>
>> Krishnakant.
>>
>>
>>
>
>
