Skip to content

Commit

Permalink
small edits
Browse files Browse the repository at this point in the history
Signed-off-by: nikki everett <[email protected]>
  • Loading branch information
nikki everett authored and ppiegaze committed Jan 12, 2024
1 parent 928a264 commit 10762c1
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/getting_started/creating_a_flyte_project.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ A Flyte project is a directory containing task and workflow code, internal Pytho
## Prerequisites

* Follow the steps in {doc}`"Installing development tools" <installing_development_tools>`
* Install [git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)
* (Optional, but recommended) Install [git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)

## Steps

Expand Down Expand Up @@ -49,6 +49,7 @@ To initialize a Flyte project with a different template, use the `--template` pa
After initializing your Flyte project, you will need to install requirements listed in `requirements.txt`:

```{prompt} bash $
cd my_project
pip install -r requirements.txt
```

Expand All @@ -57,7 +58,6 @@ pip install -r requirements.txt
We highly recommend putting your Flyte project code under version control. To do so, initialize a git repository in the Flyte project directory:

```{prompt} bash $
cd my_project
git init
```

Expand All @@ -70,7 +70,7 @@ If you are using a Dockerfile instead of ImageSpec, you will need to initialize
To check that your Flyte project was set up correctly, run the workflow in a local Python environment:

```{prompt} bash $
cd my_project/workflows
cd workflows
pyflyte run example.py wf
```

Expand Down

0 comments on commit 10762c1

Please sign in to comment.