Pat,<br><br>I went ahead and created a db for you. The credentials and privs are listed in a file in the board's directory. Let me know if it needs adjusted or anything. <br><br>Ted<br><br><div class="gmail_quote">
On Tue, Feb 14, 2012 at 12:04 PM, Pat Barron <span dir="ltr"><<a href="mailto:pat@lectroid.com">pat@lectroid.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 02/14/2012 1:13 AM, Vance Kochenderfer wrote:<br>
> I believe Pat was going to use an ssh tunnel (i.e., 'ssh -L<br>
> 3306:localhost:3306 <a href="mailto:user@wplug.org">user@wplug.org</a>') to communicate with MySQL.<br>
> This way, only the data lives on the server; the application is<br>
> entirely on his desktop.<br>
<br>
</div>Exactly. I talked to Ted a little bit yesterday and clarified that.<br>
<br>
I did a proof-of-concept at home last night (using Postgres as a<br>
back-end, just because it's what I happen to have running at home).<br>
Seems to work fine, and no GnuCash bits need to be installed on the<br>
server side. Just uses the DB for data storage.<br>
<div class="im"><br>
> This seems fine to me, with the proviso that we create a separate<br>
> MySQL user that *only* has access to this database. Principle of<br>
> least privilege and all that.<br>
<br>
</div>Works for me. ;-)<br>
<div class="im"><br>
> Pat, one thing to keep in mind is that the next treasurer may not<br>
> want to use the same tools. I know that at least once in WPLUG's<br>
> past, a treasurer has handed over his data files which were then<br>
> ignored by his successor. I'd recommend, in addition to the<br>
> database, generating something in plaintext that can be picked up<br>
> by anyone. Here's the format I used, FWIW. :)<br>
> <<a href="http://www.wplug.org/pipermail/wplug-board/2010-April/001703.html" target="_blank">http://www.wplug.org/pipermail/wplug-board/2010-April/001703.html</a>><br>
<br>
</div>True. That's why I'm trying to make it as simple as possible. I intend<br>
to have Treasurer's Reports in roughly the format you describe (to<br>
present at board meetings and GUMs), but that's just a snapshot in<br>
time. A "real" accounting system lets you view the history too.<br>
<br>
But yeah, my eventual successor would not necessarily care to do that.<br>
So by keeping it relatively simple, if the work gets thrown away later,<br>
it's no big loss. ;-)<br>
<div class="im"><br>
> To be honest, if MySQL can meet your needs, I'd prefer not to run<br>
> Postgres. Just want to avoid having another service to keep an<br>
> eye on.<br>
<br>
</div>MySQL would be fine. I just understand Postgres better (and run it at<br>
home), have been a Postgres user for a very long time. So I'm a bit of<br>
a Postgres bigot. But there's nothing Postgres can do for me that MySQL<br>
can't.<br>
<div class="im"><br>
> As I see it, you'd need:<br>
> 1. A MySQL username<br>
> 2. A password for that user<br>
> 3. A database (CREATE DATABASE gnucash ?)<br>
> 4. Privileges for the user on that database<br>
><br>
> Does any particular schema need to be set up for GNUcash to use?<br>
> Am I forgetting anything else?<br>
<br>
</div>I think that's it (and yeah, the DB name it expects is "gnucash" - the<br>
version of GnuCash I'm running on my desktop seems to get unhappy if the<br>
DB is called anything else, at least using the Postgres back-end). The<br>
user that accesses that DB doesn't need to have any access to anything<br>
else. GnuCash initializes the DB (with all the tables it needs and<br>
such) when you first set it up, all it needs going in is a "blank"<br>
database and access to it.<br>
<span class="HOEnZb"><font color="#888888"><br>
--Pat.<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
_______________________________________________<br>
wplug-internet mailing list<br>
<a href="mailto:wplug-internet@wplug.org">wplug-internet@wplug.org</a><br>
<a href="http://www.wplug.org/mailman/listinfo/wplug-internet" target="_blank">http://www.wplug.org/mailman/listinfo/wplug-internet</a><br>
</div></div></blockquote></div><br>