Forking Laravel Repo











up vote
-2
down vote

favorite












I am attempting to fork the laravel repo as I need to make a change in RegistersUsers.php. I have never forked before, but it seemed straightforward enough. I have forked the repo to my github and updated my composer.json files as follows. However I am getting an error when I update composer



Problem 1
- The requested package puggers/laravel could not be found in any version, there may be a typo in the package name.



Any help would be greatly appreciated.



{

"repositories": [

{

"type": "vcs",
"url": "https://github.com/puggers/laravel"

}

],

"name": "laravel/laravel",
"description": "The Laravel Framework.",
"keywords": ["framework", "laravel"],
"license": "MIT",
"type": "project",
"require": {
"puggers/laravel": "dev-master",
"php": "^7.1.3",
"barryvdh/laravel-ide-helper": "^2.5",
"fideloper/proxy": "^4.0",
"laravel/framework": "5.7.*",
"laravel/tinker": "^1.0",
"willvincent/feeds": "dev-master",
"ext-simplexml": "*",
"ext-json": "*",
"ext-curl": "*"

},
"require-dev": {
"beyondcode/laravel-dump-server": "^1.0",
"filp/whoops": "^2.0",
"fzaninotto/faker": "^1.4",
"mockery/mockery": "^1.0",
"nunomaduro/collision": "^2.0",
"phpunit/phpunit": "^7.0"
},
"autoload": {
"classmap": [
"database/seeds",
"database/factories"
],
"psr-4": {
"App\": "app/"
}
},
"autoload-dev": {
"psr-4": {
"Tests\": "tests/"
}
},
"extra": {
"laravel": {
"dont-discover": [
]
}
},
"scripts": {
"post-root-package-install": [
"@php -r "file_exists('.env') || copy('.env.example', '.env');""
],
"post-create-project-cmd": [
"@php artisan key:generate"
],
"post-autoload-dump": [
"Illuminate\Foundation\ComposerScripts::postAutoloadDump",
"@php artisan package:discover"
]
},
"config": {
"preferred-install": "dist",
"sort-packages": true,
"optimize-autoloader": true
},
"minimum-stability": "dev",
"prefer-stable": true
}









share|improve this question


















  • 3




    Do you mean the RegistersUsers.php trait? You could just overwrite the methods where you use the trait, or create your own trait instead, seems overkill to fork the framework for a simple trait.
    – Remul
    Nov 21 at 16:59








  • 3




    You shouldn't need to fork the laravel/laravel repo at all. That's just boilerplate to get you started on your own project, unless of course you found a bug in the boilerplate and want to make a pull request.
    – apokryfos
    Nov 21 at 17:00










  • Yeah that was about 50 million times easier. Don't know why my brain didn't go there in the first place. Thanks for the nudge in the right direction.
    – Justin
    Nov 21 at 17:07















up vote
-2
down vote

favorite












I am attempting to fork the laravel repo as I need to make a change in RegistersUsers.php. I have never forked before, but it seemed straightforward enough. I have forked the repo to my github and updated my composer.json files as follows. However I am getting an error when I update composer



Problem 1
- The requested package puggers/laravel could not be found in any version, there may be a typo in the package name.



Any help would be greatly appreciated.



{

"repositories": [

{

"type": "vcs",
"url": "https://github.com/puggers/laravel"

}

],

"name": "laravel/laravel",
"description": "The Laravel Framework.",
"keywords": ["framework", "laravel"],
"license": "MIT",
"type": "project",
"require": {
"puggers/laravel": "dev-master",
"php": "^7.1.3",
"barryvdh/laravel-ide-helper": "^2.5",
"fideloper/proxy": "^4.0",
"laravel/framework": "5.7.*",
"laravel/tinker": "^1.0",
"willvincent/feeds": "dev-master",
"ext-simplexml": "*",
"ext-json": "*",
"ext-curl": "*"

},
"require-dev": {
"beyondcode/laravel-dump-server": "^1.0",
"filp/whoops": "^2.0",
"fzaninotto/faker": "^1.4",
"mockery/mockery": "^1.0",
"nunomaduro/collision": "^2.0",
"phpunit/phpunit": "^7.0"
},
"autoload": {
"classmap": [
"database/seeds",
"database/factories"
],
"psr-4": {
"App\": "app/"
}
},
"autoload-dev": {
"psr-4": {
"Tests\": "tests/"
}
},
"extra": {
"laravel": {
"dont-discover": [
]
}
},
"scripts": {
"post-root-package-install": [
"@php -r "file_exists('.env') || copy('.env.example', '.env');""
],
"post-create-project-cmd": [
"@php artisan key:generate"
],
"post-autoload-dump": [
"Illuminate\Foundation\ComposerScripts::postAutoloadDump",
"@php artisan package:discover"
]
},
"config": {
"preferred-install": "dist",
"sort-packages": true,
"optimize-autoloader": true
},
"minimum-stability": "dev",
"prefer-stable": true
}









