We don't want to run composer update on our production server we would rather version control the vendor folder. We have shared files between our webapplications and we have a git repository called "shared" for this. What we do is currently uploading the files to the server cloning the shared repository into a shared sibling directory and use composer to load its content.
{
"repositories": [
{
"type": "path",
"url": "../shared"
}
],
"require": {
"my/shared": "*"
}
}
My current problem with this, that composer uses absolute path instead of relative path in its autoloader files when we use path type of repository. We could get rid of the composer repository and require the autoload file from the shared directory directly.
require_once __DIR__.'/../shared/vendor/autoload.php'
This would work, but it would break the code completion for VSCode.
I think you can see the problem. We need to:
Can this be solved somehow?
I added the shared directory to the intelephense.environment.includePaths , removed the repository from composer.json and required its autoload file directly. I moved these settings to a workspace file, I open that file with VSCode instead of the folder.
My files look like this:
app/application.code-workspace
{
"folders": [
{
"path": "."
}
],
"settings": {
"intelephense.environment.includePaths": [
"../shared"
]
}
}
app/composer.json
{
"name": "my/app",
"autoload": {
"psr-4": {
"Application\\": "Application"
}
}
}
app/index.php
<?php
require_once __DIR__.'/../shared/vendor/autoload.php';
require_once __DIR__.'/vendor/autoload.php';
use Application\Runner;
$runner = new Runner();
$runner->run();
app/Application/Runner.php
<?php
namespace Application;
use Shared\Test;
class Runner {
public function run(){
$test = new Test();
$test->run();
}
}
shared/composer.json
{
"name": "my/shared",
"autoload": {
"psr-4": {
"Shared\\": "Shared"
}
}
}
shared/Test.php
<?php
namespace Shared;
class Test {
public function run(){
echo 'Hello Shared!';
}
}