Re: [Tiki-devel] testing tiki version and virtualmin (switching)
Bsfez Tiki via TikiWiki-devel <[email protected]>
| Newsgroups | gmane.comp.cms.tiki.devel |
|---|---|
| Message-ID | <[email protected]> |
Thanks Jonny and Oliver, > I added an example snippet to https://doc.tiki.org/upgrade#Shell_Commands_for_swapping_versions_around after messing it up a few times. Notably the `shopt -s dotglob` magin incantation which makes the cp/mv command include hidden dot files and dirs... (on Debian) Like the second suggestion of Oliver (using rename old public_html to public_html.old ), this look like the "manual" way to me and that’s something I’m doing already more or less. However I never though about: > How about doing something like we do for next.tw.o? There's a script for that ( docs/devtools/update.dogfoodserver.sh ) that you could adjust with a proper database name/user/password/docroot folder? > Test it with a different URL, and if it works, just switch the content folders? The new content folder already points to the new DB, so it's a fast switch to the new version. > With the switch to the new DB you'd also have a new user/password combination, which is never a bad thing to do every now and then. This could be a neat solution and integrated in every Tiki version. While editing the file is not a big obstacle, it would just a perfect universal solution to use user input for those. I’m gonna work on a prototype so it also use a git branch instead of svn update. > Hope that helps a bit, we should probably add a new page for this kind of thing - "upgrade part 2" or something? > > jonny > > > > >> On 6 Aug 2021, at 16:30, Bsfez Tiki via TikiWiki-devel <[email protected]> wrote: >> >> Hello, >> >> I was wondering if someone has a good recipes for this. >> >> I have a Tiki22 in production built from a git repo and set with a virtualmin (Debian) server. >> I want to start testing a Tiki23 of this website. >> >> I need to setup a Tiki 23 and copy there some files (themes, etc) and use a clone of the db. >> >> Knowing that if it is working fine I want to use it instead of the actual Tiki22 what will be the best move ? >> - Create a domain for the Tiki23 and if it work fine, back to the main domain => rename the public_html (to keep it safe) and then copy the public_html file of the Tiki23 in the main domain ? >> - Rename the existing public_html (to keep it safe) and then with a new public_html install a Tiki23. (so I can mv the directories when I want to use the existing Tiki22 or new Tiki23) >> >> All this look a bit risky hazardous. >> >> Any good recipes more safe ? >> >> Bernard >> >> _______________________________________________ >> TikiWiki-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel >> > > > > _______________________________________________ > TikiWiki-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel _______________________________________________ TikiWiki-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel