data formats should be tagged in image names

libresh / applications

Applications we offer

9 stars 5 forks source link

data formats should be tagged in image names #20

Closed michielbdejong closed 10 years ago

michielbdejong commented 10 years ago

discard the current format without tagging it
start a branch for the proper data format, with /data/server-wide/IMG/ and /data/per-user/DOMAIN/IMG/.
from there on, data format versioning is 100% per IMG, meaning we don't really need to tag the server-wide portion (being just this super minimal directory path scheme).
if we ever need to make a breaking change in the data format of an image, then we rename the image, and possibly create a migration script. This means some users may be running 'resite' and some may be running 'resite2', on the same server, without any problem.

michielbdejong commented 10 years ago

what about aliases like 'www.' or even wildcard subdomains? -> we'll symlink them somehow - the goal of using the domain name in the path is to make the mailserver automatically know which email address lives where. The philosophy is that every user always has one "main" domain as their defining identity, and we use that as their user id.

There can still be a customer database holding details on more complex billing details and organizations, but the main hosting structure is a domain, with a secondary email address in contact.txt

michielbdejong commented 10 years ago

there should be a default user in case the domain name doesn't match any of the users on the server. but since it works the same as a user container, it can live in /data/per-user/default

michielbdejong commented 10 years ago

made these changes in master; trying them out on k2 now.

michielbdejong commented 10 years ago

got k2-data-start.tar.gz in the new format and it works