Bestand wählen
Merken

Dependency Management with Composer: PHP Reinvented

Zitierlink des Filmsegments
Embed Code

Automatisierte Medienanalyse

Beta
Erkannte Entitäten
Sprachtranskript
I have a 1 and what into dependency management with composer a PHP reinvented the world that things that I am news and I I wanted the co-creators of composer and I also work in a number of other open and free software and 1 of them as a pH GB which I think a lot of you probably heard about at some point as well and and I work informatics and as engineered is kind of to sponsor some of my work on composer these days but as we've been trying to come to a some uh a point where we can know more where spend more time on actually supporting this opens was projective certain about that as we're trying to come up with some ways of financing or and the amount of time and of spending this project and let me I start by talking about you package management dependency management what is that even are you all of you probably at least use a couple of these on the slide this is just the friend mechanism and tools I use for managing packages of managing soften managing libraries in different environments i you think the standard than existed tools but a lot of language environments come with some standard tool was used to install packages on so I think no way to think about but no JS without thinking about and GM mystical I go hand in hand for example I and for a long time a huge he had a couple of not quite so fun the tools to do similar things but I is the always movies was a copy and paste it was only because I use for it used to be for a very long time away that people would actually installed libraries into the project know them of the pulse they can in there somewhere on boy maybe Donald is a file extract some directly from a digital 1 that whole project that's you know not offering individual packages but rather used to some huge monolithic of applications and it was a one-time some worsen was pretty popular as eunuchs trials was willing 1 of the things that was actually used quite widely in the PVC beats the world and has always been there and and can it curious I just to make sure it can occur in who here has used composer before it was finished everyone OK map so the things I wasn't quite sure what to prepare for something like jump through some of the introductory stuff will pass think that everyone knew narrative and and who has used who used on something other with peer then install pH units i still a couple people but a smaller amount of people as having 1 of the main issues with parent that I that has little complicated to use for anything other than those couples standard packages available at this period can describe lots of things at the same time adjust the installer that composers today but also the way particularly library of the components and so the particles so the solid composer actually come about and I mentioned earlier that a I work and PHP BB and we actually set out to build a new plug-in system for the forum after and this was around the same time it was added to start working on porting kitchen into Symphony or making more use of Symphony components to his are just releases the 1st preview all release but research on those people and then you realize that a lot of the same problems and you know you think about it as it was the before but image and you suffered developer anywhere has this problem of having to install different suffer in China is like where other trying modulus modularized of their suffered having need some way to describe those dependencies between packages as a rather than actually of builders plugin system the ended up creating composer the inched the we look at the Our composer consists of a number of different parts so you will probably use the of the COI to compose which is the thing that you can solve things with them and the interesting part is that this is really a very thin Sealife clients on top of a library is as there was pointing out earlier how we actually build this for should be to be a plug-in system of samosas functionality actually used as a library without having to use the CLI tool and more recently we've started to see some pretty interesting projects making use of this uh certain plus plug-in the tools for applications 6 and block tool that installs plug-ins uh making use of this without having the user actually use the composer CLI tool of which just making use of the lobby to install dependencies for a particular application come and 1 thing that we are tread encourage with the CLI tool and we always like to now talk quite a bit about because I think this matters a lot more than what the told cell does is standards of interoperability between different PHQ projects packages because I'm sure there's some told install this waiver they don't work well with each other what's the point and so we tried and for certain standards that help interoperability and I'll get into a couple of these later on and this packages which ensure all users composer before but seen before as well as just the open uh that is open to anyone anyone can submit packages there and it the part that I wanna point out here is all get the went is doing is that the entirety of packages is based on this idea of feeding directly off of BCS repositories so there's no bill process there is no coupling packages 2 packages there's no creating versions some packages all of the information that you find on packages is automatically read the red from the composer configuration files on and the respective repositories and there's satis I'm curious to use such as before this is hopefully smaller of people because present and explain how it actually works and how to use that and success the is your way to host a on repository of packages so if you don't use just those open packages available on packages but you have maybe your own private Rebecca packages on here all depositors somewhere and war the as a kind interesting to train a proxy of the composer repositories so if you don't want to rely on packages being available all the time if you don't want rely on down being available from the use of you connection you status that you download a partial copy of packages there is that you use yourself and if you're trying to install your own projects using this you are no longer required to rely on the availability of all our open repositories and and lower thing we will never is a torrent proxy that I mentioned earlier that we're trying to come up with some way of financing our sustained look like involvement in composer uh and for proxy is a tool similar to status a little nicely were more user friendly in that it has about user interface which makes it a little easier to do what I just mentioned proxying packages partying get hum storing temporary copies of the information on and publishing their own the private packages and this is open-source are not in the free sense that we usually like to think about it is free for personal use the I am however we do ask for for commercial use to pay for simply to support the Open source suffer it does come with a full copy of the source code which you can make modifications to answer that simply like a new tool that we offer in addition to status with which which is fully free and open source software and with which makes a couple seems a little words differently answer judges needed these you might wanna look at that as well if you have some commercial use for this and another 1 I mentioned is a composer installers and isometric this list I have not been wells from a gun even longer anything even when it reduces it wasn't quite as long as there is already a lot and what's on there and this is a number of projects better quite widely used that Our can all have their individual modules plug-ins is that are installed with composer even though they don't follow all of the standards for interoperability that recommend that using a specialized installation tools and about the individual paths and installation steps necessary for all these tools as soon as using like any 1 of these and you'd like to automate some of the installation plug-ins models for these you can use composed Oslo's just a quick overview of what i imagine most of you have heard about most of these before but you also use composer this
juntas you quickly and there's the installer that that like that I was like to point as I was is a little curious that composers and something that usually just downloaded file or and should I hope this is like a large enough for everyone to read was a little and basically you download it and install a script and papers into cage and the background behind this is that we should composers of far file and these there's still a number of configuration flags that make far files difficult or impossible to execute and when this does happen it doesn't give you any error information and so we don't recommend that you use down on the far from set amount a double page will give you this little piece of code to run on your shelf to install composer what all of this is really down was found check for those configuration settings to make sure that you can actually rank was properly and gradient composer installed thing was of you use composers you've seen this before and solves bunch of packages that you end up with a vendor directory that contains all these different folders so this is the part is different if using of that was installers than province sticking in their it'll stick them in the respective directed at the political project and so and this is what a composer Jason look like that defines the dependencies and a kind of interestingly this has to be in the of root directory of a project as a limitation that wasn't necessarily intended to stick around forever has led to a little but there and there's some interesting aspects like the symphony framing that consists of a lot of components the current standard way to have a single repository and and including a number of packages is actually to create but never repositories feature them because you still limited having this composer decision in the root directory of your repository at the outset of this is that it's a lot easier to understand most of packages and that they always follow the same structure and so like an oven and answer to this so and you get slow more interesting so even if use composer before I'm much further again they think a CIA misconceptions about this a lot a lot of people are entirely sure when these different files do composer Jason everybody's standard touch at some point to define what dependencies the project has I'm in any of those vendor directly things and up in but there is a step in between is the composer that locked file and D. is a generated file that you don't touch yourself it gets generated initially were running a composer up data installed them and as soon as it exists you can only after the wall fell using composer opted while the composer install command tries to install the contents of the log file so there's these 2 key combat commands that composer offers updated install and as the relationship updates goes from being Jason fall to the log file and then runs in style and install simply goes from a locked file to the vendor directory you can I use various options to influence the process of how the log file is updated specifically and get into the uh later but there's also a couple relatively unknown once they're pretty useful for certain situations but the key part is really understanding this life cycle of running install whenever you just try and you get whatever the dependencies the project has and running update if you try and actually change the words and of any of the dependencies and the actual worsens are document in the log file while the uh Jason fire well but simply defines a range of reasons that the pieces of a should be compatible with that the the lockout only applies the project that you're working on so if you're installing a library the only thing that matters is the origin constraints defined in the Jožef 0 the based on these dependencies are resolved in your own project receives a lot farther defines the precise versions of all your dependencies however the log file is itself is only applied to the the individual project that you're working on as is the point of all of us but well 1st of all please always commit this file into uses president AID realize the visibility a discussion over this is something that's been discussed a lot of communities this is likely lose no there at this came from but under in the real world and there's really no downside to committing it the result is that say work on a project with a all of you if you run composer install get the exact same origin of all dependencies you don't just get any worse now matches the constraint but you get the exact same origin so somebody published a small release for 1 of your dependencies but this could result in some difference in behavior that you need to a fixing your code but some co-worker of URIs might be trying to just get the project running and then for some reason they get this new version because they're installing it later than the person who checked in the log file as the checking of both adjacent dividend check in a log file and that consequently and they end up having problems with their code simply because they have a different version of the same code and so this process makes it very explicit when you want to switch to a different which you have to explicitly run composer update and only 1 member of a team does this and all other members of the team uh have those exact origins that all you're working with all you know that the test run with and the next step is uh doing this across servers if using composers part you deployment process then you want to make sure that all of your service around the exact same versions of all dependencies you don't want them to just run any of the words that you think your suffered should be compatible with 1 of a certain that it runs the exact same versions so again blocked fall comes in to make sure that you install the specific portions rather than anything that matters and again if you're supplying an application to users the uh all of those will have the same words the figures compose themselves to install appendices you a question Mr. this was so yes it does so this is the point of parabola people always get confusing because they've I did point out that the log file is only useful to the project that you're working on so if you're working on it or if somebody publishes a library why would they include a lot from the library because it doesn't apply to the user of the library but the user of the library is number 3 here number 1 and number 2 is still both interesting for libraries because there's a group of people working on a library and they all need to run tests now you want to be able to verify that a particular bug is based on a difference in Gaussians so if someone runs into that he doesn't use a log file another user reports about dance the library you don't know whether this is the cause of the proportion of a dependency being installed a a a bug in your library so instead make sure that they all use the log file and if you wanna run tests against a different words and is composed there to test different words and and then part of the book reporters we made the following change to the log file and you can verify that the bride is actually part of this particular dependency change so yes even if you're working on a library should be committing airlock fell for other people working on the same library I and the server part really applies only in so far is that it's interesting if using continues integration but you can I want that continuous integration service to uh test yourself there with reliable origins that you know which they are and you may you may as part of your testing infrastructure actually installed different words and so dependencies or get 100 that and that as well uh but you do want to a the deterministic with us and you don't want to have random versions installed that you can't later verify actually Poseidon compositions
right next for that compose it as as a command and installs all those various into the vendor directory an important composer Jason is an order loading section which makes use of features Ottawa and there is a new thing here which is peers for uh that replaces the old Pisa is 0 loading standard he is a 0 is this mapping of class names of namespaces in class names 2 directories and violence and Inc user for uh this is become a little simpler because you can skip common prefixes within projects you end up happening is that the 2 but the user namespace of some company named large the particular project back so the particle project backslash this 1 component backslash in this subdirectory by slows the actual cost to with huge pass you for everything even the most of the actors containers everyone subdirectories so that the idea behind user forced to simplify these directory structures and you can simply specify the prefix namespace in your composer Jason and then all of the classes in there are assumed to have this namespace is a prefix free the and get the OLA
ends up in mineral a PHP and again since this view views composers you simply regarded as 1 value cancer using all the possible dependencies and there is a command to G regenerate the sort order especially using a wide class map for some project that doesn't polkas are 0 appears so for of which means that you generate an explicit list of all the classes in the files or directories that you listed are then you will need this command regularly to update this was that he added in files on and namely there's 2 options no deaf and optimize uh that you should be running if you dump a novel water for reproduction system are optimized generate such a class 4 cases ZeroMQ user for autoloader loaded directories as well which makes the lookup passes it doesn't have to actually search for the files and and node of uh excludes all development requirements of from the order loaded so even if you do install development requirements in this way you make sure that the they're not being modeled and reduce in the Ottawa in size direct so 1 understands that a
certain and this something that is if things were reported to me that a lot more developers take too hard and that's where wanna focus on this for that what is semantic worsening our semantic reasoning is this concept of having a version numbers consisting of 3 digits major release minor release and actually some 1 . 2 3 in which the patches these is exclusively for but faces the minor release should be incremented whenever you include new features and every breaking API change should include that increase the major release the authors of libraries strictly follows standard it makes it a lot easier for users of those libraries to require the correct abortions and to a builds were directed to define a future proved worship constraints as a public is a just a walk through example of how this works and Development mission could be 0 1 0 you fix some biconnected 0 . 1 1 you make some breaking changes is an exception because we're still in development of 0 point so the breaking changes lead to 0 . 2 0 uh and then you decided to make a stable release the first one is 1 0 0 I make some fixes 1 0 1 as more fixes 1 0 to include some new features 1 kind of my 0 and then you make any breaking changes and its 2 0 0 the lots so that's of semantic worsening works and now I wanna get a bit into the details of how the precisely take origins in your compose is and there is a few pretty obvious ones that is exact match constraints we simply specify the particular region that you're looking for elegant of these but you can use ranges of possibly use an asterisk in a place so this would include simply 1 . 0 point any about 2 . anything the price of X and you don't comparison operators in but please don't use just 1 of them and they were in constant so if you're doing something like greater than or equal to 1 . 0 you basically saying that your library is going to come be compatible with any future version of this particular package and that's a very unlikely to be true statement uh like a I don't I don't think I've ever heard a stopper that was compatible with any future where of another piece of suffer and please FIL free use these operators but combined them with others there and this and and or operators written constraints and you can combine but to these constraints greater than or equal to with less land using an and operator and you can also use an or operator and if for some reason it is 1 particularly that was bad idea suffer is not compatible with you could use to comes to ranges and combine them with there is the more interesting operators but it is a little more tricky to understand where I called next significant release operators and this until the operator was the first one is to and you right till the 1 . 2 and this means uh at least assertion 1 . 2 which extends to worsen 1 . 2 . 0 and then up to worsen 2 . 0 0 so if you ditch trying to describe a words in constrained related to the semantic worsens earlier on let's say I want to be compatible with always ends up until the next 1 breaking it API then you can use 1 of these operators to say that you be compatible with any new features but you won't be compatible with any breaking changes and any gets a little more specific if you add 1 point of entry that is only goes up to 1 . 3 . 0 and this isn't but precisely what the semantic version being defined anymore because the says and compatible all uh fixes but I'm not compatible with the new feature which is unlikely to be an issue and so as of think about 2 months ago that is a new operator that more strictly adheres to the concept of cementing of reasoning support went would work the same way but for 1 . 2 . 3 it's still only goes up to origin to so that the carrot operator scan would you wanna rely on if you know that your libraries that using the following semantic worsening because you can specifically state that you will be compatible with any future releases untill they make API changes so if you're building a library yourself and that's when it's important what the constraints are you should be using 1 of these 2 operators because if you're building an application that you're delivering to users the new files important to make sure that users get the right words and to building a library so that other users depend on your on your constraints to match for the dependencies they have and is use these operators so that they don't end up with which is that don't actually work with each other part of the next part of that which word sense of which libraries you end up with is stabilities so we how origins in like the number and and there's a composer stability is and that our development of this kind of a flat for each of these so
development mode is it's an alpha release better these are services still release these automatically red Odinga brothers of early on like packages as well as sad as they all read this information from these respective BCS repositories so the way that you make it releases by tagging it the war even branches are available as versions and composer and CG tagger and 8 2 . 2 0 . 2 would automatically detected as a stable origin and while this better in there is a suffix even with the number after it it'll be detected as a better release a similar thing happens with branches that we traders is automatically and is intuitively as possible and if you have a badge goal to ban 0 and then the version we take this as is 2 point x that so the developmentally is a like any other ranch is the masses usually available as DAF sludge map at death Dutch master and the same applies to all other branches so if you create any future branch on your repository these actually become available through installation with composer this is pretty useful in development if you trying to and you know you wake up and try out a new feature that you working on in a library in your application then you can actually requires particular branch that you're working on rather than having to tag a specific worship rely on this no on the recording site in your composers is an attorney use any of these but by default a composer comes with the minimum stability of stable that means it will simply discard all Gaussians that are not stable have you tried using any of these other stability is you can either simply increases your minimum stability so it's say to better in this example which means it will no longer discard better well-received releases out we can set this to Devon will simply use all releases available and this will apply to and all the constraints will then apply to these releases as needed to separate concepts are 1st it discards we said in a discourse particle versions releases and then applies the constraints on these at however you can also explicitly state in the stability that you want for at 1 particular packets of saying I would like to install this particular package in inwards among print 3 but were above but I do want include alpha release is that you can use this at all for flagging composers were and that is in the 1 below and this is simply a suffix to add to the worship constrain defining composer edges OK so this is the way that you define all of the different dependencies you make sure that you know all of the Virgin constraints met and then use composer update jeopardy a lot of and is a couple of command line options that are interesting we get to know the first one is was promised a pretty common if you win anything production use no doubt of to make sure that you're not installing any development requirements nobody faults is that you're installing development environments and that it prefers to install them from source which means it will try if if possible to install to get close to as the and check out and to give you a a BCS repository for your dependencies so that you can actually go into this when a directory may change the files in there and commit them so it's easier for you in development to work on a number of projects without having to each check that check each of them out individual this makes that typically a little slower and so in production is easy to use and pick the preferred this which will try to download the files are available and prefer stable i is and option that influences which worsens get selected because it like early let's say we use a minimum stability of better and there is a better version for something available it's newer than a stable words and that would also match are constrained than this better version would be installed if or are we only 1 the better really to be used if there is no stable available then we need to use prefer stable which for all users still worth of available but still allow for the Belarusian to be installed and that is the minimum stability and the last to a pretty new options of and added only this in last month I prefer lowest will try to install the lowest available worship matching aversion constraints as a really useful thing protesting is you try and ensure that your and constrains actually or so correct that resulted does still work with all these old words that your listing in your version of constraints and then you should be using refer lowest as part of your testing to ensure that your test so run with all these always and the last 1 in their last what ignore platform requirements allows you to install a package even if the words and constraints for peace peace engines Dutschke itself I don't match which comes in handy if you have a project that runs on a particular set of that you may have a bigger and walks for but you just put the 1 that run this 1 particular test has nothing to do with all these extensions on your local machine we don't have the right words of those extensions so you can still install all independencies without it failing for promising extensions were inward extensions right so as promised
earlier I wanna show you how to use as an is really straightforward I you simply news composers building create project command where you check of the git repository directly but you end up with a copy of status but into which you put a a file you can name are among the typical things to call set chosen something Jason and and this contains a list of repositories similar to what you can do and compose adjacent to define your own BCS repositories field packages from your sat configuration file contains a list of the repositories that you would like to lure packages from and the default behavior such require all of explicitly written here which means that all the packages a confined any these repositories will be published on his edits repository the alternative down here is that you explicitly listed versions that you are interested in publishing on a repository that using requires similar to compose adjacent as in this case a package package to would have all the Gaussians published but package we would only publishers in 2 0 0 you I'm a further In this configuration you can use the archive command that's a by default status looks at these repositories generates the metadata so that your composer and so can make use of his metadata but the download will still go directly to the BCS repositories that list and I C 1 xt builds car files for these Gaussians and have them downloaded of HDP rather than always having to clone that good repository that you can use the aka commands so that status will automatically also build all of the different packages for the reasons that you need and the prefix URL is the uh is the URL under which those pages later be available so a status will dump these into a local directory and then you need to make sure that this is available under this URL so that users of the repository can actually reach these and he's given them the option last when there as and the allows you to skip over branches when building packages so branches always installed from the repository and then building it is simply a call to the bin set a script that's included and status but with the directory that you're trying to build into which is web in this case and then you make sure that this is available on the web so you can also serve as over ssh you can I really for anything that you like I just make sure that is somehow ritual and on the other side in your composer Jason neutral because repository the top composer a composer repositories is just a Jason file listing all these packages for example I just set is generated by any particular URL so the that example it or that were if you wanna make this available system want to all of your packages or projects that you work on you can't use composers config file which is in things will too small inductive in your home directory . composers less config Jason about war the notions of the public look at 1 site that a little long and you can use list the er repository that you like to use in there and then all of you the projects on your system will no dependencies from this repository so it's pretty straightforward that's say in you in a company working at a set of a repository like this for everyone to use without a long hassle without having to manually specify those repositories right so there's another party to
talk about it so that elements of was based Paeschke reinvented so for this which is In lots of composers of others all this work and anything there's a couple talks there ready so try to like a certain this part a little bit that covered both the all the new developments in my how peachy but is being written how these projects are laid out out 10 of new things are happening in the language but 81 improving tetanus and the 1st thing we condemn I
say this is like to be done a dependency management reinvented like but obviously composes a new tool and and I think the the most important point what composers change to how people approach dependencies in future projects is that we no longer have a tool that you use to make state changes so it's a with pair you install a particular package you to do is manually download the the lessons and follow it fixed but the it's so extracted and then you have a there and you have you had processes that change the state of your project but now instead of the composer Jason file in which you define the overall system state media trying to reach In the composer Jason and how you manipulate it has nothing to do with the current state of the system it doesn't matter was currently in your in the directories and defining a stated you would like all of you dependence is to be and then you have a tool that ensures that the state action matches this description and so the the per the overall process of his work has changed and this sounds a little familiar to you this is the same thing that the tools like public shaft and all salt been doing for a server confirmation a server management server configuration management and it's a that a process that's become a lot more commonly used because it's easier to wrap produce more predictable and I think this is helped to that PHP key to make use of this a lot more because it does make the whole consul more approachable more easy to use and you can see this if you look at some
statistics so this is the the citizens the publishing packages I'd have to read the numbers of there's you see the graph and how it expands out we have over 50 thousand PhD Isabel and practices so so you know if you're if you're looking for something to probably on ready to trainable something you maybe take a look this is probably on their already so there is over 200 thousand words and these packages we have reached a point of over 15 million installations month part of individual packages and so the PHP world as and taken by storm but this concept of being able to install their dependencies in such a predictable and easy way so are so as get back to like
PHP reinvented and anything there's a couple of goals that people had in PHP projects for a long time and this is in making API as simple easy you easily approachable of improving code quality at the end having a large amount of modularity visibility of individual components of the code and some of the WIC programming suffer engineering methods of achieving these on the you know better separation of concerns the depends injections and there's become really popular in the cage the world to make it possible to do couple individual components that things like events make a possible uh to interact between components without strongly coupling them and the yeah designing sufferer testability in mind at least over is similar the coupling component creation of components and these suffer engineering process of the methods on 1 side and of composer on the other side as a tool that allows you to now actually package up these individual components so that you no longer have to do this is part of 1 mass of cold but you can actually would as individual packages the and the result of this is a series of new frameworks you simply to was the very beginning of this process as things like Laura bolus highlights something like solids wasn't previously is possible with PHP and it simply makes use of a number of these components of 1 of the existing frameworks to build a new framework as was really easy now to just create a new framework based on a small part of another 1 because you can easily take all those parts on previously would have been a hard job to even seperate these things so the combination of all these engineering changes of all the the differ methodology that people use to program PhD build more maintainable more component offer goes hand in hand with the possibility of actually using these as individual lectures that we have a lot more single-purpose libraries it no longer all his big applications that do everything that we have a lot of small libraries do particular specific things like acetic guzzle a connects to keep clan monolog logging library and and that helps you in creating new applications making use of these individual tools for a specific things they're trying to do the an older all all of this has led to a it's a faster innovation cycle is something you notice in PHP overall but I do think that all of these In changes are interlinked they they they led to a faster development of the language and there's a lot of factors into anything that these but the increase in speed of new projects new ideas and how fast you can build them based on existing code from has also led to changes to the overall environment in which PHP is written the act of language itself even the so this is going away like you to do from now on you work on a new project the 1st thing is look around what's out there ready our is in there may be some that ourselves part of my problem and then and try to not address all these problems at the same time but right some of these single-purpose libraries solve 1 particular problem that you like to work on and publish this 1 particular small single-purpose library afterwards and then others can reuse the work that you put into those just as you reuse their work and through this process we will further increase this innovation time people reinvigorate pitch as couplings that you wanna find market composer August the composer documentation pages that organ mentioned earlier you find all the code for composer projects on GitHub and there's some uh go groups for a discussion of the users a development and is also to ISI channels that you can find the help on or discuss things so burning composer figure on few or anything brought roughly 5 unit of and you can also do 1 and literally at made amendments as more questions afterward so I think this 1 has to do with mites furthermore is review the of the management of the mind the that would be what look as is saying there's a a river is a package that doesn't actually contain any code but simply conflicts with a lot of origins and the purpose of this is to a conflict with insecure of various offices you make sure that you install this package will have a conflict with any word and have a package it has a a security issue I she was in this but it seems like a very of straightforward way of doing this of the individual the package maintainers so use that library don't update their dependencies specimens and you can obviously do this yourself as in like like was worse than 1 have installed but I think that's probably pretty good there the the I think it's the role as a are always slashed OK that's the organization is look at ROAD is securities of another let me know that as a question like the rejected they use and OK so the question is is there a way to find out who is using your of your library that through peg adjusts API and so use in a sense of who is using as installing obviously not because we don't want people to your however but if you allow yourself was to hazardous compose itself actually comes with a command now that can let you know what the dependencies of a package or other 1 and the inwards dependencies so you can check 1 depends on this particular package which makes use of packages API to give you this information and there's also you have so-called version i . com but which has a lot of information about how it is that some users packages and graphically displays this power you can see which other of open source packages depend on this point is that you looking at and they do think there's like 2 or 3 other projects try graph some of the information packages of which I don't know the names of the top of my head but you can certainly find some of these
the couple ways to do that the I have the questions following lecture the chart we all the effect of that but right so as time was as I said the packages is growing and growing is I like his projects and its dependencies or 2 so the ends of the composite is involved has more and more packages and this becomes a livable to maintain as well and yes you actually suggested the answer but you can trade middle packages so a composer Jason larger publishing package has a type that defaults library mization a type called middle that means that you have to it doesn't contain any source code is simply a description of the package this package can have a requirement on a list of packages that summer logically belong together and so and maybe I have my typical web out package that includes like the frame aligned using the template engine using without a couple other things and then in my projects I simply require this meta-package wasn't hasn't really requirements to all the the individual packages that only and through that I can actually consolidated of ribs packages or dependencies into individual composer packets are and further questions 1 of the rotation 3 years of and you you you you you you you you you you look do you know who you are and you have to do and you know you and so on so this is a bring up to uh to issues of with that he sees the composer and a thing is like a typical perspective and I mentioned you may work on 1 of these distributions of package managers sorry I'd like tennis and so the the first one was I have to have a go with the 1st thing about the 2nd 1 too much as a narrator so composer doesn't have any signing currently and the yes a dozen and yes we do actually initiated however I and all of the traffic runs you as as L so you are limited in uh what can happen to attacks on typically Chu was they basically of packages does get hacked the neural realtor to that user don't have signing and and if you get up because most of us realize his have guessed that you we have these issues but it did have does get hacked then as a lot of issues I think so that's 1 of these that work in ignoring for the moment but you're absolutely right that packages is kind of I like to a single point of failure from a security perspective and we do 1 include signing at some point and there is this makes things very difficult for us because the ups and current have packages is that we can directly let people download stuff from github and they offer for example the use of archives for all the tags which unsigned even if you time assigned the git commit that you tagged and that then gets built into a package so for us to be able to offer signing of packages we actually have to build all packages for all these open source projects on packages to actually were might have them uploaded and I we haven't quite figured out how to do that in a somewhat the same and just as easy to use weighted and in this the 2nd part is actually somewhat related to this is that composer handles dependencies per application and that is the very purpose of composers we don't want to do system dependencies that that's the the purpose of composers to build a applications like the resulting of product is something that I would install through a distributions the package manager but this is purely for developers and aid is not designed to install the just 1 instance of a particular piece of code the the very idea of course of composers to manage dependencies of 1 projects within the directory have self-contained and so yes I understand this is not what you're trying to do but that is a very intentional decision to do that that this way the very I think there is 1 more question in here all the so that and so the question is which can which some others suffer inspired is most wobbling composer and the cat and this is actually a number is in 1 particular 1 but it all started with me is starting to work and the dependencies so itself uh which is based on the SAT solver in lips zipper which gets used to install rpm some open says and so that's how we resolve all these worrying constrains of a figure which was a with dependencies to install and then a lot of the and configuration files like the composer Jason and all this looks is inspired by and PM's configuration files from the node as well as the lot thousand I'll give you have fallen by the in the real world the mother is a tool on top of Ruby gems of which makes which trends gems which is another 1 of these tools where you you install a package free of like processes to make changes into 1 of these really describe state with remember you stupid described the statement as data and gem is being used to inspect tially make those changes and so I think maybe those 3 where this deftly inference from others as well the thing I think we're done with if you have some more questions come see me here the poorly thank thank you
Offene Menge
Bit
Punkt
Prozess <Physik>
Freeware
Dokumentenserver
Formale Sprache
Versionsverwaltung
Kartesische Koordinaten
Benutzeroberfläche
Extrempunkt
Freeware
Client
Wechselsprung
Umweltinformatik
Datenmanagement
Puls <Technik>
Einheit <Mathematik>
Addition
Kraftfahrzeugmechatroniker
Lineares Funktional
Dokumentenserver
Übersetzungsspeicher
Applet
Partielle Differentiation
p-Block
Quellcode
Frequenz
Rechenschieber
Projektive Ebene
Information
Datenfluss
Programmierumgebung
Standardabweichung
Schnittstelle
Proxy Server
Subtraktion
Zahlenbereich
Zellularer Automat
Informationsmanagement
Informationsmodellierung
Software
Proxy Server
Programmbibliothek
Vererbungshierarchie
Skript <Programm>
Installation <Informatik>
Zusammenhängender Graph
Softwareentwickler
Konfigurationsraum
Bildgebendes Verfahren
Einfach zusammenhängender Raum
Benutzeroberfläche
Open Source
Mailing-Liste
Plug in
Physikalisches System
Elektronische Publikation
Modul
Mapping <Computergraphik>
Modallogik
Offene Menge
Mereologie
Wort <Informatik>
Partikelsystem
Resultante
Punkt
Prozess <Physik>
Versionsverwaltung
Gruppenkeim
Kartesische Koordinaten
Homepage
Gradient
Trigonometrische Funktion
Fahne <Mathematik>
Skript <Programm>
Wurzel <Mathematik>
Figurierte Zahl
Softwaretest
Namensraum
Dokumentenserver
Physikalischer Effekt
Datenlogger
Konfiguration <Informatik>
Entscheidungstheorie
Dienst <Informatik>
Menge
Server
Garbentheorie
Projektive Ebene
Information
Ordnung <Mathematik>
Versionsverwaltung
Schlüsselverwaltung
Verzeichnisdienst
Message-Passing
Fehlermeldung
Maschinenschreiben
Nebenbedingung
Server
Subtraktion
Rahmenproblem
Klasse <Mathematik>
Mathematisierung
Zahlenbereich
Schriftzeichenerkennung
Maßerweiterung
Informationsmanagement
Code
Spannweite <Stochastik>
Reelle Zahl
Determiniertheit <Informatik>
Programmbibliothek
Inverser Limes
Zusammenhängender Graph
Installation <Informatik>
Inhalt <Mathematik>
Datenstruktur
Konfigurationsraum
Videospiel
Elektronische Publikation
Namensraum
Reibungskraft
Kontinuierliche Integration
Peer-to-Peer-Netz
Elektronische Publikation
Integral
Programmfehler
Mapping <Computergraphik>
Dreiecksfreier Graph
Mereologie
Wort <Informatik>
Parabel <Mathematik>
Partikelsystem
Verkehrsinformation
Nebenbedingung
Bit
Stabilitätstheorie <Logik>
Punkt
Freeware
Wasserdampftafel
Klasse <Mathematik>
Mathematisierung
Nebenbedingung
Versionsverwaltung
Zahlenbereich
Kartesische Koordinaten
Patch <Software>
Nichtlinearer Operator
Informationsmanagement
Eins
Spannweite <Stochastik>
Knotenmenge
Programmbibliothek
Kontrollstruktur
Installation <Informatik>
Softwareentwickler
Streuungsdiagramm
Autorisierung
Nichtlinearer Operator
Befehl <Informatik>
Sichtenkonzept
Matching <Graphentheorie>
Gebäude <Mathematik>
Ausnahmebehandlung
Mailing-Liste
Paarvergleich
Physikalisches System
Elektronische Publikation
Fokalpunkt
Quick-Sort
Endogene Variable
Konfiguration <Informatik>
Spannweite <Stochastik>
Mapping <Computergraphik>
Patch <Software>
Beweistheorie
Digitalisierer
Mereologie
Projektive Ebene
Wort <Informatik>
Ordnung <Mathematik>
Versionsverwaltung
Verzeichnisdienst
Nebenbedingung
Stabilitätstheorie <Logik>
Web Site
Punkt
Extrempunkt
Hochdruck
Familie <Mathematik>
Versionsverwaltung
Zahlenbereich
Kartesische Koordinaten
Benutzeroberfläche
Informationsmanagement
Systemplattform
Virtuelle Maschine
Datensatz
Programmbibliothek
Jensen-Maß
Softwareentwickler
Maßerweiterung
Default
Softwaretest
ATM
Dokumentenserver
Matching <Graphentheorie>
Stochastische Abhängigkeit
Verzweigendes Programm
Ruhmasse
Mailing-Liste
Quellcode
Biprodukt
Elektronische Publikation
Konfiguration <Informatik>
Mapping <Computergraphik>
Dienst <Informatik>
Betafunktion
Mereologie
Projektive Ebene
Wort <Informatik>
Information
Partikelsystem
Verzeichnisdienst
Programmierumgebung
Aggregatzustand
Bit
Web Site
Dokumentenserver
Formale Sprache
Versionsverwaltung
Gebäude <Mathematik>
Element <Mathematik>
Informationsmanagement
Homepage
Metadaten
Benutzerbeteiligung
Binärdaten
Äußere Algebra eines Moduls
Skript <Programm>
Softwareentwickler
Konfigurationsraum
Default
Dokumentenserver
Konfigurationsraum
Verzweigendes Programm
Systemaufruf
Mailing-Liste
Physikalisches System
Elektronische Publikation
Packprogramm
Konfiguration <Informatik>
Datenfeld
Menge
Mereologie
Projektive Ebene
URL
Verzeichnisdienst
Statistik
Punkt
Prozess <Physik>
Graph
Gruppenoperation
Zahlenbereich
Physikalisches System
Elektronische Publikation
Informationsmanagement
Physikalisches System
Konfigurationsverwaltung
Datenmanagement
Mereologie
Hypermedia
Server
Wort <Informatik>
Installation <Informatik>
Projektive Ebene
Versionsverwaltung
Verzeichnisdienst
Schlüsselverwaltung
Phasenumwandlung
Aggregatzustand
Resultante
Distributionstheorie
Stereometrie
Prozess <Physik>
Punkt
Freeware
Inferenz <Künstliche Intelligenz>
Datensichtgerät
Formale Sprache
Versionsverwaltung
Gruppenkeim
Kartesische Koordinaten
Drehung
Benutzeroberfläche
Homepage
Deskriptive Statistik
Datenmanagement
Prozess <Informatik>
Vorzeichen <Mathematik>
Code
Default
Figurierte Zahl
Erfüllbarkeitsproblem
Befehl <Informatik>
Computersicherheit
Reihe
Quellcode
Biprodukt
Ereignishorizont
Teilbarkeit
Entscheidungstheorie
Softwarewartung
Twitter <Softwareplattform>
Projektive Ebene
Information
Computerunterstützte Übersetzung
Verzeichnisdienst
Programmierumgebung
Lipschitz-Bedingung
Instantiierung
Aggregatzustand
Rahmenproblem
Selbst organisierendes System
Mathematisierung
Schaltnetz
Ablöseblase
Zahlenbereich
Informationsmanagement
Framework <Informatik>
Code
Methodenbank
Benutzerbeteiligung
Knotenmenge
Perspektive
Datentyp
Programmbibliothek
COM
Zusammenhängender Graph
Softwareentwickler
Optimierung
Ereignishorizont
Konfigurationsraum
Hilfesystem
Leistung <Physik>
Schreib-Lese-Kopf
Quarkmodell
Soundverarbeitung
Trennungsaxiom
Graph
Open Source
Einfache Genauigkeit
Mailing-Liste
Physikalisches System
Elektronische Publikation
Packprogramm
Office-Paket
Dreiecksfreier Graph
Mereologie
Injektivität
Informationsmanagement

Metadaten

Formale Metadaten

Titel Dependency Management with Composer: PHP Reinvented
Alternativer Titel Php And Friends - Dependency management with composer: php reinvented
Serientitel FOSDEM 2015
Autor Adermann, Nils
Lizenz CC-Namensnennung 2.0 Belgien:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
DOI 10.5446/34469
Herausgeber FOSDEM VZW
Erscheinungsjahr 2016
Sprache Englisch
Produktionsjahr 2015

Inhaltliche Metadaten

Fachgebiet Informatik

Ähnliche Filme

Loading...
Feedback