What about merging recipes and deployer?

Question

What about merging recipes and deployer?

Closed this issue 5 years ago · 7 comments

antonmedv commented 6 years ago

subj

Answer 1 · 2019-01-17T06:04:23.000Z

And have one big repo of recipes in deployer.

Answer 2 · 2019-01-17T06:05:21.000Z

I think it will be better for project. BTW - what about Deployer CI (Pro)? It's stopped?

Answer 3 · 2019-01-17T07:07:58.000Z

Sounds good. I think having main recipes + contrib was not as intuitive as it could be and release pace of both do match.

Answer 4 · 2019-01-17T07:36:25.000Z

@asafov development is continuing :) it's really big projects and have a lot of difficult parts, but I'm working on it. As well on new deployer v7, docker support, new website + new docs. So I hope to ship it soon, but dont know when.

Answer 5 · 2019-01-17T07:40:03.000Z

@antonmedv на самом деле у меня уже была идея сделать что-то типа конфигуратора с веб-мордой для cli деплойера. У меня есть каркас для CRUD, который я могу быстро развернуть, дальше останется только загнать туда все модули.
Идея была сделать возможность прямо из морды конфигурировать в том числе и flow. У тебя такого же рода продукт получается?

Translate: i developed now web interface for deployer for own needs.

Answer 6 · 2019-01-17T07:41:33.000Z

@asafov can you show your web interface?

Answer 7 · 2019-01-17T07:49:57.000Z

https://ibb.co/nrdmMkg
For example. Builded from db properties. ACL, auth, data tables, filters, fields for edit (with types), etc.
Based on ZF2. I have idea for run deployer by gearman or any other technology and build config at the fly from databases. Arch was "Host" -> "Code base" -> "Application".
"Code base" - is unique product (by git), application is Host + Code Base + Settings.