Best way to create archived/historic app versions |
[eluser]yatil[/eluser]
Hi folks. I programmed a website for a small conference last year, containing programme, podcasts and informations. The same event will happen again this year, so we need a new version of the website. I’d really just like to duplicate the app to use the old logic to register. Is there any possibility to use subfolders in a meaningful manner? (The website is already on a subdomain.) The current website is located at http://atag.accessible-media.at/ and I'd like to move the site to http://atag.accessible-media.at/2008/ and do a new version at http://atag.accessible-media.at/2009/ — The root would just redirect to the 2009 subfolder. Are there any tutorials or a quick step by step introduction what I have to do to make a seamless transition? Or is there a way to use the same logic for both instances and having just different database tables+templates? I am really looking forward to your suggestions as I’ve been unsuccessful until now. If you need any more informations, I’m happy to provide them. Regards, Eric
[eluser]tomcode[/eluser]
CI is pretty flexible and allows personalised system and application paths. Additionally I got used to implement an asset path and a view path variable. Sometimes I rename the application folder to the release name and number : domaine_XXX, sharing one common assets folder. Sometimes I separate versions into different system folders. The asset path and view path variables allow me further fine tuning for layout changes.
[eluser]stefanhapper[/eluser]
Yatil, yes this should be possible. The easiest way (while not sure if the most elegant one) will be to create a new index.php file under a new subfolder (or subdomain) and set the path to a copy of the system folder (which can basically sit whereever you like). Hope this helps.
[eluser]yatil[/eluser]
Hi! Thanks for your tips, will look into them as soon as possible! |
Welcome Guest, Not a member yet? Register Sign In |