I know it's been a while but I've mostly finished the Note Self CouchDB 
setup tutorial 
<http://thelostadmin.tiddlyspot.com/#How%20to%20Setup%20CouchDB%20for%20Note%20Self>.
 
It should get you to the point where you actually have a working Note Self 
& CouchDB test environment. Anyone willing to test, please do so and let me 
know where things aren't as clear as they could be.

I need to reset my Windows setup and re-built it to get a few more screen 
shots (and validate I didn't miss anything).

Once that is done, I'm going to make a second tutorial that adds HTTPS 
support and makes it reasonable to consider putting it on the Internet. You 
can get a VM for as little as US$2.50 that is sufficient for a single user, 
so I figured HTTPS would be worth explaining. I'm currently doing this with 
Vultr.com (https://www.vultr.com/?ref=7210118)[1] and using Note Self as a 
privately hosted One Note alternative. 

Once I'm done with the tutorials I will configure the CouchDB on my home 
computer to sync with the one on Vultr so that I even have off-site backup. 
I'll probably make a tutorial on this as well. It is dead easy.

[1] If you sign up with Vultr and pay for hosting, I get a token amount of 
credit for directing you there. If this is considered inappropriate for 
this forum, let me know and I'll remove the link and mention of Vultr.

On Friday, May 18, 2018 at 10:30:32 AM UTC-4, Lost Admin wrote:
>
> A while back PMario made a video on how to set-up a webdav server on IIS 
> <https://groups.google.com/forum/#!searchin/tiddlywiki/ISS$20Webdav%7Csort:date/tiddlywiki/_YwmiKqMyrI/H_nGBYs9CgAJ>.
>  
> I also made some observations on tiddlywiki's WebDAV saver using Apache 
> HTTP. Since then, the issue I had in my observations has been corrected 
> (awesome work by the way to Jeremy and anyone who helped). As far as I can 
> tell the WebDAV Saver works very well on IIS webdav and Apache webdav (I 
> run both).
>
>
> I imagine many people on this list are technically savvy and capable of 
> setting up their own server for TiddlyWiki. But I do wonder if there are 
> people who want to do so but would like a tutorial to follow.
>
> When I first found Tiddlywiki, I initially used the download saver. 
> Shortly after I learned about TiddlySpot and started using it (I still do). 
> That lead me to finding out how it works and learning about "store.php" and 
> the various GitHub repositories for variations of it.
>
> When the WebDAV saver became available, I switched my home server (just a 
> little always-on Intel NUC) to use WebDAV and removed store.php (and PHP). 
> Lately I've been playing with Note Self, which uses the Apache CouchDB as a 
> back end database, and set-up my own small infrastructure on vultr.com 
> (cloud vm hosting).
>
> None of what I've done is particularly exciting but it does require a 
> certain amount of knowledge. For the most part, I found tutorials on how to 
> set-up the various components, followed them, and then read documentation 
> and fiddled with settings until I was satisfied everything worked smoothly.
>
> What I didn't do, was create good documentation on how I actually did what 
> I did. Before I actually set-out on doing so, would people actually use it?
>
> or
>
> How many of you want to set-up your own dedicated server for TiddlyWiki 
> but want a tutorial to follow?
>
> I'll be creating one for a basic self-hosted Note Self 
> <https://noteself.github.io/> CouchDB back-end and posting it on the Note 
> Self forums <https://forum.noteself.org/> regardless.
>
>

-- 
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4d048138-fca6-4548-a798-8290e597d638%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to