Deploy issue when app is not in the root git repository
sarbull opened this issue · comments
Deploy is not working when the app is not in the root git repository.
Right now i have my app in
git-repo/
git-repo/application
git-repo/application/app
git-repo/application/public
...
And when i run
php artisan deploy
'/git-repo/application' is not a Git repository.
I get this ^
Also i think laravel needs the vendor files in order to make the app work, so i think that this deploy system needs some sort of
return [
'ignored' => [],
'force' => [
'vendor' // in order to force deploy the ignored files from git.
]
];
Thanks!
Big 👍 for this ftp deploy system, specially on laravel apps with shared hosting!
Thanks for the kind words.
Maneuver reads the .git
directory to check if it's a git repo, so yes, it won't work outside of the root. It's supposed to work that way and I don't believe it's much of a problem.
As for the vendor
directory, I plan to add a force option and hopefully I can look into it asap. For now, your only option is to remove the vendor
from .gitignore
.
@fadion yes, but i have to create a new commit and then re add the folder into the gitignore file.. it's kinda weird.
I think that 'force' thing could solve everything.. If there is anything i can help you with this, i'd be glad.
The #13 Issue. Haha!
It's supposed to work that way and I don't believe it's much of a problem.
@fadion yes but, for example i like to keep in my git repo structured like this:
/application
/design
README.md
What could be the best solution for this?
/application
and /design
are the same repo and you want just the application/
folder pushed to the server?
@fadion yes
Git doesn't work that way. Maneuver just reads the diff and gets what files have changed for the whole git repo, not parts of it. You'll have to organize the application and design in different repos for Maneuver to work as you expect.
I see. Ok, looking forward on that force feature. Also check #14. Thanks!