dev
branch#43
)[Fork the repo if you are outside collaborator.]
$ git clone git@github.com:iluminar/goodwork.git
for outside collaborator
$ git clone git@github.com:{yourusername}/goodwork.git
$ cd goodwork
$ git remote add origin git@github.com:iluminar/goodwork.git
Docker & Docker Compose must be installed
a) Copy .env
from .env.example
cp .env.example .env
b) Define environment variable
Set app port, db credentials and mail driver credentials in .env
file. Also provide SSL_CERT_DOMAIN
(your domain) and SSL_CERT_DIR
(directory of your ssl certificates file) values for ssl setup.(Not needed for local development)
c) Run the installer
sudo chmod +x install.sh
./install.sh local
To stop server:
./cmd stop
& to start server./cmd start
Login Credentials for Admin User
email: admin@example.com
password: secret
$ git checkout dev
$ git pull origin dev
$ composer install
$ cp .env.example .env
$ php artisan key:generate
$ npm install
dev
branch latest commit (the branch name should be as “issue[number]”. E.g. – “issue7”):$ git checkout -b issue[number]
$ git add .
$ git commit -m "commit message"
$ git push origin issue[number]
$ git fetch origin
dev
branch:$ git checkout dev
$ git pull origin dev
dev
:$ git checkout issue[number]
$ git rebase dev
$ git add .
$ git rebase --continue
$ git push origin issue[number] --force
$ git diff issue[number] upstream/dev
$ git branch -D issue[number]
$ git push origin :issue[number]
N.B:
master
or dev
branchfeature
branchfeature
, rather give it name of your task id e.g issue7
dev
branchAdd delete user option in the dashboard
Or like this
Replace jQuery onReady listener with plain JS; fixes #13
- Add issue number in final commit message when the task is complete
Goodwork follows the PSR-2 coding standard and the PSR-4 autoloading standard and StandardJS style for Javascript file StandardJS.
Notable changes in source file should be recorded in CHANGELOG.md
file.
Format of the record should be like below
## Version no. (Release date)
## Change
- Message [Issue no](Issue url)
Types of changes
Added
for new features.Changed
for changes in existing functionality.Deprecated
for soon-to-be removed features.Removed
for now removed features.Fixed
for any bug fixes.Security
in case of vulnerabilities.