Closed n-peugnet closed 2 years ago
So, what has been chosen for now is:
webdav.club1.fr/
drive/club1.fr/
club1.fr/~<user>/
But we are not sure this is the best solution as we are also trying to add https://github.com/club-1/hosting/issues/37.
~
) character is not easy to type and spellclub1.fr/~nicolas/git/
to /home/nicolas/public/git/
(one must know that club1.fr/~nicolas/
maps to /home/nicolas/public/
)git.club1.fr/<user>/
that would map to /home/<user>/git/
and do the same for static content, for instance static.club1.fr/<user>/
would map to /home/<user>/static/
also, by default userdirs are stored on public_html
, maybe we should use something like public_git
to make it clear that these folder are public and must have the correct permissions (read by Others)
I was thinking of something like that:
git.club1.fr /home/<user>/public_git git repos
user.club1.fr /home/<user>/public_html quick web experiment
shared.club1.fr /home/<user>/shared symlinks created with WebDavDrive or manualy
webdav.club1.fr webdav API
mail.club1.fr mail servers
But I'm confused about the idea of mixing or not shared
(symlinks) and public_html
.
That made me think of my dream of an encrypted folder unlocked "by LDAP connection", that is accessible from SSH and WebDav.
/home/<user>/vault encrypted folder
I try to imagine a home space like this:
--|--mail
|--vault
|--public_git
|--public_html
|--shared
After a phone call with @n-peugnet , and what we have learned from CLUB1's workshop, I think we can fix at least :
git.club1.fr /home/<user>/git git repos
public.club1.fr /home/<user>/public quick web experiment
(@n-peugnet , correct me if I'm wrong)
Done
Webdav server
webdav.club1.fr
dav.club1.fr
cloud.club1.fr
Webdav client
drive.club1.fr
files.club1.fr
User dirs
static.club1.fr/~nicolas
files.club1.fr/~nicolas
user.club1.fr/~nicolas
perso.club1.fr/~nicolas
www.club1.fr/~nicolas
Webdav client and User dirs could be merged into one