• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Different file structure when using composer?


I just noticed that the file structure of CI4 is different whether you install it using composer or do a 'manual' install ... what is the reasoning (if any reasoning at all) behind this? And should I worry about developing in either of these 'ways'? Yeah, I just see things potentially creeping up to bite me in the kneecaps …

I see no 'system' directory but a 'vendor' instead (containing the complete framework, including the 'system' folder) ...

well i'm old school using slackware linux to do things and i used to install manually.

I prefer https://packagist.org/packages/codeigniter4/appstarter; its a fairly minimalist directory structure.

Where composer comes into its own is when you start adding things such as https://packagist.org/packages/twbs/bootstrap for front end , and then maybe some add on that allows users to download a blog in the form of a pdf file.

Bootstrap and CI4 keep getting updated, to do it manually will soon become a pain. With composer its easily ; at your web dev root directory its just a case of using:

$ composer update --no-dev

//here the --no-dev flag is that i 'm not that interested in the extra stuff, what thus does is update all entries listed in composer.json and their deps

Have a look at :https://getcomposer.org/

To get an overview

oh yes your right there is no system but a "vendor" when you install extra software like twitter bootstrap it all goes into vendor. One other thing that composer does is that it gets everything load everything automatically.

if you ever need to refresh loading of whats in venor you can use:

$ composer dump

Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  

  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2021 MyBB Group.