On 25 January 2015 at 22:53, Daniel Baird danielba...@gmail.com wrote:
[...]Then your attack service is a bit narrower (well not exactly
narrower.. just more battle-tested).
Gah, typo silly me: surface. Your attack SURFACE is a bit narrower etc.
--
You received this message because you
Hi Captain Packers
The TW5 source doesn't currently support acting as an SSL server. As Daniel
says, the expectation is that in production people would want to terminate
their SSL connection with something more standard than TiddlyWiki.
Best wishes
Jeremy
On Sun, Jan 25, 2015 at 12:53 PM,
You can do SSL directly from a node server -- I don't know if Jeremy has
actually done it with the TW server, but it's not especially difficult.
However it's often a good idea to do SSL through a well-used and mature
proxy like nginx or apache. Then your attack service is a bit narrower
(well not
So I need to set up a proxy server?
On Thursday, January 22, 2015 at 11:58:00 AM UTC-5, PMario wrote:
TW doesn't need MySQL + PHP + Perl
So you basically would have enough with an xa Apache environment and
apache set up as a proxy.
Do you want to expose your node tw to the web?
-mario
TW doesn't need MySQL + PHP + Perl
So you basically would have enough with an xa Apache environment and
apache set up as a proxy.
Do you want to expose your node tw to the web?
-mario
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To
yes, but I want to use an ssl port. I can't figure out how to do it. Do I
have to hack tiddlywiki.js and set up a secure node.js server within the
tiddlywiki.js file before tiddlywiki is booted? seems like there should be
some tiddlywiki command line arguments to set up a secure server if there
6 matches
Mail list logo
