Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Phiter Fernandes
    @phiter
    is there a way to make it not pass the argument to @unlock?
    Phiter Fernandes
    @phiter
    Ok I found a way to ignore it
    "create" : [
                "@phinx create --template=MigrationTemplate.php.dist",
                "@unlock"
            ],
            "unlock" : "chmod -R 777 db/migrations && :",
    I put && colon after the chmod so anything after it is ignored
    Ben Johnson
    @cbj4074
    @phiterf That's a creative solution. Thanks for sharing. :) That behavior seems odd in the first place.
    ashashingadia2996
    @ashashingadia2996
    I want to install my local package using composer, I have tried solutions found from the web and didn't get desired results. Can anyone please suggest me steps for that. Any help would be appreciated :)
    Ben Johnson
    @cbj4074
    @ashashingadia2996 What, exactly, have you tried so far? It would be helpful to know what you tried so we know why it didn't work.
    megri
    @megri
    I am using a lib jms/serializer that uses annotations from doctrine. For the annotations to be workable it seems I am required to add Doctrine\Common\Annotations\AnnotationRegistry::registerLoader('class_exists'); at the start of my project. I'm thinking it'd be nice if I could somehow incorporate this into the generated autoload.php-file, so that it's always called exactly once without me having to spell it out all over the place. Is this somehow possible?
    Pierre-Emmanuel Lallemant
    @pelallemant
    Hi. I'm using curl -s https://getcomposer.org/installer | php to install composer, and I now have tons of warnings about deprecation of package names which doesn't match a certain pattern. My question is: when the 2.0 will be available, will it be installed by my last command ? And is there any information about the 2.0 release, will it make the 1.X composer down, or will packagist still be working with older versions of composer ? It would be nice that there would be an installer for the 1.X and another installer for the 2.X . By doing this, projects deployed in CI/CD using this installer would not fetch by error the 2.X (which could crash if package names aren't valid)
    Ben Johnson
    @cbj4074
    @megri Didn't see your question from so long ago, but if I understand it correctly, you can simply do as I describe here: https://stackoverflow.com/a/55339202/1772379
    Doqnach
    @Doqnach
    any idea when composer:1.8.5 will be on docker-hub? since 1.8.4 gives CVE warnings because of the git version (alpine 3.8 based)
    Ricardo Murillo
    @ricardowall13_twitter
    I think if you can blindly trust other parties to have your infrastructure and centralize it for the whole network, then a blockchain is not what you need.
    See this thinking here
    https://medium.com/worldsibu/forma-they-way-youve-wished-enterprise-blockchain-infrastructure-was-61f470fcbc78
    Doqnach
    @Doqnach
    hey all, anyone any idea how to get event data in a composer script if it's a bash script?
    @everyone
    UniFreak
    @UniFreak
    Hi, I’m trying to install a private hosted package, by running the command composer require mycompany/qlog
    but the result keeps error out due to unmet dependencies of elastiquent/elasticquent
    here is the composer.json of the project: https://kopy.io/M38ee
    and the run result: https://kopy.io/eF1Uo
    I have some confusion: why a unrelated package will affect elasticquent package? how can I make what’s there still untouched and only make the new one installed?
    Ben Johnson
    @cbj4074
    @UniFreak Laravel 5.1, eh? :D I've never found Composer's messages particularly intuitive, but if I'm reading that correctly, you simply need to add "minimum-stability": "dev" to your composer.json.
    I'm pretty sure that Composer needs to re-evaluate all of your dependencies when you require a new package, so even though they are "unrelated packages", something may have changed since the composer.lock was saved that is now problematic with regard to adding or updating your dependencies.
    Ben Johnson
    @cbj4074
    Or, maybe mycompany/qlog requires a newer version of Laravel? What's the output of composer why-not mycompany/qlog?
    Vadim Mazur
    @mazurva

    Hello! Can anyone tell how to replace a fork of the original packege, if the standard methods don't work. Do fork dmstr/yii2-adminlte-asset to prepare Pull Request
    When I do composer update I see such picture

    Updating dmstr/yii2-adminlte-asset dev-master (572c699 => ddaa6ac):  Checking out ddaa6acdee

    where 572c699 - my fork, ddaa6ac - last original commit

    My version composer.json:
        "minimum-stability": "dev",
        "repositories": [
            {
                "type": "git",
                "url": "https://github.com/mazurva/yii2-adminlte-asset.git"
            }
        ],
        "require": {
            "yiisoft/yii2": "2.0.*",
            "dmstr/yii2-adminlte-asset": "dev-master"
        }
    Ben Johnson
    @cbj4074
    @mazurva Have you tried removing and then re-adding the dependency?
    I know you have to do that when changing the version constraint, so it's possible the same is true when you change the effective repository.
    Vadim Mazur
    @mazurva
    @cbj4074 Nothing has changed.
    Vadim Mazur
    @mazurva
    Thanks, anyway.
    Doqnach
    @Doqnach
      Repository "0" ({"packagist":false}) must have a type defined
    How can you supply packagist=false on composer init? I am using:
    composer init --repository="{\"packagist\":false}" but this obviously isn't working...
    Doqnach
    @Doqnach
    discussion going in composer/composer#8210
    Michael Skenderian
    @mskenderian_twitter
    i have a private repo "repositories": { "wpsa/options": { "type": "vcs", "url": "https://my.domain.com/wpsa/options.git" }
    when composer installs it, it asked for username and password, which is what i expect. but then i get the message A token will be created and stored in "/home/vagrant/.composer/auth.json", your password will never be stored
    checking that file, it has stored my username and password.
    JonasWijne
    @JonasWijne
    hi, would it be possible to have the same repo multiple times in composer.json but with diffrent login credentials?
    Doqnach
    @Doqnach
    exactly the same? (host + path)
    JonasWijne
    @JonasWijne
    yes
    Doqnach
    @Doqnach
    because then I don't think so, unless you do it via http(s) and basic auth plain text in composer.json
    and even then, it will lookup the package in each and every repo you mention, so if it exists in both/all it will pick I think the first one it finds?
    but I might be wrong here
    JonasWijne
    @JonasWijne
    Reason is that, the packages in the repo are based on the login credentials given (kinda weird but hey )
    Doqnach
    @Doqnach
    that does sound weird to me yeah :-P
    well, the only way I know how to do it is the above
    which I feel is terrible
    JonasWijne
    @JonasWijne
    @Doqnach, i tried with the basic auth in plaintext, and it worked
    Doqnach
    @Doqnach
    Have fun with credentials plain text in VCS :-P
    JonasWijne
    @JonasWijne
    yeah, my toughts exacly
    gonne make a script which will replace the username and password based on some env variables
    thx for the idea / help
    Kristiyan Katsarov
    @katsar0v
    Hello guys! I just joined the composer - Community in Gitter :)
    Kristiyan Katsarov
    @katsar0v
    I wanted to ask: does composer make sum check of required dependencies? When defining custom packages, then a hashsum may be defined, but what about dependencies from packagist or wpackagist? Would love to hear from anyone! Thanks in advance!
    Rob
    @alcohol
    yes
    packagist adds a checksum