All geek questions in one place

Cloning a CodeIgniter structure to create my site

Based on the background of SVN Git, it really takes some time to get used to. I really like it, but I'm still trying to figure out how to use it in different situations. So here is my question:

My PHP select structure is CodeIgniter. I plan to create my own website with CI, and I thought the best way to do this is to clone CI and build my site. I would do this because I really need a super easy way to update the CI structure. I'm just not sure if this is really the right way to use cloning or if there is another tactic that I should take. I was looking for submodules a bit, but this is not really the right way. Help?

+4
source share
2 answers

Sorry, I really did not understand Git / GitHub, this question was poorly asked on my part. I only considered removing it, but I think that my answer here can help other SVN developers who are starting to take risks on Git / GitHub.

Basically, I want to work with CodeIgniter and be able to retrieve updates from CI Master Branch. The workflow I need is very simple: Fork CI and Branch my fork to create my personal websites. By doing this, I can get updates from the upstream CI branch while maintaining the updated framework database.

In SVN, branching is so crappy that only the concept of branching with Git seemed crazy, now that I understand more about Git, I understand that branching is all I really need. Duh. Anyway, hope this helps anyone who comes from SVN. Branching is dead quick and easy in Git ... don't overdo it.

+1
source

Given that CodeIgniter has a GitHub repository , of course, you can clone it directly on your server, at the location specified in the Installation page .
Although for the pure purpose of deployment (i.e. for the code base, I will not make any updates and will not return to the remote repo, I prefer to download the archive from the provided archives on GitHub for each project ).

But this should be separate from your project (with your views, controllers, models, ... from your "application"), which should be in a separate bare repo on the same server and cloned locally on your workstation.
Then, the deployment method specified in Lars in the comment will take care of the rest.

+1
source

Source: https://habr.com/ru/post/1369305/

More articles:


All Articles