-
Notifications
You must be signed in to change notification settings - Fork 674
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
updated getting started page with correct instructions (#147)
- Loading branch information
Showing
1 changed file
with
4 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,15 +9,16 @@ The easiest way to author a Flyte Workflow is using the provided python SDK call | |
You can save some effort by cloning the ``flytesnacks`` repo, and re-initializing it as a new git repository :: | ||
|
||
git clone [email protected]:lyft/flytesnacks.git myflyteproject | ||
cd myworkflow | ||
cd myflyteproject | ||
rm -rf .git | ||
git init | ||
cd python | ||
|
||
now open the "Makefile" and change the first line to ``IMAGE_NAME=myflyteproject`` | ||
|
||
Let's also remove the existing python task so we can write one from scratch. :: | ||
|
||
rm workflows/edges.py | ||
rm single_step/edges.py | ||
|
||
Creating a Project | ||
****************** | ||
|
@@ -36,6 +37,7 @@ The most basic Flyte primitive is a "task". Flyte Tasks are units of work that c | |
|
||
Start by creating a new file :: | ||
|
||
mkdir -p workflows | ||
touch workflows/first.py | ||
|
||
This directory has been marked in the `configuration file <https://github.com/lyft/flytesnacks/blob/764b82aca5701137ebc0eda4e818466e5acc9219/sandbox.config#L2>`_ as the location to look for workflows and tasks. Begin by importing some of the libraries that we'll need for this example. | ||
|