share|improve this question


















  • 3




    Do you mean the RegistersUsers.php trait? You could just overwrite the methods where you use the trait, or create your own trait instead, seems overkill to fork the framework for a simple trait.
    – Remul
    Nov 21 at 16:59








  • 3




    You shouldn't need to fork the laravel/laravel repo at all. That's just boilerplate to get you started on your own project, unless of course you found a bug in the boilerplate and want to make a pull request.
    – apokryfos
    Nov 21 at 17:00










  • Yeah that was about 50 million times easier. Don't know why my brain didn't go there in the first place. Thanks for the nudge in the right direction.
    – Justin
    Nov 21 at 17:07













up vote
-2
down vote

favorite









up vote
-2
down vote

favorite











I am attempting to fork the laravel repo as I need to make a change in RegistersUsers.php. I have never forked before, but it seemed straightforward enough. I have forked the repo to my github and updated my composer.json files as follows. However I am getting an error when I update composer



Problem 1
- The requested package puggers/laravel could not be found in any version, there may be a typo in the package name.



Any help would be greatly appreciated.



{

"repositories": [

{

"type": "vcs",
"url": "https://github.com/puggers/laravel"

}

],

"name": "laravel/laravel",
"description": "The Laravel Framework.",
"keywords": ["framework", "laravel"],
"license": "MIT",
"type": "project",
"require": {
"puggers/laravel": "dev-master",
"php": "^7.1.3",
"barryvdh/laravel-ide-helper": "^2.5",
"fideloper/proxy": "^4.0",
"laravel/framework": "5.7.*",
"laravel/tinker": "^1.0",
"willvincent/feeds": "dev-master",
"ext-simplexml": "*",
"ext-json": "*",
"ext-curl": "*"

},
"require-dev": {
"beyondcode/laravel-dump-server": "^1.0",
"filp/whoops": "^2.0",
"fzaninotto/faker": "^1.4",
"mockery/mockery": "^1.0",
"nunomaduro/collision": "^2.0",
"phpunit/phpunit": "^7.0"
},
"autoload": {
"classmap": [
"database/seeds",
"database/factories"
],
"psr-4": {
"App\": "app/"
}
},
"autoload-dev": {
"psr-4": {
"Tests\": "tests/"
}
},
"extra": {
"laravel": {
"dont-discover": [
]
}
},
"scripts": {
"post-root-package-install": [
"@php -r "file_exists('.env') || copy('.env.example', '.env');""
],
"post-create-project-cmd": [
"@php artisan key:generate"
],
"post-autoload-dump": [
"Illuminate\Foundation\ComposerScripts::postAutoloadDump",
"@php artisan package:discover"
]
},
"config": {
"preferred-install": "dist",
"sort-packages": true,
"optimize-autoloader": true
},
"minimum-stability": "dev",
"prefer-stable": true
}









share|improve this question













I am attempting to fork the laravel repo as I need to make a change in RegistersUsers.php. I have never forked before, but it seemed straightforward enough. I have forked the repo to my github and updated my composer.json files as follows. However I am getting an error when I update composer



Problem 1
- The requested package puggers/laravel could not be found in any version, there may be a typo in the package name.



Any help would be greatly appreciated.



