Because we need to be able to store templates server-side, and it also relates to #104 .
This needs to be sufficiently generic to support templates, pictures and archived config files. Preferably support everything, whatever that means.
This will need some thinking over... There are many concerns:
Access is an issue, but not a hard one.
History. We want to be able to overwrite a template, obviously, but we should keep track of it. (Can we just piggy-back on git here, perhaps?)
Partial uploads? File sizes?
How do we expose this server-side? Today, templating just reads a file on disk, which is really nice, but that doesn't integrate well with more complex methods.
Access methods: What does config archiving actually support? Might not be a huge issue...
"But WHYYYY Kristian!?"
Because we need to be able to store templates server-side, and it also relates to #104 .
This needs to be sufficiently generic to support templates, pictures and archived config files. Preferably support everything, whatever that means.
This will need some thinking over... There are many concerns: