Hi Olegh, I reviewed your protw projects (nice!) and saw that there is additional configuration information in the "tiddlywiki.info" file.
But I'm not familiar with the configuration syntax, or the "rendertiddler(s)" stuff... So I'm still stuck trying to understand how to configure a build for a single html file. Let me re-state my use case, because I don't think I made myself very clear: 1. When a new user (me) wants to try TW5, I download a new empty wiki file. 2. I end up with a single HTML file, that I can name to something like: 'my-new-project.html". 3. (Well, we know it's not "just" an HTML file, it's also whole lot of JavaScript "black-magic" as well). 4. I get busy & make a bunch of new tiddlers, maybe hundreds. But to naive user (me) it's still a single HTML file. 5. I want to upload "my-new-project.html" to my own fork <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2FChintiminiFarm%2Fshare-project-proposal&sa=D&sntz=1&usg=AFQjCNHHosExYreECbD5n0Wg4Yk8Jn6hyw> and have it served from there. 6. I see the current build configuration of the tw5-auto-publish2gitlab-pages <https://www.google.com/url?q=https%3A%2F%2Fgitlab.com%2Fdanielo515%2Ftw5-auto-publish2gitlab-pages%2Ftree%2Fmaster&sa=D&sntz=1&usg=AFQjCNF452_Yyr_XVgy8-eyvs87CM553XA> system seems to be based on .tid files. 7. But if you try to "export all tiddlers" into a tid file, you find out that TW5 only exports a single tiddler. 8. So, you are stuck (it seems to me). So, I would like to upload this single "my-new-project.html" file into the project space, in whatever appropriate spot is best, and configure it (with appropriate syntax) in the "tiddlywiki.info" file. - Can that be done? and... - Can you give my the "tiddlywiki.info" syntax for that? Best regards, -- Daniel On Tuesday, November 21, 2017 at 6:34:19 AM UTC-8, oleghbond wrote: > > Dear Daniel, > > thanks to Danielo I accepted and use regularly this approach. Please look > at my site github.com/protw and one of my projects > https://github.com/protw/tw5 dedicated to TW5 (in Ukrainian) where I put > an instructions how to deploy TW5 project at Github + Github Pages (2.2, > 2.2.1 - 2.2.4). > > The way how to build the resulting wiki is determined in tiddlywiki.info > <https://github.com/protw/tw5/blob/master/wiki/tiddlywiki.info>. There > you can see section "build" having two subsections "static" and "index" for > two different representations of resulting wiki. > > Actually you may check these two results visiting the following pages > (accordingly): > > - https://protw.github.io/tw5/static > - https://protw.github.io/tw5 > > Sincerely, > > Olegh Bondarenko > http://goo.gl/bzDZfd > > > > > 2017-11-20 23:46 GMT+02:00 Daniel Cunningham <daniel.phill...@gmail.com > <javascript:>>: > >> Hi Danielo, >> >> I have been experimenting with my own fork >> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2FChintiminiFarm%2Fshare-project-proposal&sa=D&sntz=1&usg=AFQjCNHHosExYreECbD5n0Wg4Yk8Jn6hyw> >> >> of your tw5-auto-publish2gitlab-pages >> <https://www.google.com/url?q=https%3A%2F%2Fgitlab.com%2Fdanielo515%2Ftw5-auto-publish2gitlab-pages%2Ftree%2Fmaster&sa=D&sntz=1&usg=AFQjCNF452_Yyr_XVgy8-eyvs87CM553XA>. >> >> I haven't messed around with either GitHub or a continuous integration tool >> like Travis CI before, so it was fun learning about those. Thanks for the >> extensive effort and clear expertise you have put into this project. >> >> My purpose for this exercise is that I want to share a TW5 wiki (a >> project that I've been building on my local machine) and I thought that >> sharing it as a page from GitHub (or GitLab) would be... nifty. >> >> I see that the "user content" part of your configuration is based around >> a single .tid file, and that it looks like you use the Travis CI tools to >> use a YML file to auto-generate an index.html file from a .tid file (and >> then run some other scripts as well). Is that correct? >> >> My bigger question: Is there a way to (re) configure this system so that >> I could upload an HTML file (that is a complete TW5 wiki) that I want to >> share? I found out that exporting as a .tid file only exports a single >> tiddler, and I have an extended wiki with many (as in hundreds) of >> individual tiddlers that I want to share. So as it stands right now, I >> can't use your system to share a completed TW5 wiki from my local machine. >> Unless of course, I'm missing something really obvious (which I am the >> first to admit happens all the time). >> >> I have (zip|zero|nada) experience with Travis CI and/or YML files, but >> perhaps there is some specification I could configure that would let Travis >> CI reach in and use a target HTML file (in other words, my source TW5 wiki) >> and use that to generate the index.html? >> >> The best of all possible worlds for me would be to upload a TW5 wiki as a >> single HTML file into the wiki directory, edit one or more config files to >> say: "look for this target HTML file", let Travis CI detect the push event >> and have the auto-config "magic" do its stuff. >> >> >> Best regards, >> >> -- Daniel >> >> On Thursday, September 24, 2015 at 11:58:38 AM UTC-7, Danielo RodrÃguez >> wrote: >>> >>> >>> Motivated for Matabele's post about how and where host tiddlywiki files >>> I want to announce that I have been investigating and looking for a way to >>> do this easily on Github pages. >>> We all love Github pages. They are an easy,reliable and cheap way to >>> host static sites. TiddlyWiki >>> <https://github.com/danielo515/TW5-auto-publish2gh-pages/blob/master/tiddlywiki.com> >>> is >>> a single page web application that can be hosted as a single html file. The >>> problem with it is that there is not an easy fast way to host a tiddlywiki >>> file on github pages... until now. >>> >>> I have created a repository/tutorial to host a tiddlywiki on your own >>> Github pages repository. Following it you will be able to have your own >>> wiki up and runing in less than 10 minutes *without* any git or Github >>> Knowledge and *without installing* any software on your computer: >>> >>> https://github.com/danielo515/TW5-auto-publish2gh-pages >>> >>> Sounds pretty neat uh? >>> >>> @Jeremy, If you feel that this could be useful, feel free to add it to >>> the community resources. Maybe I can create a small tiddler pointing to the >>> tutorial. In fact it is similar to "hosting a tiddlywiki on dropbox", so it >>> can be a tiddler of the same category. >>> >>> Questions, ideas, doubts and pull requests are very welcome. >>> >>> Regards >>> >>> >>> >>> I just added suppor for gitlab pages. The workflow is much easier, is >>> just a matter of clonning the repository on your gitlab account. For the >>> momment please ignore the readme, it is the version of github. >>> https://gitlab.com/danielo515/tw5-auto-publish2gitlab-pages >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "TiddlyWiki" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/tiddlywiki/s8pnvQW5UgY/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> tiddlywiki+...@googlegroups.com <javascript:>. >> To post to this group, send email to tiddl...@googlegroups.com >> <javascript:>. >> 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/239ec11f-ac8d-442a-afe6-db586f32fc82%40googlegroups.com >> >> <https://groups.google.com/d/msgid/tiddlywiki/239ec11f-ac8d-442a-afe6-db586f32fc82%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. 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/453a481d-a3f8-4ff6-999d-ade6679b98e4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
