GithubHelp home page GithubHelp logo

eltonlazzarin / monorepo Goto Github PK

View Code? Open in Web Editor NEW
8.0 0.0 2.0 413 KB

Simple folder structure for Monorepo architecture

License: MIT License

JavaScript 19.65% HTML 1.21% TypeScript 11.47% Starlark 3.33% Java 34.23% Ruby 3.52% Objective-C 26.59%
monorepo-example monorepo nodejs nodejs-server react reactjs reatjs-app web-application react-native mobile-app

monorepo's Introduction

Discord logo

Simple folder structure for Monorepo architecture

GitHub top language GitHub language count GitHub last commit GitHub issues GitHub

About The Project   |    Technologies   |    Getting Started   |    How To Contribute   |    License

👨🏻‍💻 About the project

In revision control systems, a monorepo is a software development strategy where code for many projects is stored in the same repository.

So, I decided to study and I created a simple monorepo folder structure.

🚀 Technologies

Main technologies that I used to develop this frontend app

💻 Getting started

Requirements

Clone the project and access the folder

$ git clone https://github.com/eltonlazzarin/monorepo.git

$ cd monorepo

Follow the steps below

# Install the dependencies
$ yarn i

# Run the web app
$ yarn start

🤔 How to contribute

Follow the steps below

# Clone your fork
$ git clone https://github.com/eltonlazzarin/monorepo.git

$ cd monorepo

# Create a branch with your feature
$ git checkout -b your-feature

# Make the commit with your changes
$ git commit -m 'feat: Your new feature'

# Send the code to your remote branch
$ git push origin your-feature

After your pull request is merged, you can delete your branch

📝 License

This project is under the MIT license. See the LICENSE for more information.

monorepo's People

Contributors

eltonlazzarin avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

monorepo's Issues

Proposition for cross functional teams

Hi, I'm really happy to find to something like this. I've been giving a lot of thought on this lately.
I just needed your thoughts on this.

Take an hypothetical team of engineers that are organised based on certain feature that would be deployed both on the backend on client applications (web, mobile and via public APIs). So each team is responsible for the servers and client packages. How would their organise the code to reflects their team while allowing easy sharing of common packages between teams. Example would be a hashing library or a Hero component package.

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.