Welcome Guest, Not a member yet? Register   Sign In
install on server
#1

[eluser]CI2RULZ[/eluser]
one of the beauties of CI is the ability to download and be ready to rock right from the jump. my question is, however, would it be beneficial to setup CI on the server, add to the ini include path, so all projects using CI can pull from one source? Anyone else do it this way, or does it cause unnecessary hassle when it comes to upgrades? For those that do this, how many files do you keep on the server... the library, or some of the core features as well? Just interested.
#2

[eluser]n0xie[/eluser]
[quote author="cmiwebstudio" date="1262794110"]one of the beauties of CI is the ability to download and be ready to rock right from the jump. my question is, however, would it be beneficial to setup CI on the server, add to the ini include path, so all projects using CI can pull from one source? Anyone else do it this way, or does it cause unnecessary hassle when it comes to upgrades? For those that do this, how many files do you keep on the server... the library, or some of the core features as well? Just interested.[/quote]
Yes, we do this.

We have 1 CodeIgniter 'system' folder like this:

/lib
/CodeIgniter
/1.6.2
/1.7.0
/1.7.1
/1.7.2
/current (symlink to the latest version, in this case 1.7.2)

And we just symlink everything to the 'current' folder. This way, whenever we do an upgrade and something breaks, you just turn the symlink to an older version and your sites are up and running again, while you figure out why the latest upgrade broke something.




Theme © iAndrew 2016 - Forum software by © MyBB