Re: Rules.CSV format as alternative to htaccess

Hi Stian,
I like it a lot! Definitely more simple than having to create the htaccess
by hand.
I also think that the media type is a very interesting question, as
sometimes I have done ORs in the rewrite conditions.
Regarding an owner for each rewrite rule, I think it's too much. In most of
the cases a single owner will edit most of the htaccess (except in repos
like /people). And you can see the edits through the commits, right?
I have tried to edit the wiki to fix a typo, but I don't have permission. I
will try with a pull request.

2016-03-01 17:35 GMT+01:00 Ian Dunlop <>:

> Hello,
> That's a great start Stian. I assume that the "" example is
> predicated on the csv file being present in a top level folder called
> "example" in the github repo (which the page does hint at - I'm just trying
> to understand how it all works). Can there be more than one media-type for
> a redirect? The examples only show one for each row.
> Does each redirect rule need an owner - should we add a column for email
> addresses to contact in case of issues?
> Cheers,
> Ian
> On 1 March 2016 at 11:44, Stian Soiland-Reyes <
>> wrote:
>> So here is my suggestion for rules.csv format and mechanism:
>> In short, a CSV file (which you can edit in your favourite spreadsheet
>> editor) could be used to auto generate corresponding .htaccess (of
>> everything is in order) in a w3id folder.
>> I added an optional column for content negotiatation. i think this could
>> cover 90% of existing .htaccess files (although they would not need to
>> "upgrade")
>> Then for transitions we can simply generate there rules.csv
>> files.
>> Ideas? Suggestions? Feel free to edit in the wiki as well!

Received on Tuesday, 1 March 2016 16:55:50 UTC