neechbear / tiddlywiki Goto Github PK

Hi folks,

Could I ask for ARM and other architecture support? The base Node image it relies on supports all kinds of architectures and personally I would like to run this on ARM64.

Please share your thoughts!

@neechbear Thanks for the work BTW!

$ docker run --rm -p 8080:8080 -v ~/wikidata:/var/lib/tiddlyiki --name mywiki nicolaw/tiddlywiki

This:

-v ~/wikidata:/var/lib/tiddlyiki

Should be:

-v ~/wikidata:/var/lib/tiddlywiki

Why does the Dockerfile explicitly expose port 8080?
Isn't declaring a port with docker run -p sufficient?

The systemd config is incomplete. It correctly starts the service in current session, but does not auto start on reboot. In order to set a service to auto start, it must be enabled. But upon trying to use the following command

sudo systemctl enable mywiki.service

it reports that the service unit file is missing the [Install] section.

Please review the config.

Hi, thanks for putting this together, it has been very helpful.

I wanted to configure the path that tiddlywiki would be available at. It does appear at that path, but tiddlywiki itself is broken. The following minimal example demonstrates the issue.

docker run -p 8080:8080 -e TW_PATHPREFIX=/wiki nicolaw/tiddlywiki 

The UI shows the following errors

I did see this in the documentation:
https://tiddlywiki.com/static/Using%2520a%2520custom%2520path%2520prefix%2520with%2520the%2520client-server%2520edition.html

Perhaps a comment to mention that additional changes are needed or perhaps something in init-and-run that automatically sets up path prefix would be great.

Hi there,
i am sure there is reason behind it, but i could not start via the docker-compose example.

https://github.com/neechbear/tiddlywiki#docker-compose

There is a part missing of the compose file, a random port declared i dont know the purpose of and the volume deceleration is missing.

a more helpful example would be

version: "3.9"
services:
  tiddlywiki:
    container_name: tiddlywiki
    image: nicolaw/tiddlywiki
    volumes:
      - tiddlywiki:/home/diab/tiddlywiki_data_safe
    ports:
      - "8080:8080"
volumes:
  tiddlywiki: null

Hi there,

First of all thank you for this Dockerized TiddlyWiki, it is really useful!

Secondly, I have a feature request: it would be nice if this Dockerized solution supported the pre-installation of specific TiddlyWiki plugins. I'm not exactly sure about how to automate downloading them, how they are identified and versioned, but it would make this project even more useful.

For context and some inspiration, to automate the installation of TiddlyMap I created a very similar project, which is heavily based on yours. And actually after finishing that I realized it would be much better if your project supported this use-case out of the box.

To accomplish it, I had to do 2 things:

• Download the plugins beforehand (in a separate stage in the Dockerfile),
• And then install them after initializing the server edition of TiddlyWiki.
• (I should also add the plugins to the generated tiddlywiki.info, but for some reason the plugins are loaded without that, so I just left that out.)

The step of downloading said plugins could be in the same init-and-run script, but we definitely need to copy them to their right destination after the wiki instance has been initialized.

I think the end goal should be to support the pre-installation of specific plugins via providing a simple text file of them, very similar to how the Dockerized Jenkins does it. We could achieve something similar by extending init-and-run.

What do you think?

Hello,

Would it be possible to merge the pull request to update the version in this container to 5.1.23?

Thank you!