https://github.com/h-REA/valueflows-project-metarepo

[OUTDATED] Metarepo that links and initialises all dependencies necessary for full-stack development of ValueFlows-compatible apps. Built for HoloREA initially, planned to extend beyond.
https://github.com/h-REA/valueflows-project-metarepo

Last synced: 3 months ago
JSON representation

[OUTDATED] Metarepo that links and initialises all dependencies necessary for full-stack development of ValueFlows-compatible apps. Built for HoloREA initially, planned to extend beyond.

• Host: GitHub
• URL: https://github.com/h-REA/valueflows-project-metarepo
• Owner: h-REA
• License: other
• Created: 2019-11-11T23:29:32.000Z (about 5 years ago)
• Default Branch: sprout
• Last Pushed: 2022-09-11T18:52:53.000Z (over 2 years ago)
• Last Synced: 2024-09-01T14:02:49.492Z (5 months ago)
• Language: Shell
• Homepage:
• Size: 11.7 KB
• Stars: 2
• Watchers: 4
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-starred - h-REA/valueflows-project-metarepo - [OUTDATED] Metarepo that links and initialises all dependencies necessary for full-stack development of ValueFlows-compatible apps. Built for HoloREA initially, planned to extend beyond. (others)

README

        
# Warning: This project is highly outdated, and code should not be expected to run currently

# ValueFlows project metarepo

This repository exists to orchestrate setup of the full ValueFlows stack, including (for now) a Holochain backend.

**To begin, just run `init.sh`.** Now, go make a coffee while you wait 'cos this will take a long time.

If you contribute only to one of the projects mentioned in `.gitmodules`, you do not need this repository. It is for developers working on HoloREA, `vf-graphql` and/or `vf-ui` simultaneously, who wish to be able to test changes across different projects without having to publish everything to NPM and crates.io.

Note that it is expected to see output like `(modified content)`, `(new commits)` in the `git status` output for this repository. This is because `init.sh` is used to bootstrap all repos from their master branches, and the versions of the modules tracked within *this* repository are not typically kept up to date.

You should deal with every submodule provided by this repository as its own entirely independent git repository, just as if you were working on them individually. Don't fiddle around with this parent repository unless you really know what you're doing (;