Problem

As a developer I often have a settings table which is only editable by database tools (e.g. sql or text editor) and often only on the backend server. It would be nice to have a solution to allow easy editing while not being on the backend.

Solution

A small xcopy:able web site or application.
For database data it could have a connection string to the server and for text files it could have a path.

It should be able to figure out some meta data by itself but then, with local settings, override them to a more user friendly format.
For instance, if settings is a CSV table, the local settings could have definitions for separator characters, column headers and column data types.

This suggested solution is not for production but would solve the problem during development and even for production time backend manipulation in the right, careful hands. The same hands that otherwise would write sql queries to do the same task.