Also, while the guide was written for CodeIgniter 4.0.4, that was simply the latest version at the time. We do not recommend running that specific version, the instructions probably work for all CodeIgniter 4 versions.
If, indeed, you apply them correctly.
Also, please consider that the appstarter template you’re using is not just plain CodeIgniter, it needs a Composer install step to work. And seeing how the vendor directory is absent, I’m guessing that you didn’t do that.
What you do appear to have done is move files into different locations, notably the files from the public directory. While that can be done as an alternative to the .htaccess route that the community guide proposes, it does mean that you’re tinkering with the structure of the framework, which means you need to know what you’re doing.
All in all, please understand that CodeIgniter is a framework, not a CMS. It’s a component you use to build your own application, and its target audience is developers. It’s not like WordPress where you can just drop a zip file on the server, login to a web interface, and click everything together.
My recommendation to move forward is as follows:
- Setup a local development environment, like XAMPP.
- Install CodeIgniter on your own computer, make sure everything is installed (including the Composer dependencies), following the instructions from CodeIgniter.
- Apply the necessary configuration from the community guide.
- When you have CodeIgniter installation that works, you can upload it to your account here over FTP.
Then, when you actually start building your application, you can develop and test it locally on your own computer first, and only upload your changes when you have something that works and you’re confident to deploy.
If you just upload CodeIgniter directly to our servers, how are you going to build your application then? Using the text editor from the file manager?