Giter VIP home page Giter VIP logo

metaflow-docs's Introduction

Metaflow Documentation

This repository houses the documentation for metaflow, both for Python and R.

Static documentation

These documents are published using the docusaurus framework.

Updating the documentation is very simple and there are a couple of options on how to do it, depending on what sort of change you are making.

Easy changes in the browser

Screen Shot 2022-03-08 at 12 17 00 PM

Navigate to the page that you want to edit and click on Edit this Page which appears at the bottom of the content. An in-browser IDE will appear in your browser where you can edit the .md file. Then push those changes to a new branch and create a pull request.

See Using GitHub in VSCode for more information on how to create branches in the IDE.

Running the documentation locally for more complex changes

  • Clone this repo
  • cd docs
  • yarn
  • yarn start

Any saved changes that you make to the .md files in the docs directory will automatically be reflected at the local preview page.

PR Previews

Screen Shot 2022-03-17 at 11 00 23 AM

If you create a PR, a preview domain will be created where you can view your changes. The link to that preview domain will be shown in the Conversation tab of your PR. The preview is published using Vercel.

Automatic publishing

Any pushes to the master branch will automatically publish to the live documentation pages. The publishing uses GitHub Actions and GitHub pages. You can see the progress of the publish action by going to the Actions tab of this repository.

If you forget the site URL, you can go to Environments on the right hand side, click on github-pages and then click on View Deployment.

metaflow-docs's People

Contributors

agilgur5 avatar bbrandt avatar crk-codaio avatar dasturge avatar emattia avatar ferras avatar gitbook-bot avatar hamelsmu avatar iamsgarg-ob avatar jasonge27 avatar jimbudarz avatar lothiraldan avatar madhur-ob avatar mikkolehtimaki avatar nbertagnolli avatar oavdeev avatar obgibson avatar rohanrebello avatar romain-intel avatar ryantd avatar savingoyal avatar tuulos avatar valaydave avatar yanp avatar yogeshg avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

metaflow-docs's Issues

"Basics of Metaflow" has nonfunctional example

In the Data Flow Through Graph section of the Basics of Metaflow page in the documents, the example is broken. When it is run it produces the error:

Step join is both a join step (it takes an extra argument) and a split step (it transitions to multiple steps). This is not allowed. Add a new step so that split and join become separate steps.

[Api Docs 2.0] hide the import statement if `show_import="False"`

Please hide the import statement if show_import="False"

<DocSection type="property" name="input" module="metaflow.flowspec" show_import="False" heading_level="4" link="https://github.com/Netflix/metaflow/tree/master/">
<Description summary="A Flow represents all existing flows with a certain name, in other words,\nclasses derived from 'FlowSpec'" extended_summary="As such, it contains all Runs (executions of a flow) related to this flow." />
</DocSection>

@obgibson

[Api Docs 2.0] Docs Do not show up without a SigArgs section

The following Doesn't render a the description

<DocSection type="property" name="input" module="metaflow.flowspec" show_import="False" heading_level="4" link="https://github.com/Netflix/metaflow/tree/master/">
<Description summary="A Flow represents all existing flows with a certain name, in other words,\nclasses derived from 'FlowSpec'" extended_summary="As such, it contains all Runs (executions of a flow) related to this flow." />
</DocSection>

Results in

image

It appears that if I add a SigArg component the description renders

<SigArgSection>
</SigArgSection>

But this is not desired behavior, since the presence of SigArg also adds parenthesis to the rendered object name.

cc: @obgibson

Broken 'Infrastructure Stack' image url

The link https://lh5.googleusercontent.com/f68UAR7UxClKR6XvHXq-ZeepDXLHISoVboj6amF9f0cv6jCxqTsjyYnm-isKIHdINMl\_gdlPVbR3wJ9vIDwipjMIglHwwetL3-rVNhUTRN4a7UYXmVZ78IqeI2fGJ2OA2Silk5ZS is broken in the
What is Metaflow
section of the docs, which would depict the layers of the data science infrastructure stack.

Screenshot 2022-01-21 at 10 36 25

It would be nice to see the intended image.

Improve documentation around resume

The resume command is a powerful one but a lot of people only consider it when something failed (if then). resume, however, can be used for other things and not necessarily when things have failed (you may want, for example, to reuse some initial steps and change the end). Improving documentation around these use cases may be useful to users.

METAFLOW_DEFAULT_METADATA is not well documented

The docs and templates talk about METAFLOW_SERVICE_URL in a few places, which seems self explanatory. But they don't really mention that METAFLOW_DEFAULT_METADATA also needs to be set to use remote metadata service. Took me a while to figure this out, maybe there is a way to make it more obvious in the docs?

Manual Deployment guide assumes usage of Elastic IP, but does not describe how to create it

First of all, thank for creating such an elaborate documentation for Metaflow in general and for manual deployment specifically ๐Ÿ‘๐Ÿป. I assume it can be tedious to keep it up to date, but it really helps users who can not use the Cloud Formation template for various reasons (such as myself).

While reading through the manual deployment guide within the admin docs section, I noticed that you refer to using an existing Elastic IP (Compute > Create VPC > 1. Run VPC Wizard > Step 4) , but do not mention how to create it in the first place:

For Elastic IP Allocation ID, choose the ID of the Elastic IP address that you created earlier.

While readers may figure out how to do so, it would be great if it was mentioned in the guide directly.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.