Ciao Anjar My point was ONLY that .htaccess setup is NOT a TW issue. It is a server admin issue. So why are we talking about it?
In very smart TW like BOB you can manage the needed files in the online server version. But that is likely rare. Hope this clarifies the scope for you. TT On Monday, 9 November 2020 21:00:06 UTC+1, Anjar wrote: > > Hi TT, > > I'm not sure I follow your thoughts. For example, I have an online > tiddlywiki for sheet music and since some of the scores are in public > domain and others not, I separate them and protect the latter with > htaccess. That way I can still make a tiddler for it and tag it etc. and > embed the pdf with _canonical_uri and application/pdf, but restrict access > to myself only. > > Similarly, I guess it would be trivial to have a html/php form embedded in > tiddlywiki from a protected folder that creates "protected tiddlers" in an > otherwise public tiddlywiki, which at least I think expands the usability > of tiddlywiki, especially if it becomes possible to load those external > files at start and treat them as ordinary tiddlers. Just a thought:) > > Best, > Anders > > mandag 9. november 2020 kl. 18:17:08 UTC+1 skrev TiddlyTweeter: > >> Ciao Anjar >> >> ... you can have some content public but also put some content in a >>> subfolder protected by htaccess and include it in the tiddlywiki. Works >>> perfectly for pfs etc >>> >> >> Right. Though that is nothing to do with TW, or changes anything you do >> in it. >> >> The only TW bit I can see is you COULD use the Bob version to >> create/delete any needed .htaccess files on-the-fly. >> >> Thoughts >> TT >> > -- 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/c05acc35-f943-48b5-b9b2-6e818d4c0b12o%40googlegroups.com.