{

"repositories": [

{

"type": "vcs",
"url": "https://github.com/puggers/laravel"

}

],

"name": "laravel/laravel",
"description": "The Laravel Framework.",
"keywords": ["framework", "laravel"],
"license": "MIT",
"type": "project",
"require": {
"puggers/laravel": "dev-master",
"php": "^7.1.3",
"barryvdh/laravel-ide-helper": "^2.5",
"fideloper/proxy": "^4.0",
"laravel/framework": "5.7.*",
"laravel/tinker": "^1.0",
"willvincent/feeds": "dev-master",
"ext-simplexml": "*",
"ext-json": "*",
"ext-curl": "*"

},
"require-dev": {
"beyondcode/laravel-dump-server": "^1.0",
"filp/whoops": "^2.0",
"fzaninotto/faker": "^1.4",
"mockery/mockery": "^1.0",
"nunomaduro/collision": "^2.0",
"phpunit/phpunit": "^7.0"
},
"autoload": {
"classmap": [
"database/seeds",
"database/factories"
],
"psr-4": {
"App\": "app/"
}
},
"autoload-dev": {
"psr-4": {
"Tests\": "tests/"
}
},
"extra": {
"laravel": {
"dont-discover": [
]
}
},
"scripts": {
"post-root-package-install": [
"@php -r "file_exists('.env') || copy('.env.example', '.env');""
],
"post-create-project-cmd": [
"@php artisan key:generate"
],
"post-autoload-dump": [
"Illuminate\Foundation\ComposerScripts::postAutoloadDump",
"@php artisan package:discover"
]
},
"config": {
"preferred-install": "dist",
"sort-packages": true,
"optimize-autoloader": true
},
"minimum-stability": "dev",
"prefer-stable": true
}






laravel github composer-php






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 21 at 16:37









Justin

395




395








  • 3




    Do you mean the RegistersUsers.php trait? You could just overwrite the methods where you use the trait, or create your own trait instead, seems overkill to fork the framework for a simple trait.
    – Remul
    Nov 21 at 16:59








  • 3




    You shouldn't need to fork the laravel/laravel repo at all. That's just boilerplate to get you started on your own project, unless of course you found a bug in the boilerplate and want to make a pull request.
    – apokryfos
    Nov 21 at 17:00










  • Yeah that was about 50 million times easier. Don't know why my brain didn't go there in the first place. Thanks for the nudge in the right direction.
    – Justin
    Nov 21 at 17:07














  • 3




    Do you mean the RegistersUsers.php trait? You could just overwrite the methods where you use the trait, or create your own trait instead, seems overkill to fork the framework for a simple trait.
    – Remul
    Nov 21 at 16:59








  • 3




    You shouldn't need to fork the laravel/laravel repo at all. That's just boilerplate to get you started on your own project, unless of course you found a bug in the boilerplate and want to make a pull request.
    – apokryfos
    Nov 21 at 17:00










  • Yeah that was about 50 million times easier. Don't know why my brain didn't go there in the first place. Thanks for the nudge in the right direction.
    – Justin
    Nov 21 at 17:07








3




3




Do you mean the RegistersUsers.php trait? You could just overwrite the methods where you use the trait, or create your own trait instead, seems overkill to fork the framework for a simple trait.
– Remul
Nov 21 at 16:59






Do you mean the RegistersUsers.php trait? You could just overwrite the methods where you use the trait, or create your own trait instead, seems overkill to fork the framework for a simple trait.
– Remul
Nov 21 at 16:59






3




3




You shouldn't need to fork the laravel/laravel repo at all. That's just boilerplate to get you started on your own project, unless of course you found a bug in the boilerplate and want to make a pull request.
– apokryfos
Nov 21 at 17:00




You shouldn't need to fork the laravel/laravel repo at all. That's just boilerplate to get you started on your own project, unless of course you found a bug in the boilerplate and want to make a pull request.
– apokryfos
Nov 21 at 17:00












Yeah that was about 50 million times easier. Don't know why my brain didn't go there in the first place. Thanks for the nudge in the right direction.
– Justin
Nov 21 at 17:07




Yeah that was about 50 million times easier. Don't know why my brain didn't go there in the first place. Thanks for the nudge in the right direction.
– Justin
Nov 21 at 17:07

















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53416709%2fforking-laravel-repo%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53416709%2fforking-laravel-repo%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Berounka

Fiat S.p.A.

Type 'String' is not a subtype of type 'int' of 'index'