[Git & WSL] Django Coding - Day 1

#note: Django will not be mentioned in here. See the next record - Day 2.

 

* WSL Set up ---- done

* pipenv installation ---- done

 

cd Documents

mkdir airbnb-clone

cd airbnb-clone

 

pipenv --three

code .

 

#[on VSCode]

pipenv shell #this action allows me to select and access inside a bubble (virtual workplace, like sandbox)

 

#[potential error spot] Example's Django version was 2.2.5 But, I installed the latest one.

# Probably no big problem to understand and proceed as I thought.

 

# The concept : bubble is such a good example to see how each independent workplace is needed for security reason. 

 

# This is all about using WSL(Linux) and python to interact with other stuff (e.g. pipenv for its bubble notion to create and access it.).

# Then used git for its repository connection.

# pipenv shell = to use Django properly, for the project tha I am working on it now.

####################################

[Git] 로컬 저장소에 Commit하기 :: PlanB의 백엔드 엔지니어링 (tistory.com)

[Git] 로컬 저장소에 Commit하기

* terminal command : git status # shows whether changed files are marked as staging(added) or not. By doing so, ready to commit changed content to github. 

* terminal command : git commit -m "#example"

* terminal command: which django-admin

 

# None of them will work if I am not in the bubble. (e.g. django-admin will only be worked once I input 'pipenv shell' and successfully accessed the bubble.

 

# Always use pipenv shell command if VSCode or WSL was closed. Then check by django-admin. If it works, I am in the bubble.