arildb_: joined #tikiwiki
arildb: joined #tikiwiki
fabricius: gour just additional features and things easier - Ricks books are still good for the basics and first steps
gour principles remain
refizul: fabricius: gour cannot hear you ;-)
lindonb: joined #tikiwiki
fabricius: joined #tikiwiki
luciash: polom
lphuberdeau: left #tikiwiki
lindonb: joined #tikiwiki
goj_killedByISP: joined #tikiwiki
Enrique: joined #tikiwiki
Hola, buenas noches a todos, ¿alguien sabe cómo traducir el cms wiki al español?
luciash: hola Enrique, I do not speak Spanish but if you mean help with translation to Spanish, try http://i18n.tiki.org
Enrique: Hello, thank you very much for the link, I'm seeing now.
luciash: or contact Xavi: http://tiki.org/UserPagexavidp
he speaks Spanish and Catalan at least ;)
Enrique: Thank you!
arildb_: joined #tikiwiki
fabricius: joined #tikiwiki
gour: joined #tikiwiki
fabricius: refizul: gost it after writing, bust thx anyway
gour: what is the procedure to move installation from one TLD to the other? all i see are notes from moving from one server to the other...
fabricius: joined #tikiwiki
redflo: joined #tikiwiki
fabricius: joined #tikiwiki
luciash: gour: u just change any custom modifications to your .htaccess and Admin > Login remember me session cookie domain to your TLD
gour: and if u mean Google search position, u has to tak care of the 301 redirect manually, but that is not Tiki specific
gour: luciash: first of all i plan to use tiki with nginx and second, no need to redirect...i just want to play with tiki on my localhost and/or on staging server and when accomplishing something move to production TLD, so wonder how to adjust installation settings to work when changing from tld1 to tld2 without htaccess/redirect magic?
is there support for disqus comments available for tiki blog? i've WP site using disqus and wonder what to do...
rinnan: left #tikiwiki
steve____: joined #tikiwiki
rinnan: joined #tikiwiki
marclaporte: joined #tikiwiki
dhazel: joined #tikiwiki
steve____: joined #tikiwiki
redflo: joined #tikiwiki
lorinc: joined #tikiwiki
marclaporte: joined #tikiwiki
-: gour watched floss weekly 'tiki' episode...nice job by marclaporte ;)
marclaporte: thanks!
I wish I could have debatted him more!
The show was shorter than usual because of tech issues (audio) at the beginning
There is a podcast here too: http://info.tiki.org/article188-Tiki-reaches-500-contributors-with-commit-access
gour: i like that simplicity and pragmatism are part of the project...feeling much better reading tiki stuff than the feeling i had with typo3's complexity :-)
marclaporte: :-)
gour: i guess the project will stay with svn for the foreseeable future?
marclaporte: The official source, yes
gour: i tried cvs in the past, skipped over svn and jumped to darcs...later tried mtn, using bzr & hg for some time and recently a bit of git...but for personal stuff i use fossil now
not having many branches (i assume so), fossil is also nice (possible) fir for tiki
marclaporte: But Louis-Philippe Huberdeau is working on a Git / Github mirror project. The goal is to make it easier / have a "suggested" method of maintaining local patches and for deep customizations
gour: yeah, dvcs helps here...i have a habit to keep all my writings/code under (d)vcs
nice thing about fossil is that it, as richard hipp (author of it & sqlite) put: "github-in-a-box" combining, wiki, tracker & code
marclaporte: Interesting. They obviously dogfood, and Ohloh doesn't support source analysis: https://www.ohloh.net/p/fossil-scm
interesting: http://www.fossil-scm.org/index.html/doc/trunk/www/wikitheory.wiki
gour: well, it's C
single executable very easy to build/upgrade
it favours security over speed...and very simple to operate
marclaporte: For a small project, I am actually considering if we should improve Tiki to become a VCS... (!)
gour: heh
fossil, based on sqlite3, is nice example
marclaporte: I am looking for the best way to manage source code the themes and extra translations for http://profiles.tiki.org/Cartograf. We have images, some js, some Smarty templates
And I am entertaining this idea: http://dev.tiki.org/PluginArchiveBuilder
And I want this: https://dev.tiki.org/Web+commits
gour: fossil is nice 'cause the whole repo (in this case, images & code...) is contained in a single & portable sqlite3 db file