You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: en/cloud_development_setup/instructions.md
+10-16Lines changed: 10 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -34,30 +34,24 @@ $ mkdir djangogirls
34
34
$ cd djangogirls
35
35
```
36
36
37
-
We will make a virtualenv called `myvenv`.
37
+
We will make a virtualenv called `myvenv` by running `python3 -m venv myvenv`.
38
+
It will look like this:
38
39
39
-
To create a new `virtualenv` on RunCode, you first need to install the `virtualenv` module. To do so, first you need to update
40
-
the packages in your environment
41
-
>```
42
-
>$ sudo apt-get update -y
43
-
>```
44
-
> then install `virtualenv` by running the command:
45
-
>```
46
-
>$ sudo apt-get install -y virtualenv
47
-
>```
40
+
{% filename %}command-line{% endfilename %}
41
+
```
42
+
$ python3 -m venv myvenv
43
+
```
48
44
49
-
> After this you can create the `virtualenv` run the command:
50
-
>```
51
-
>$ virtualenv -p python myvenv
52
-
>```
53
-
> and a new `virtualenv` with the name `myvenv` or whatever name you chose should be created in your `djangogirls` folder.
45
+
`myvenv` is the name of your `virtualenv`. You can use any other name, but stick to lowercase and use no spaces. It is also a good idea to keep the name short as you'll be referencing it a lot!
54
46
55
47
## Working with a Virtual Environment
56
48
>Start your virtual environment by running:
57
49
>```
58
-
>$ . myvenv/bin/activate
50
+
>$ source myvenv/bin/activate
59
51
>```
60
52
53
+
Remember to replace `myvenv` with your chosen `virtualenv` name!
54
+
61
55
### Installing packages with requirements
62
56
63
57
A requirements file keeps a list of dependencies to be installed using
0 commit comments