So even though the application was built with CodeIgniter, the framework isn’t built into it & still needs to be installed?
- If it's done "correctly" you normally don't bundle Composer packages. You put a composer.json file in your Github project. To let Composer know what files it need to download for the application to work. That's how our "Appstarter" package work in the userguide as well. After you have made your application and publish it. People need to download CodeIgniter themself.
OK, so the framework is considered to be a dependency and no dependencies will be included in the GitHub code. I think it says on the Composer Installation page that the vendor folder is usually gitignored so that ties in. I'm new to frameworks & dependency managers so trying understand how it all works...
- That's correct, in the Appstarter application we have ignored the vendor folder. That's normal practice. Not everyone describe that you need to run
composer install in their readme file to get the application working. The reason for it are that it will download the latest version, containing bug and security fixes. So that the owner of the project don't need to update it all the time themself.
I see, so the section Adding CodeIgniter4 to an Existing Project is for projects not built with CodeIgniter (please correct if not true).
- That's correct. You started making your application without the intent to use CodeIgniter and later chose to add it. So you need to manually do all the things Appstarter does for you.
I do want to extend the project and have completed the CodeIgniter first app tutorial. So that should help.
- Great, good luck on the development!
