[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ~-web-paths on wuiet

On Sat, Nov 09, 2013 at 10:55:21AM +0100, Joachim Breitner wrote:
> Am Samstag, den 09.11.2013, 10:48 +0100 schrieb Philipp Kern:
> > Your script looks reasonably easy that it can just be included in the
> > normal tree. Would it be possible that you place a tiny git repository
> > with the script and its javascript dependencies in your home, so that we
> > can continuously pull from it?
> sure, but this does not solve the problem of how I should develop these
> scripts (or my feature branches of /status/ or anything of the like), if
> I cannot _also_ access it in some unofficial location. For that, ~-paths
> worked very well in the past.

I guess it should be an explicit /unofficial/, /test/ or
/test-do-not-link-to-it/-like path instead.

> How do you test feature of, say, /status/ (assuming you don’t just work
> on the real installation).

You have a point here, of course. I personally do develop on the real
installation because if I need to, it's fixups, not real development.

To be fair: Your CGI could be tested by generating a static HTML output.
It's a little bit more tricky with (pg)status, because that has multiple
different pages.

If we go the subdir route because we cannot use machine names anymore, we
should maybe then iterate over homedirs and add and remove ~links automatically
based on the presence of ~user/public_html (with minimal overrides if
somebody's abusing it). I *guess* our www-data is limited enough that it's not
a problem to run all scripts as it.

Or, alternatively, a separate vhost like buildd-test.debian.org?

Kind regards
Philipp Kern

Attachment: signature.asc
Description: Digital signature

Reply to: