Skip to content

conda-forge/dagster-feedstock

Repository files navigation

About dagster-feedstock

Feedstock license: BSD-3-Clause

About dagster

Home: https://github.com/dagster-io

Package license: Apache-2.0

Summary: The data orchestration platform built for productivity.

Documentation: https://dagster.readthedocs.io

Dagster is a system for building modern data applications. Combining an elegant programming model and beautiful tools, Dagster allows infrastructure engineers, data engineers, and data scientists to seamlessly collaborate to process and produce the trusted, reliable data needed in today's world.

About dagster-pipes

Home: https://github.com/dagster-io/dagster/tree/master/python_modules/dagster-pipes

Package license: Apache-2.0

Summary: Toolkit for Dagster integrations with transform logic outside of Dagster

About dagster

Home: https://github.com/dagster-io/dagster

Package license: Apache-2.0

Summary: The data orchestration platform built for productivity.

Documentation: https://dagster.readthedocs.io

Dagster lets you define pipelines in terms of the data flow between reusable, logical components, then test locally and run anywhere. With a unified view of pipelines and the assets they produce, Dagster can schedule and orchestrate Pandas, Spark, SQL, or anything else that Python can invoke.

Dagster is designed for data platform engineers, data engineers, and full-stack data scientists. Building a data platform with Dagster makes your stakeholders more independent and your systems more robust. Developing data pipelines with Dagster makes testing easier and deploying faster.

About dagster-graphql

Home: https://github.com/dagster-io/dagster/tree/master/python_modules/dagster-graphql

Package license: Apache-2.0

Summary: The GraphQL frontend to python dagster.

About dagster-webserver

Home: https://github.com/dagster-io/dagster/tree/master/python_modules/dagster-webserver

Package license: Apache-2.0

Summary: Web UI for dagster.

About dagit

Home: https://github.com/dagster-io/dagster/tree/master/python_modules/dagit

Package license: Apache-2.0

Summary: Dagster UI

About dagster-airflow

Home: https://github.com/dagster-io/dagster/tree/master/python_modules/dagster-airflow

Package license: Apache-2.0

Summary: Airflow plugin for Dagster

Current build status

All platforms:

Current release info

Name Downloads Version Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms

Installing dagster

Installing dagster from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, dagit, dagster, dagster-airflow, dagster-graphql, dagster-pipes, dagster-webserver can be installed with conda:

conda install dagit dagster dagster-airflow dagster-graphql dagster-pipes dagster-webserver

or with mamba:

mamba install dagit dagster dagster-airflow dagster-graphql dagster-pipes dagster-webserver

It is possible to list all of the versions of dagit available on your platform with conda:

conda search dagit --channel conda-forge

or with mamba:

mamba search dagit --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search dagit --channel conda-forge

# List packages depending on `dagit`:
mamba repoquery whoneeds dagit --channel conda-forge

# List dependencies of `dagit`:
mamba repoquery depends dagit --channel conda-forge

About conda-forge

Powered by NumFOCUS

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating dagster-feedstock

If you would like to improve the dagster recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/dagster-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

  • If the version of a package is not being increased, please add or increase the build/number.
  • If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers