Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | more changes to org file |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
87058bb2ccd0ec80d1d09f123aec8fe3 |
| User & Date: | sehqlr 2017-12-05 17:19:00.702 |
Context
|
2017-12-17
| ||
| 21:56 | Delete Idris source, add Literate Programming document check-in: 06ec941e60 user: sehqlr tags: trunk | |
|
2017-12-05
| ||
| 17:19 | more changes to org file check-in: 87058bb2cc user: sehqlr tags: trunk | |
|
2017-11-14
| ||
| 23:09 | Wrote out more of the decription of the app check-in: 4288c65de8 user: sehqlr tags: trunk | |
Changes
Changes to Project.org.
| ︙ | ︙ | |||
38 39 40 41 42 43 44 | I plan on using Python as the language of the prototype, since I've worked with Python the longest. However, I also want to implement this in Haskell, since I love Haskell. * Functional Description This is the beginnings of a specification that will be implemented as a runnable specification later. ** Interface | | | > > > > > > > > > > > > > > > > > > > | | | 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 |
I plan on using Python as the language of the prototype, since I've worked
with Python the longest. However, I also want to implement this in Haskell,
since I love Haskell.
* Functional Description
This is the beginnings of a specification that will be implemented as a runnable specification later.
** Interface
The main interface will be a RESTful web service defined with an
OpenAPI Specification document. It will behave like a standard web server
serving up static files.
#+NAME: base sketch
#+BEGIN_SRC yaml :exports none :tangle swagger.yaml :noweb yes
openapi: 3.0.0
info:
title: Static
description: >-
a semi-dynamic database-as-documents web content management system
version: 0.0.1
paths:
/documents:
get:
summary: Returns paths for all documents currently in the database
description: >-
This returns an
#+END_SRC
I will leverage code generation tools to create the clients. According to the
swagger code-gen docs, you can generate a Bash client, so that could cover a
basic CLI as well.
If front end or other graphical interfaces would benefit from a secondary
protocol, we can add that later. The prototypes and alpha/beta versions will
target the RESTful API only.
** Components
These are the main components of static, starting from the HTTP service to
|
| ︙ | ︙ |