symfony flex with private recipes - composer-php

What's the proper way to setup a flex recipe (private or public repository) for a package (private repository)?
What I tried so far
Got a private repository on bitbucket with a package.
Got a private repository on github with recipes.
Configured symfony flex server on github repository.
Added projects ids in config.json (recipes repository)
Yet, I can't understand how a recipe gets called during composer update..

Related

Unable to use JFrog Artifactory to proxy GitHub private repositories as Go Registry

I want to use Go Remote repository proxying Github. I have created Go remote repo github proxying https://github.com/ and I have created a Go virtual repository as well. Credentials added as mentioned in https://www.jfrog.com/confluence/display/RTF/Go+Registry#GoRegistry-RemoteRepositories.
I did everything explained on the link above but when I tried to get the modules I get that:
go env -w GONOSUMDB="*github.com/xxx/*"
export GOPROXY="https://test:%5Bredacted%5D#xxx.jfrog.io/artifactory/api/go/go"
go mod download -x
get https://test:%5Bredacted%5D#xxx.jfrog.io/artifactory/api/go/go/github.com/xxx/platform/#v/v0.21.0.mod
get https://test:%5Bredacted%5D#xxx.jfrog.io/artifactory/api/go/go/github.com/xxx/platform/#v/v0.21.0.mod: 404 Not Found (0.894s)
go: github.com/xxx/platform#v0.21.0: reading https://test:%5Bredacted%5D#xxx.jfrog.io/artifactory/api/go/go/github.com/xxx/platform/#v/v0.21.0.mod: 404 Not Found
Besides that, I can get public modules from github. Auth seems not working.
You should upgrade to JFrog Artifactory 6.19+ or 7.4.0+ as this was a missing feature until then (https://www.jfrog.com/jira/browse/RTFACT-19395).

Travis CI not recognizing renamed repository

So I originally named my github repo my_repo, but then renamed it my-repo shortly after creation, like within the first day. This was roughly a year ago.
Ever since, I've been building the project with Travis CI, using the free .org version. Now after making all my repos private and upgrading to the pro version with travis-ci.com, I've had to provide new API credentials in my .travis.yml. So I have to do so with
travis encrypt $(heroku auth:token) --add deploy.api_key --pro
This has worked with other repositories, but not this particular one. Instead, I get
repository not known to https://api.travis-ci.com/: dben89x/my_repo
However, on my Travis CI dashboard, it's trying to build it as dben89x/my-repo. I'm not sure how to tell travis to build it as dben89x/my-repo.
All my git remotes are set up as my-repo. I've tried logging out in the CLI and logging back in.
I found the answer here: https://github.com/travis-ci/travis-ci/issues/3264#issuecomment-180246348
Went into .git/config and changed
[travis]
slug = dben89x/my_repo
to
[travis]
slug = dben89x/my-repo

AWS Codebuild Golang Lambda using Serverless Framework

I'm building golang lambda functions using the serverless framework in AWS CodeBuild. This project is in a private bitbucket repository. And the CodeBuild source is the bitbucket repo
I'm having some problems of using local packages in the code.
I have this project structure
hello
test
test.go
main.go
serverless.yml
...other files
what I'm trying to do is to use package test in hello/test/test.go in the hello/main.go.
And I've tried 2 options.
Import the package using "myproject/hello/test"
Using bitbucket url and dep ensure. Moving test to another project.
the problems:
in AWS CodeBuild, the package cannot be found as the real package directory is /....aws path/bitbucket.org/<username>/<repo>/ and the $GOPATH is /...aws path/.
dep ensure freezes when writing the private bitbucket repo. I'm assuming that it's because authentication issues?
So, what can I do to use my golang packages in AWS CodeBuild? And it's a private repo not a public one.
Based on Peter's comments, I resolved the issue by using the full path of my bitbucket repo in my $GOPATH/src.
so the path should be bitbucket.org/<username>/<repo>

Host private PHP packages on packagist with gitlab

I have a gitlab installation for my organization. To standardize, the frameworks and development process we'd like to make the use of our own packagist installation on our server.
The thing that is confusing me, is when I have to submit a package which is on a repo of gitlab, it requires authentication. I know while including a package in composer.json I can put repo, username and password so that it can read package from there. or while I am creating a project:
composer create-project vendor/name path --repository-url=http://user:password#my.gitlab.com/myrepo/package.git
If that is true, do we really need packagist? if yes then what would be the best way to setup this.
I'd appreciate if you guys also tell me how the package submission on packagist(our own hosted) will work.

Can not sync private project to Travis CI from Github

I am using Travis CI to run script of repository github, but i can not see my private project to sync
Anything i can make to do it ?
https://gyazo.com/1086bc83f8b91ce38c74618c38df7705
In Travis CI, private and public repos are separately managed. Public repositories appear in https://travis-ci.org/profile and private ones in https://magnum.travis-ci.com/profile.
For more details you can refer to https://github.com/travis-ci/travis-ci/issues/2519

Resources