<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>GitLab on Lin's Blog</title><link>https://coder.tw/en/tags/gitlab/</link><description>Recent content in GitLab on Lin's Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 01 Feb 2017 23:58:28 +0000</lastBuildDate><atom:link href="https://coder.tw/en/tags/gitlab/index.xml" rel="self" type="application/rss+xml"/><item><title>When GitLab Deleted Its Database by Mistake, How Do We Keep the rm Command Under Control?</title><link>https://coder.tw/en/posts/gitlab-deleted-database-rm-command/</link><pubDate>Wed, 01 Feb 2017 23:58:28 +0000</pubDate><guid>https://coder.tw/en/posts/gitlab-deleted-database-rm-command/</guid><description>&lt;p&gt;We have all heard the story of someone accidentally deleting the root directory as a joke, but don&amp;rsquo;t think it is just a joke! I have personally seen countless friends&amp;rsquo; computers suffer this kind of disaster. Today, the engineers at GitLab (a service similar to GitHub) also demonstrated the immense power of the rm -rf command&amp;hellip; They wiped out the database on the production server&amp;hellip; I always thought this kind of disaster would never happen to me, but now even a service like GitLab, which has tens of thousands of users, has had it happen through carelessness. That made me look into how to prevent it, so let&amp;rsquo;s talk about how to keep the rm command under control!&lt;/p&gt;</description></item></channel></rss>