Re: [Rest2web-develop] Mixing other files in with the HTML generated by rest2web

[Michael F. <fuz...@vo...>]

Eur Ing Chris Green wrote:
> On Wed, Mar 07, 2007 at 09:32:08PM +0000, Michael Foord wrote:
>   
>> Eur Ing Chris Green wrote:
>>     
>>> I'm considering using rest2web for maintaining my personal web of
>>> documents and other stuff that I keep on my home linux box.
>>>
>>> I have been writing some notes in reST already and have been using
>>> rst2html.py to convert them to HTML.  Since rest2web can automate this
>>> process and add menus etc. it seems like it may help me.
>>>
>>> However I'm not quite sure how to manage other information and
>>> documents like PDF files, I really want to keep this in the same
>>> directory hierarchy as the information.  E.g. I have a workshop manual
>>> for my motorbike in PDF format and would like to keep this in the
>>> motorbike directory along with a couple of HTML files created by
>>> res2web.
>>>
>>> I don't see any clean/easy way to do this, it might be possible by
>>> adding lines to the individual restindex sections if the index.txt
>>> files but this seems a bit clumsy.  What I really want is for rest2web
>>> only to build the files it needs to and to leave the existing
>>> directory hierarchy of the output in place.  Or am I confused and it
>>> does that already?
>>>
>>> E.g. if I have a directory somewhere down the output hierarchy called
>>> motorbikes and it has a file zzr1200.pdf in it will rest2web delete
>>> that file when I run r2w.py or will it only delete/overwrite the HTML
>>> files it creates from .txt files?
>>>
>>>   
>>>       
>> rest2web *never* deletes files from the output directory (except when it 
>> has to overwrite them with a newer version).
>>
>>     
> OK, thanks, excellent!
>
>
>   
>> Additionally you can use the 'file' keyword in the restindex to copy 
>> files from the source directory into the output directory.
>>
>>     
> Ah, I had seen that but hadn't really understood what it did.
>
>
> Actually, for my requirements I think it could make sense to have the
> start_directory and target_directory set to the same directory. The
> idea is to have documentation and notes that I can read as text files
> (i.e. the reST format files) and as HTML web pages using the apache
> server running on the computer.  The HTML doesn't have to be exported
> anywhere.  Will this cause any issues?
>
>   
Shouldn't do.

Fuzzyman