Hi Heusmich,

I think a first option could be to serve a tiddlywiki file via WebDav : not
only it can give access to the wiki from anywhere on your network, but it
will also handle the saver operations without any further configuration.
There are many WebDav services available for the Linux platform, but Rclone
is probably one of the most easy to use, yet very powerful.

So a basic, unsecure, command for serving a TiddlyWiki file that resides in
your ~/public_html/wikis repository with Rclone (let's call it mywiki.html)
would be:

rclone serve webdav ~/public_html/wikis/ --addr 0.0.0.0:8998

That's it! As you guessed, it will make all the files present in
~/public_html/wikis/
available at the port 8998 on your Linux machine. So if your server has the
IP address 192.168.1.3 on your network, pointing a browser to
http://192.168.1.3:8998/mywiki.html will serve the file mywiki.html on
HTTP, and write any modifications directly on the same file.

As Mario noted, such a simple setup means that you must really trust your
network. Even if you are the only person who uses it, some applications
running on your other machines can easily discover your WebDav service, and
do whatever with your wiki file.

The next step would thus be to add an authentication file with htpasswd.
The command "htpasswd -cB .myhtpasswd.txt me" would ask you a password for
the user *me*, then create the file .myhtpasswd.txt with that password
encrypted.

Now you can reissue a slightly more secure command:

rclone serve webdav ~/public_html/wikis --htpasswd ~/.myhtpasswd.txt --addr
0.0.0.0:8998

Each time someone wants to connect to http://192.168.1.3:8998, (s)he will
be asked for their credentials. But if an application is sniffing your
network, it will see the password as you type it.

The next step would thus be to add a key and a certificate so that rclone
serves through HTTPS instead of HTTP. https://tiddlywiki.com/#Using%20HTTPS
explains how to generate the key and the self-signed certificate.

Once you have the cert and the key file, you can enhance the above command
by issuing:

rclone serve webdav ~/public_html/wikis --htpasswd ~/.myhtpasswd.txt --addr
0.0.0.0:8998 --cert ~/.tls/server.crt --key ~/.tls/key.pem

This is more reasonable, although you'll notice that your browser complains
that the certificate is self-signed.

Now you are ready to try a different approach, that is serving your wiki
through NodeJS. See the two tiddlers at
https://tiddlywiki.com/#WebServer:%5B%5BInstalling%20TiddlyWiki%20on%20Node.js%5D%5D%20WebServer

Regards,
-- Xavier Cazin.


On Wed, Feb 9, 2022 at 11:07 AM 'heusmich' via TiddlyWiki <
[email protected]> wrote:

> Hi @all,
>
> Is there a possibility to use TiddlyWiki on my dedicated Linux root server
> (Ubuntu 20.04 LTS)?
> If possible I would love it to have access to the wiki from everywhere and
> can also make it available for other users.
>
> It would also be good to have two different access possibilities.
> So for example when you open the link to the wiki you can only read the
> entries of the wiki.
> And the other possibility would be to log in, then you can edit the
> entries, create new entries and so on...
> And maybe it is possible not to make all entries of the wiki visible to
> all users, so for example make some entries invisible unless you are logged
> in.
>
> Can anybody tell me if this is possible and - if yes - how I can realize
> this?
>
> Best regards
> heusmich
>
> --
> 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/94ce1533-74e4-42bd-b081-807f6132f925n%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/94ce1533-74e4-42bd-b081-807f6132f925n%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/CADeSwYOsTe-O5qyCW5vz8EpS6NGUvPUJF7S%3DTAsT48xm5i%2BMRg%40mail.gmail.com.

Reply via email to