일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | |||
5 | 6 | 7 | 8 | 9 | 10 | 11 |
12 | 13 | 14 | 15 | 16 | 17 | 18 |
19 | 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 | 31 |
- rds
- 코멘토 직무부트캠프
- 프로토타입 미니 프로젝트
- 제너레이터
- 로드 밸런서
- eip 비용
- 워드프레스 매니지드
- alb 구축
- private 서브넷 접속
- 생성자 함수
- ec2에 apache설치
- bastion host
- 비동기처리
- aws
- 직무부트캠프 후기
- aws 비용 계산
- NAT 게이트웨이
- 코멘토
- Budgets
- ec2 ssh 접속
- MySQL 접속
- 프라미스
- 자바스크립트 클래스
- ec2 생성
- 직무경험
- 코멘토 후기
- 프리티어
- pricing calculator
- 직무부트캠프
- 프로토타입 상속
- Today
- Total
목록문서 독해 연습 (7)
기본을 충실하게
As with many great things in life, Git began with a bit of creative destruction and fiery controversy. 인생의 위대한 것들이 그렇듯이, 깃은 약간의 생성과 소멸 그리고 격한 논쟁과 함께 시작되었다. The Linux kernel is an open source software project of fairly large scope. During the early years of the Linux kernel maintenance (1991–2002), changes to the software were passed around as patches and archived files. In 2002, the Linux kernel..
This is where Distributed Version Control Systems (DVCSs) step in. In a DVCS (such as Git, Mercurial, Bazaar or Darcs), clients don’t just check out the latest snapshot of the files; rather, they fully mirror the repository, including its full history. Thus, if any server dies, and these systems were collaborating via that server, any of the client repositories can be copied back up to the serve..
The next major issue that people encounter is that they need to collaborate with developers on other systems. To deal with this problem, Centralized Version Control Systems (CVCSs) were developed. These systems (such as CVS, Subversion, and Perforce) have a single server that contains all the versioned files, and a number of clients that check out files from that central place. For many years, t..
Many people’s version-control method of choice is to copy files into another directory (perhaps a time-stamped directory, if they’re clever). This approach is very common because it is so simple, but it is also incredibly error prone. It is easy to forget which directory you’re in and accidentally write to the wrong file or copy over files you don’t mean to. 많은 사람들이 버전 제어로 파일을 다른 디렉터리로 복사하는 방법을 ..
What is “version control”, and why should you care? Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later. For the examples in this book, you will use software source code as the files being version controlled, though in reality you can do this with nearly any type of file on a computer. 버전 관리가 무었이고, 왜 관심을 가져야 할까? / 버전..
This chapter will be about getting started with Git. We will begin by explaining some background on version control tools, then move on to how to get Git running on your system and finally how to get it set up to start working with. At the end of this chapter you should understand why Git is around, why you should use it and you should be all set up to do so. 이 챕터는 Git의 처음으로 시작할 것이다. / 우리는 조금 설명..
Introduction In Chapter 1, we’re going to cover Version Control Systems (VCSs) and Git basics — no technical stuff, just what Git is, why it came about in a land full of VCSs, what sets it apart, and why so many people are using it. Then, we’ll explain how to download Git and set it up for the first time if you don’t already have it on your system. 챕터1에서, // 우리는 버전 제어 시스템 과 깃 기초를 다룰 것입니다 // 기술적인..