issue_comments

Meant to add that of course it would be better not to reinvent CSS (one time was already enough). But one option would be to provide a mechanism to specify a CSS class for a column (a cell, a row...) and let the user give a URL path to a CSS file on the command line.

I initially went looking for a way to hide a column completely. Today I found the setting to truncate cells, but it applies to all cells. In my case I have text columns that can have many thousands of characters. I was wondering whether the metadata JSON would be an appropriate place to indicate how columns are displayed (on a col-by-col basis). E.g., I'd like to be able to specify that only 20 chars of a given column be shown, and the font be monospace. But maybe I can do that in some other way - I barely know anything about datasette yet, sorry!

@simonw What about allowing a base url. The <base>....</base> tag has been around forever. Then just use all relative URLs, which I guess is likely what you already do. See https://www.w3schools.com/TAGs/tag_base.asp

FWIW I did a dumb merge of the branch here: https://github.com/jsfenfen/datasette and it seemed to work in that I could run stuff at a subdirectory, but ended up abandoning it in favor of just posting a subdomain because getting the nginx configs right was making me crazy. I still would prefer posting at a subdirectory but the subdomain seems simpler at the moment.

Hmmm, wait, maybe my mindless (copy/paste) use of proxy_redirect is causing me grief...

Agreed, this would be nice to have. I'm currently working around it in nginx with additional location blocks:

```

location /datasette/ {
    proxy_pass         http://127.0.0.1:8001/;
    proxy_redirect     off;
    include proxy_params;
}

location /dna-protein-genome/ {
    proxy_pass         http://127.0.0.1:8001/dna-protein-genome/;
    proxy_redirect     off;
    include proxy_params;
}

location /rna-protein-genome/ {
    proxy_pass         http://127.0.0.1:8001/rna-protein-genome/;
    proxy_redirect     off;
    include proxy_params;
}

```

The 2nd and 3rd above are my databases. This works, but I have a small problem with URLs like /rna-protein-genome?params.... that I could fix with some more nginx munging. I seem to do this sort of thing once every 5 years and then have to look it all up again.

Thanks!