MasoniteFramework/cookie-cutterrepository is the main repository that will install when creating new projects using the
project startcommand. This is actually a full Masonite project. When you run
project startit simply reaches out to this GitHub repo, fetches the zip and unzips it on your computer. Not much development will be done in this repository and won't be changed unless something requires changes in the default installation project structure.
MasoniteFramework/corerepository is deprecated and development has been moved into
MasoniteFramework/masonite. This repository contains all the development of Masonite and contains all the releases for Masonite. If you need to fix a bug or add a new feature then this is the repository to fork and make your changes from.
MasoniteFramework/craftis deprecated. This was where the craft CLI tool lived that has since been moved into the
git clone http://github.com/your-username/cookie-cutter.git
git checkout -b develop
git pull origin developto get the current release version.
<feature|fix>-<issue-number>) and make your desired changes.
git push origin change-default-orm
git clone http://github.com/your-username/masonite.git
cdinto the directory you installed core.
pip install -e .from inside the masonite directory. This will install masonite as a pip package in editable mode. Any changes you make to the codebase will immediately be available in your project. You may need to restart your development server.
#comment above it
MasoniteFramework/docsrepo (and the README.md inside
MasoniteFramework/masoniterepo if applicable) with details of changes to the UI. This includes new environment variables, new file locations, container parameters, new feature explanations etc.
<feature|fix>/<issue-number>. For example if you are doing a bug fix and the issue number is
576then name your branch
fix/576. This will help us locate the branches on our computers at later dates. If it is a new feature name it
4.0then the previous release branches could be
developbranch is a staging branch to the next major version. So for example, Masonite will be on version
4.0. If you have an idea for a feature but it will break the existing feature then you will branch from (and back into) the
developbranch. This branch will eventually be merged into
4.1branch and become apart of the next major version when that is released.
developbranch. You will make your change and then open a pull request to the
developbranch. This is a long running branch and will be merged once the next major version of Masonite is ready to be released.