MasoniteFramework/masoniterepository is the main repository that will install when creating new projects using the
craft newcommand. This is actually a full Masonite project. Not much development will be done in this repository and won't be changed unless new releases of Masonite require changes in the default installation project.
MasoniteFramework/corerepository is where the main
masonitepip package lives. This is where the
from masonite ...module lives.
MasoniteFramework/craftrepository where the
craftcommand lives. This is the actual command itself and is installed when you run
pip install masonite-cli --user.
git clone http://github.com/your-username/masonite.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/core.git
pip install .from inside the masonite-core directory. This will install masonite as a pip package.
git clone http://github.com/your-username/craft.git
pip install --editable .from inside the masonite-cli directory. This will install craft (which contains the craft commands) as a pip package but also keep a reference to the folder so you can make changes freely to craft commands while not having to worry about continuously reinstalling it.
#comment above it
MasoniteFramework/docsrepo with details of changes to the interface, this includes new environment variables, new file locations, container parameters 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 systems at later dates. If it is a new feature name it
corerepos require unit testing.