diff options
author | John Ankarström <john@ankarstrom.se> | 2021-03-02 00:10:45 +0100 |
---|---|---|
committer | John Ankarström <john@ankarstrom.se> | 2021-03-02 00:10:45 +0100 |
commit | 469a4c2424a684524a8323a8a1a3727e1b6a4ed7 (patch) | |
tree | acb61ff26c932e9cf5eac09aff89d5d452a92ac4 /interfaces | |
parent | 7640f27b9e183c6e9a00249c352e3515d3f90c75 (diff) | |
download | comb-469a4c2424a684524a8323a8a1a3727e1b6a4ed7.tar.gz |
Add simple web interface
The structure is preliminary. It might be a better idea to start
Sinatra in a main script, which decides what interface to use.
The question is whether non-Sinatra interfaces should be supported.
Most will likely use Sinatra, but perhaps not all. With that in
mind, how should it be decided which interface to use?
The best idea is probably to have a protocols directory, with one
script per protocol. http.rb would be the HTTP server, using Sinatra,
while ftp.rb or whatever could be run alongside it.
Alternatively, there could be the following structure:
interfaces/
- http/
- http.rb
- web/
- web.rb
- views/
- admin/
- rss/
- ftp/
- ftp.rb
That would probably be the cleanest implementation.
Diffstat (limited to 'interfaces')
0 files changed, 0 insertions, 0 deletions