Next generation of dotPlant CMS.
WARNING 🔥 dotplant3 is not production ready yet❗ Developers will not support you until the release is made.
It contains lots of bugs, unimplemented features and other very bad things. We don't know the exact release date for now. ¯\(ツ)/¯
- Clone a project
git clone git@github.com:DevGroup-ru/dotplant3.git
- Go to an application directory
cd dotplant3
- Run an installing of composer packages
./composer.sh create-project
- Modify configuration files
- Open
config/db-local.php
and set your connection parameters. It looks like; - Change a domain in
config/languages/Context.php
andconfig/languages/Language.php
if needs; - Create a new domain configuration at your web server and set
webroot
as/path/to/dotplant3/web
.
- Open
- Run migrations
./yii migrate
- Run a extensions activation process
./activate.sh
- Open a site in you browser
http://dotplant3.dev
WARNING
Composer working dir should always be
extensions/
.Run composer with
--working-dir=extensions/
For example:
php composer.phar --working-dir=extensions/ update -vvv
Assume that your dp3 app is located at ~/git-my/dotplant3
and all other dev packages are in ~/git-my/*
, for example ~/git-my/yii2-deferred-tasks
.
- Create
dev.composer.json
- you can use an example file - All local packages with
../../
todev.composer.json
as path repositories. - Run
./composer.sh update -vvv
- Now your vendor packages symlinks to your working dirs.
Note: double ../
is needed as composer working dir is extensions/
.