Hi Xavier,
Thanks for your telling. I found only one occurence
of default-tiddler-location and that's in $:/boot/boot.js
<http://localhost:8080/#%24%3A%2Fboot%2Fboot.js> :
if ($tw.boot.wikiPath == wikiPath) { $tw.boot.wikiTiddlersPath =
path.resolve($tw.boot.wikiPath,config["default-tiddler-location"] ||
$tw.config.wikiTiddlersSubDir); }
Well... so what? Where is the change I should made? Is that a modification
within $:/core/modules/config.js ? I have not found any reference to fr-FR
so I assume it was deducted from the name of the file/plugin.
Where are the sources for fr-FR and fr-FR-server?
I have found the same problem with es-ES-server and ko-KR-server which are
the two only other translated server editions.
Regards,
Le mercredi 15 septembre 2021 à 15:20:35 UTC+2, [email protected] a
écrit :
> Hi Jean-Pierre,
>
> Historically, the fr-FR and fr-FR-server editions were aimed at providing
> a translated version of tw5.com. I had wanted to gather a team of
> translators in order to achieve this, but I eventually gave up as the task
> seemed too daunting. I focused instead on the fr-FR language plugin.
>
> What you experience — tiddlers are saved in the fr-FR sub-directory
> instead of the served wiki — is probably due to the
> "default-tiddler-location": "../fr-FR/tiddlers" in the config of the
> fr-FR-server edition. If you remove that before you --init a new wiki, you
> will get a more natural behaviour. If you confirm that it solves the
> problem, I'll propose a removal from the official edition.
>
> Cheers,
> -- Xavier Cazin.
>
> On Wed, Sep 15, 2021 at 12:43 PM Jean-Pierre Rivière <
> [email protected]> wrote:
>
>> Hi @PMario and mauloop!
>>
>> I(ve taken my time but I can now bring some valuable new input. But
>> before that, let me thank you for your answers. I've dipped deeper in
>> docker and nodejs tiddlywiki as a result. And I can tell you that I've
>> finally come to a successful setup but some problems are still there. But I
>> can create an OK docker image and use it to launch it a suceesfull
>> tiddlywiki and load stuff inside before really launching it as a server (I
>> have not yet seen how to use apache as a proxy).
>>
>> So for the sake of answering my question, here is my Dockerfile:
>> ---------
>> # Dockerfile pour lancer le tiddlywiki proteva
>> # copiée et adaptée du modèle elasticdog/tiddlywiki disponible sur le
>> docker hub
>> from node:16.9.0-alpine3.11
>>
>> LABEL author="Jean-Pierre RIVIÈRE"
>> LABEL content="instance de nodejs avec le tiddliwki proteva"
>>
>> env TIDDLYWIKI_VERSION=5.1.23
>> env PROTEVA_FEED=proteva-data.json
>> env WORKDIR=/usr/share/tiddlywiki/proteva-wiki
>>
>> EXPOSE 8080
>>
>> WORKDIR $WORKDIR
>> VOLUME $WORKDIR
>>
>> run apk update && apk add --no-cache tini
>> run npm install -g tiddlywiki@$TIDDLYWIKI_VERSION && npm install clean
>> --force
>>
>> #ENTRYPOINT ["tiddlywiki", "proteva"]
>> #CMD ["--listen", "host=0.0.0.0"]
>> ENTRYPOINT ["/sbin/tini", "--"]
>> CMD ["tiddlywiki", "proteva", "--listen", "host=0.0.0.0"]
>> ------
>>
>> and here is my proteva.sh script that I use to manage the wiki with
>> ./proteva.sh init && ./proteva.sh start
>> --------
>> #!/bin/sh
>> # shell pour initialiser ou lancer proteva via docker
>>
>> IMAGE=proteva
>> WIKI=$IMAGE
>> PROTEVA_FEED=proteva-data.json
>> PROTEVA_DIR=$PWD/proteva-data
>> WORKDIR=/usr/share/tiddlywiki/proteva-wiki
>> EDITION=rerver
>>
>> case $1 in
>> init)
>> echo wiping $PROTEVA_DIR
>> [ -d $PROTEVA_DIR ] && sudo rm -rf $PROTEVA_DIR
>> mkdir $PROTEVA_DIR
>> echo building $IMAGE docker image
>> sudo docker build . -t $IMAGE
>> echo built
>> sudo docker run --rm -v $PROTEVA_DIR:$WORKDIR $IMAGE tiddlywiki $WIKI
>> --init $EDITION
>> echo initialized
>> cp $PROTEVA_FEED $PROTEVA_DIR
>> sudo docker run --rm -v $PROTEVA_DIR:$WORKDIR $IMAGE tiddlywiki $WIKI
>> --load $PROTEVA_FEED
>> rm $PROTEVA_DIR/$PROTEVA_FEED
>> echo import done
>> ;;
>> start)
>> [ -d $PROTEVA_DIR ] || mkdir $PROTEVA_DIR
>> sudo docker run --rm -it -p 8080:8080 -v $PROTEVA_DIR:$WORKDIR --name
>> $WIKI $IMAGE tiddlywiki $WIKI --listen host=0.0.0.0
>> ;;
>> *) echo "usage : ${0##/} ORDER"
>> echo ' where ORDER is either "init" or "start"'
>> echo ' to initialize or launch proteva tiddlywiki nodejs via
>> docker.'
>> ;;
>> esac
>> ----------------
>>
>> Now for the remaining problem: the fr-FR-server edition seems at fault.
>> If I use iti instead of server (as value of the EDITION variable in the
>> script)' the --init and --listen part is OK (launching the "proteva" wiki),
>> the --load part is wrong for the data are copied in the fr-FR sub-directory
>> (instead of the proteva sub-directory). Besides, I can't see any French
>> with that edition.
>>
>> the real command I use is:
>>
>> sudo docker run --rm -v
>> /home/jnpr/big/workspace/accessibilite/dockerized/proteva-data:/usr/share/tiddlywiki/proteva-wiki
>>
>> proteva tiddlywiki proteva --load proteva-data.json
>>
>> This commands create this strucure all of its own:
>>
>> proteva-data
>> ├── fr-FR
>> │ └── tiddlers
>> │ ├── $__StoryList.tid
>> │ └── TODO.tid
>>
>> (proteva-data is created previously along proteva-data/proteva by --init)
>>
>> Where can I get the fr-FR sources/fellows of this project to help sort
>> out this mystery?
>>
>> Le dimanche 12 septembre 2021 à 00:59:09 UTC+2, mauloop a écrit :
>>
>>> I published on Github a little project to run Tiddlyserver with Docker.
>>> You can find it at https://github.com/mauloop/tiddlyserver-docker.
>>> It allows multiple wikis within a single server instance and custom
>>> editions path.
>>>
>>> I made it for my own use, so it does not provide very rich
>>> documentation, but just a quick and dirty readme with minimum commands
>>> needed to get started. However it could fit some of your requirements.
>>>
>>> Finally here is good example about how to set up Apache to proxy a
>>> Nodejs TW5 <https://nicolaw.uk/#:TiddlyWikiApacheProxy%20Hello>. I
>>> think it could work with TiddlyServer too with very little changes, but I
>>> never experienced this.
>>>
>>> Hope this could help. Have fun, )+(auloop
>>>
>>> Il giorno giovedì 9 settembre 2021 alle 23:23:54 UTC+2
>>> [email protected] ha scritto:
>>>
>>>> Hi everybody!
>>>>
>>>> I need to have some of my tiddlywiki being onto nodejs to gain some
>>>> functionality. For this, I have selected docker to have iti as easy as I
>>>> can. Besides docker, I need some shell script to setup the wiki (docker
>>>> images) ready to launch (listen command). Good point: this was an occasion
>>>> for me to invest into docker.
>>>>
>>>> But there remains a problem, which is that of the tiddlywiki edition.
>>>> the "editions" command list the available options with a quick summary.
>>>> But
>>>> some options would gain a little more explanations, like the
>>>> server-external-js which seems to mean that the js is not mangled inside
>>>> the js. That could be useful to serve several wikis from the same server.
>>>>
>>>> But in fact, I need a localized edition. Alas, editions are not
>>>> cumulative (but the server-external-js really should be an option and not
>>>> a
>>>> proper edition because that's not an editorial difference at all and it
>>>> could be useful for many editions).
>>>>
>>>> By localized, I mean that I want the content in French, but without all
>>>> the fuss of fr-FR editions which I would need to get rid of but for a few
>>>> tiddlers (and this would be a burden to implement and maintain). As for
>>>> the
>>>> fr-FR-server, the interface has not been translated (I wonder what has
>>>> been
>>>> translated and where I could find this information?)
>>>>
>>>> docker code used (without the volume and port stuff) on my tiddlywiki
>>>> docker image tiddock:
>>>>
>>>> docker run -d --rm tiddock wiki --init fr-FR-server
>>>> docker run -d --rm tiddock server host=0.0.0.0
>>>>
>>>> (I used elasticdog Dockerfile and shells to see what was needed to do.
>>>> Thanks elasticdog!)
>>>>
>>>> Also, if I understand what is said here, I must not directly use
>>>> tiddlywiki for a production wiki but use a proxy liki nginx can provide. I
>>>> have no knowledge of nginx so far. Where could I find some useful docs or
>>>> sources of a tiddlywiki with this kind of setup?
>>>>
>>>> Thanks in advance for your help.
>>>>
>>>> --
>> You received this message because you are subscribed to the Google Groups
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/tiddlywiki/f81dff53-55f4-4d85-b0b7-07605729288dn%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/tiddlywiki/f81dff53-55f4-4d85-b0b7-07605729288dn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/bfb26cd2-0fe4-4179-bc98-4177d069d776n%40googlegroups.com.