Mirror of ayon core so that FrameWork can fork it.
Find a file
2020-09-10 00:19:18 +02:00
.github Add project automation for bugs 2020-05-28 00:22:37 +02:00
docs storage is not used in pype 2020-04-09 18:27:37 +02:00
pype remove unused import 2020-09-10 00:19:18 +02:00
repos first shot at infrastructure 2020-09-09 23:31:28 +02:00
schema Cloud Mongo 2020-06-18 22:33:29 +01:00
setup first step of pype's reorganization 2020-05-25 18:20:02 +02:00
vendor first shot at infrastructure 2020-09-09 23:31:28 +02:00
.gitattributes first shot at infrastructure 2020-09-09 23:31:28 +02:00
.gitignore first shot at infrastructure 2020-09-09 23:31:28 +02:00
.gitmodules first shot at infrastructure 2020-09-09 23:31:28 +02:00
.hound.yml hound flake8 config moved to setup.cfg 2020-09-10 00:17:41 +02:00
build.ps1 first shot at infrastructure 2020-09-09 23:31:28 +02:00
build.sh first shot at infrastructure 2020-09-09 23:31:28 +02:00
conftest.py first shot at infrastructure 2020-09-09 23:31:28 +02:00
LICENSE Update LICENSE 2020-03-17 15:56:46 +01:00
pype.py first shot at infrastructure 2020-09-09 23:31:28 +02:00
README.md updated build info 2020-09-09 23:39:10 +02:00
requirements.txt first shot at infrastructure 2020-09-09 23:31:28 +02:00
setup.cfg first shot at infrastructure 2020-09-09 23:31:28 +02:00
setup.py shut the hound up 2020-09-10 00:13:25 +02:00
version.py first shot at infrastructure 2020-09-09 23:31:28 +02:00

Pype

Introduction

Multi-platform open-source pipeline built around the Avalon platform, expanding it with extra features and integrations. Pype connects asset database, project management and time tracking into a single modular system. It has tight integration with ftrack, but it can also run independently.

To get all the key information about the project, go to PYPE.club

Hardware requirements

Pype should be installed centrally on a fast network storage with at least read access right for all workstations and users in the Studio. Full Deplyoyment with all dependencies and both Development and Production branches installed takes about 1GB of data, however to ensure smooth updates and general working comfort, we recommend allocating at least at least 4GB of storage dedicated to PYPE deployment.

For well functioning ftrack event server, we recommend a linux virtual server with Ubuntu or CentosOS. CPU and RAM allocation need differ based on the studio size, but a 2GB of RAM, with a dual core CPU and around 4GB of storage should suffice.

Building Pype

Windows

You will need Python 3.7 and newer and git.

Clone repository:

git clone --recurse-submodules git@github.com:pypeclub/pype.git

Run PowerShell script build.ps1. It will create venv, install all required dependencies and build Pype. After it is finished, you will find Pype in build folder.

Pype is build using CX_Freeze to freeze itself and all dependencies.