On Tue, Jun 22, 2010 at 12:30:37PM -0400, Chris Ball wrote: > That URL's difficult, since it's under the wiki's namespace, but I've > gone ahead and set up a --serve on http://bugs.bugseverywhere.org/ and > pushed an update to the tutorial doc.
Hmm, the tutorial also mentions pushing over http:
If your bug isn't listed, please open a new bug::
$ be --repo http://bugs.bugseverywhere.org/ new 'bug'
Created bug with ID bea/abc
$ be --repo http://bugs.bugseverywhere.org/ comment bea/def
<editor spawned for comments>
But `be serve` recommends you *not* enable remote writing without
authentication:
be $ ./be serve --help
...
If you bind your server to a public interface, take a look at the
``--read-only`` option or the combined ``--ssl --auth FILE``
options so other people can't mess with your repository.
...
And the lack of https in your URL suggests you aren't using SSL.
* Is http://bugs.bugseverywhere.org/ writable?
yes:
* Must we authenticate?
yes:
* How do we handle password distribution?
no:
* Are you prepared for spam?
no:
* Should we comment out that section of the tutorial.
Also, who wants to implement PGP or SSH-key authentication? ;).
--
This email may be signed or encrypted with GPG (http://www.gnupg.org).
The GPG signature (if present) will be attached as 'signature.asc'.
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt
pgpCdzszXhYd7.pgp
Description: PGP signature
_______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
