Hi, maybe you could try my port version of widdly: https://github.com/cs8425/widdly It was written in golang, and have 3 different type of backend storage. But not yet serve different wikis on different paths. I'm not sure I had enough time to done this feature, but you can still using a reverse proxy to redirect each path to different widdly instance.
Or if you did not mind the bandwidth, than you can simply use any WebDAV server to host tiddlywiki. (will upload whole html file on each save) here are a simplest http server that can serve tiddlywiki: https://github.com/cs8425/go-smalltools/blob/master/network/httpd.go You may need to add some authentication methods by yourself. I hope these would help you. :) Enrico Guiraud於 2019年12月20日星期五 UTC+8下午11時59分31秒寫道： > > Hi all, > big fan of tiddlywiki (I routinely use 3, hosted on a VPS) and recently I > started advertising it to my friends. > To get more people into tiddlywiki, I just set them up for them on my VPS. > > The problem: I'm now serving an average of 5-6 tiddlywikis, and my little > VPS is almost out of RAM: each tiddlywiki server uses 110 MB or more. > That's _a lot_, isn't it? > > Can anyone suggest ways to reduce memory usage when serving multiple > tiddlywikis? > > Would it be possible to have one server serve different wikis on different > paths (and if so, would it help)? > > > Does anyone know what causes the large memory usage and whether it can be > optimized? I would be willing to put some hours into this -- am a > developer, but don't know much about javascript. > > > Cheers, > > Enrico > -- 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/ea348247-4a42-458d-9db2-0964574520a2%40googlegroups.com.
