Hi,

I am an apache ignoramus who has been trying to follow these instructions on a Debian 3.1 box.  I got hung up for
the following reason.  I had to explicitly enable some apache features, which was a simple matter of making the
following symlinks in /etc/apache2/mods-enabled: 

	proxy.conf -> ../mods-available/proxy.conf
	proxy.load -> ../mods-available/proxy.load
	rewrite.load -> ../mods-available/rewrite.load
	headers.load -> ../mods-available/headers.load
	ssl.conf -> ../mods-available/ssl.conf
	ssl.load -> ../mods-available/ssl.load

Easy enough.  The default proxy.conf has sensible-looking warnings about not running your server as an open proxy.
 However, I wasn't able to tweak it to encrypted port forwarding from :443 to :8079.

What I've done that works is to add a local proxy section to the /etc/apache2/conf.d/elogredirect.conf by Damon
Nettles:

	<VirtualHost *:443>
		### ... everything else

		<Proxy *>
			Allow from all
		</Proxy>
	</VirtualHost>

I think, since this is in a subsection, that it only affects that virtual host.  But it'd be nice if someone who
actually understands this language would reassure me that I'm not setting myself up for some security hole.  At
any rate it took me long enough to figure this out that I thought I'd post a note in public, and this seems like
the forum to do so.

Thanks.

Rob

> Hi Stefan,
> 
> I'm starting to get a similar problem to Lance's ("SQL Database").  Searching is beginning to take time.
> 
> In searching, I either can search one logbook (still relatively quick), or all of them.
> 
> I have my logbooks in groups, and often I know which group I want to search, and it would make the searching
> much quicker were the search confined to just that group.  I don't think I've missed anything in the
> documentation on this matter.  
> 
> If not a change to the elog program, is there another way of (say) arranging the logbooks that will achieve this?

You can't do that right now. I would have to extend the functionality to allow searching in groups. Also have a look 
at https://midas.psi.ch/elogs/Forum/66901. Maybe that helps a bit in meantime.

Hi Stefan,

I was rather hoping that was *not* going to be your answer.

I much prefer the plain ascii file format, for it allows me to edit it for "mistakes" post submission, 
shall we say. 

> > Hi Stefan,
> > 
> > I'm starting to get a similar problem to Lance's ("SQL Database").  Searching is beginning to take time.
> > 
> > In searching, I either can search one logbook (still relatively quick), or all of them.
> > 
> > I have my logbooks in groups, and often I know which group I want to search, and it would make the searching
> > much quicker were the search confined to just that group.  I don't think I've missed anything in the
> > documentation on this matter.  
> > 
> > If not a change to the elog program, is there another way of (say) arranging the logbooks that will achieve this?
> 
> You can't do that right now. I would have to extend the functionality to allow searching in groups. Also have a look 
> at https://midas.psi.ch/elogs/Forum/66901. Maybe that helps a bit in meantime.

There are no specific classes for the search dialog, but you can play with the classes "form2", "attribname" and "attribvalue". These classes are used in several places, so all will change in the same way, but maybe that's what you like. 

 Understand.. So when a search/sort is done, the searched item come up with a yellow background... 

The thing is, if you set a "Cell Style XXX= background-color: ZZZ" it become useless since it is replace with the yellow background.

I tried to play with the css but I couldnt figure it out... So you say I cant do anything about it ? I'm just wondering where this yellow color comes from :)

vs the way I would like it to be :

That question screams: please read the manual! Find command: https://elog.psi.ch/elog/userguide.html#browse

Search all logbooks = 2

No. You can either search one logbook or all logbooks. There is however the way to have separate groups of logbooks, which are "invisible" from each other. Like running several elogd daemons at the same time. Then your search on all logbooks will only run on the logbooks of one group. Check the documentation for "top groups".

- Stefan