php - Multiple apps with composer -


there main application, let's call app.

app has several dependencies (including open source projects , proprietary libraries).

there multiple clients use own instance of app (on different domains manage). of these clients use adjusted version of app. implemented creating specific module (let's call sm) each client add instance of app (so don't change of code app).

currently, i've implemented follows:

  • develop app locally, use composer update dependencies (composer update), push app on central repo

  • for each regular client, pull app central repo , install composer dependencies (composer install)

  • for clients specific implementation, create new sm (specific module), has following composer.json file:

    ... "require": {     "app": "x.x.x" }  ...

then apply same steps before sm (composer update locally, push central repo, pull central repo, composer install).

everything fine, except 2 issues i'd overcome:

  1. composer.lock app ignored sm (since app loaded library in vendor/ folder, , composer ignores composer.lock files of libraries); not @ all, not confident specific clients use exact same libraries app.

  2. each time fix bug or implement new feature in app (and happens - few times day), apart steps perform regular clients, need rebuild sms (since 1 of libraries - app - updated new version need use). overhead since of changes perform inside app (and not sm). so, if other way (app having sm dependency), have been working faster (since wouldn't need composer update on each sm).

are there known workflows or best practices cover scenario in order mitigate 2 issues above or @ least decrease complexity of upgrade/deployment process?

please note of steps above automated, question not automation part, complexity of architecture

i implemented creating specific module (let's call sm) each client add instance of app

for clients specific implementation, create new sm (specific module), has following composer.json file:

it's application client specific module (next other dependencies).

the application has module dependency (app having sm dependency).

and not: module pulls application it's vendor dependency in. cause steps take during development phase (your issue 2).

i suggest refactor application , it's modules until following folder structure:

|-application             #< application has dependencies   |-src   |-tests   |-vendor     |-framework           #< maybe application framework based     |-libs                #< more dependencies     |-...                 #< other modules     |-sm                  #< client specific module

this allows pull in dependencies, extend "the application" client-specific needs.

this overcomes issue 1, because app main repository , contains lock file. it's essential lock versions, developers bound same versions , packaging same set of versions.

so, if other way (app having sm dependency), have been working faster (since wouldn't need composer update on each sm).

yes! need rebuild module, each time change app vanish, if start "develop inside app" module dependencies.

and multiple clients, use multiple application repos, have custom set of requirements. 10 clients, 10 application repos, 10 composer.json files. run composer install no-dev pre-package each repo , place zip downloads. done.

you can use "container" or "packaging" project here, composer.json of each project include app , specific modules. might utilize caret or tilde operator specify version range app ("vendor/app": "^1.2.3") , update , repackage, after new version of application released. approach should work composer autoloading, because application remain inside vendor folder, too. little wrapper needed, set composer autoloader , switch on application.

or, if application modular. package main application , provide client-specific modules downloads. approach upgrades have multiple download steps: upgrade app, upgrade modules. think of "wordpress-style" updates/upgrades.

you might reduce complexity of upgrade/deployment process further dropping composer install --no-dev part on client machine building "client-specific application archives" on developer machine. these "--no-dev" package of application it's dependencies, including client-specific module(s) = pre-packaged.

like, application-v1.2.3-withmoduleaforclienta-v3.2.1.zip.

on dev machine: composer install --no-dev --optimize-autoloader + zip.

to install or upgrade download client, extract, execute upgrade script. done.


-

Comments

Post a Comment

Popular posts from this blog

apache - PHP Soap issue while content length is larger -

we have developed soap based webservice post data third party webservice. accepts 4 params. in 1 of parameters accepts xml string no size limit restriction put in place. the webservice works fine in local environment running on php 5.2 , apache2. works content length long 10 mb. in staging server running nginx , php fpm.we have updated max post size , max upload filesize in php.ini , client_max_body param in nginx.conf allow upto 50 mb. but webservice client keeps on loading in staging environment. gives 502 timeout , gives soap error. can me understand issue here?
Read more

asynchronous - Python asyncio task got bad yield -

i confused how play around asyncio module in python 3.4. have searching api search engine, , want each search request run either parallel, or asynchronously, don't have wait 1 search finish start another. here high-level searching api build objects raw search results. search engine using kind of asyncio mechanism, won't bother that. # no asyncio module used here class search(object): ... self.s = some_search_engine() ... def searching(self, *args, **kwargs): ret = {} # raw searching according args , kwargs , build wrapped results ... return ret to try async requests, wrote following test case test how can interact stuff asyncio module. # here testing script @asyncio.coroutine def handle(f, *args, **kwargs): r = yield f(*args, **kwargs) return r s = search() loop = asyncio.get_event_loop() loop.run_until_complete(handle(s.searching, arg1, arg2, ...)) loop.close() by running pytest, return runtimeerror: task got bad yield : {results s...
Read more

javascript - Complete OpenIDConnect auth when requesting via Ajax -

the normal openidconnect server works like: you go a.com/secure-resource you 302 server your browser handles , sends identity server you login there it sends a.com via post you logged in on a.com , a.com/secure-resource on browser. however have scenario i'm trying solve need help. the user logged in on idserver the user logged in on a.com the user not logged in on b.com we need send ajax call web server b.com (from domain a.com ) b.com configured use openidconnect. but because request b.com via ajax, user cannot redirected idserver. (all in response 302 ) we can go ahead , handle 302 via ajax (i'm still not sure whether work, security-wise). but is there scenario in identityserver/openidconnect designed these situations? with identityserver in scenario setup server b.com use bearer token authentication, need use access token provided a.com in headers of ajax call $.ajax({ url: 'http://b.com', headers: { ...
Read more