I assume Trac calls some Python module that implements SMTP directly,
which means it acts as its own MTA.
Keep in mind, though, that all of the cert stuff would probably still
have to be done since gmail's smtp server requires the use of TLS,
which requires the cert.
On 11/5/07, Adam Dewitz <[EMA
The TLS stuff is external to sycamore - it is part of the config of
your mail transfer agent. How to config this differs depending on the
MTA you're using.
Here's a tutorial on how to do it on ubuntu with postfix:
http://prantran.blogspot.com/2007/01/getting-postfix-to-work-on-ubuntu-with.html
our URLs to look pretty you /really/ need to
> look into using SCGI or FastCGI!
>
> --philip
>
> On 6/18/07, Rottenchester <[EMAIL PROTECTED]> wrote:
> > Ooops, left this out of my cut and paste:
> >
> > Alias /wiki /home/rocwiki/trunk/share/web/wiki
> >
Ooops, left this out of my cut and paste:
Alias /wiki /home/rocwiki/trunk/share/web/wiki
Don't worry about the /doc alias. Apache includes that so you can
read apache doc from your web server - t's not used for anything else,
AFAIK.
On 6/18/07, Far McKon <[EMAIL PROTECTED]> wrote:
> The change
1. I don't know what your config does, but Rocwiki and the test wikis
are all on cgi. In sycamore_config.py, relative_dir is set to '', and
then apache config has the following:
ScriptAlias / /home/rocwiki/trunk/share/web/index.cgi/
That redirects all URLs to index.cgi.
2. I'm not 100% sure w
write it.
>
> Just to be clear, you really mean *everything* below the level of
> /hosted/sapling_base, Including all subdirectories including 'share',
> 'Sycamore' should be all rights for the 'webserver user' ?
>
> I'm rusty on edit permissions
This is the key:
IOError: [Errno 13] Permission denied:
'/hosted/sapling_base/share/data/dicts.pickle'
You need to change the permissions on that data dir and everything
under it so your web server process can read and write it.
On 6/12/07, Far McKon <[EMAIL PROTECTED]> wrote:
> When I try to ad
Great! Thanks, Scott
On 5/27/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> > For now, if you'd like to help out or help me commit the code in the
> > first place, I've uploaded a tarball of the code I'm working with
> > here: http://baxter.cernio.com/sycamore_base.tar.gz
>
> This code is n
ine vs # of spaces on current line).
>
> Rottenchester wrote:
> > You guys might also be interested in pylint, which supposedly can
> > enforce coding standards:
>
> Thanks, I'll check it out. I wouldn't trust a tool to do the tab
> conversion. I did have to make some deci
You guys might also be interested in pylint, which supposedly can
enforce coding standards:
http://www.logilab.org/857
On 5/24/07, Adam Dewitz <[EMAIL PROTECTED]> wrote:
> I'll help. We need to come up with a plan so we don't overlap.
>
>
> On May 24, 2007, at 9:52 AM, [EMAIL PROTECTED] wrote:
>
Did you use a tool to do that? If not, maybe there's a "pretty
print" tool we can use to automate the changes.
On 5/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > awesome!
>
> In case you're curious, I checked in some whitespace changes[1].
>
> There might be some bugs from that but it
> So, my opinion is that we have the sycamore wiki for design
> docs/discussion (mainly because it's familiar and I don't want to taint my
> wiki knowledge by using multiple wikis), the trac wiki just point to the
> sycamore wiki (as it does now), and have users report bugs directly into
> the trac
Here's something else to think about.
We're going to be doing a v2 of the data model quite soon. There are
a lot of fields in the database that reflect cruft that's no longer
used, or was ill-considered in the first place. The more of this
type of cruft we can remove, the better. If we get ri
n May 21, 2007, at 7:41 AM, Rottenchester wrote:
>
> I had some debug code in there that I forgot to remove last night. It
> works now after I reverted back to the latest svn.
>
> Sorry about that. I shouldn't be using that as my personal sandbox.
>
> ___
Good idea. I did it. I'll take both tickets because I'll be into the
Xapian stuff with 57.
On 5/21/07, Adam Dewitz <[EMAIL PROTECTED]> wrote:
> Perhaps we should break Ticket #55 up into 2 separate tickets:
>
>
> Ticket #55 Search Fails for Partial Word with type: enhancement
>
> Philip
.org for general project information
> and documentation.
>
> Thoughts?
>
> AD
>
>
>
>
> On May 21, 2007, at 1:36 PM, Rottenchester wrote:
>
> This sounds good - I'm still learning about trac. Is there a way to
> integrate the discussion with the ticket
> Yup, all pretty standard stuff. I've revised you process a bit. Let me
> know what you think...
>
> 1. Identify a problem or feature
> 2. Add/modify the bug/feature report in trac
> 3. Propose a solution
> 4. Discussion, documentation, add/modify expected milestone
> 5. Jump to 1 until a refined
The nice thing about trac is that the roadmaps and timelines are
automatic, as long as all contributors and bug reporters are
consistent in submitting tickets. Does anyone think the following
process is "overzealous"?
1. Developers and users come to broad agreement on the goals of the
next few m
I pasted in a long discussion that Phil and I had a few months ago
into the "Talk" on the Database Design page.
Also, I'm 100% behind the coding standards doc and will start using
them for all new code I write.
On 5/21/07, Adam Dewitz <[EMAIL PROTECTED]> wrote:
> This was primarily the work of RC
I had some debug code in there that I forgot to remove last night. It
works now after I reverted back to the latest svn.
Sorry about that. I shouldn't be using that as my personal sandbox.
On 5/20/07, Adam Dewitz <[EMAIL PROTECTED]> wrote:
> RC, You set Ticket 36 to fixed, but I still get a Tra
s to happen. I'm not sure if that's an issue in this case, but I
> just thought I'd throw it out there. See:
> http://daviswiki.org/index.scgi/Front_20Page :)
>
> --Philip
>
> On 5/18/07, Rottenchester <[EMAIL PROTECTED]> wrote:
> > Scott, thanks for the r
There are a couple of bugs we're working in sapling that are claimed
to be fixed in the wikis branch. But, as I mentioned this morning,
none of the wikis code has been checked in. It seems like a waste
for us to go out and re-fix those bugs, and it is also a lost
opportunity to start to merge wi
These are used only by themes so putting them in one place for use by
all themes makes sense to me.
On 5/18/07, Adam Dewitz <[EMAIL PROTECTED]> wrote:
> Currently the isEdit and isInfo functions live in the theme file (E.g
> eggheadbeta). Does it make more sense to move these to a more generic
> l
Scott, thanks for the reference. It looks like that encoding is the
intent of quoteFIlenames and the fix I checked in this a.m. should
handle edge cases that were causing an error in some testing we were
doing.
The remaining issue in UTF-8 handling is another error in search.py
that apparently P
My $.02: all themable stuff (e.g., HTML) should be in themes.
On 5/18/07, Adam Dewitz <[EMAIL PROTECTED]> wrote:
> Is there a reason part of the search form HTML resides in wikiutil?
> Wouldn't it make more sense to have this in the theme file within the
> searchform function?
>
>
>
> From wikiu
There are a couple of bugs in trac related to UTF-8. It looks like
all file names and URLs are run through the pretty restrictive
quoteFilename in wikiutil.py. This recodes all characters that aren't
in (A-Z,a-z,1-9). In a UTF-8 environment, it doesn't work on UTF-8
URLs.
AFAIK, all browsers a
You could try latin1 encoding instead of utf-8 in your
sycamore_config.py. latin1 passes through some characters that fail
utf-8 decoding.
On 5/15/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> So I'm trying to install sapling on Dreamhost. I've gone through the
> motions of building my own p
I don't know if this is of general interest, but here goes:
Xapian is supported on ubuntu as of Feisty (7.04). On Dapper (6.10)
and Edgy (6.06), I've had excellent luck with the packages from
xapian.org. A good explanation of how to add the Xapian repository is
available here:
http://xapian.org
independentshall.org), but he got stuck
> > by Xapian/ Memcache at the buildDB step, and abandoned ship for a wiki
> > software he had used before.
> >
> > IMHO, we should make those default to OFF, or catch the thrown error
> > and hand out a clear error message.
> >
&g
the version required (1.2.1_p2). If you're
> > using Ubuntu 6.06, the package in the repo is too old. The package in
> > Ubuntu 6.1 is the required release.
> >
> > AD
> >
> >
> > On May 9, 2007, at 9:39 PM, Rottenchester wrote:
> >
>
It's crapping out on a connection to the db. You might want to see if
you can connect to the mysql db using the userid and password you've
put in sycamore_config.py.
mysql -u -p
password:
What version of ubuntu are you using?
On 5/9/07, Far McKon <[EMAIL PROTECTED]> wrote:
> I removed "pyth
31 matches
Mail list logo