I need to switch the Seafile domain while the old domain needs to remain functional for links (redirects) and client connections, not Seahub.
I think I know how to achieve this nginx config wise but has anybody experience with this?
@shoeper Can Seafile handle the redirects?
One needs to set the Seahub domain for links and client config?
My current approach would be to have another nginx config for the new domain while the old one redirects its Seahub, Media, SeaDAV and generated links to the new domain, keeping the Seafile sync and webdav working for the clients.
Once we got thIs working the info will make its way into the community manual.
What about it? For now this has nothing to do with DNS records. They are an requirement and have nothing to do with what I am asking since this is mostly about how Seafile/Seahub works with multiple domains for a switch (not multi-tenancy).
I’m using on one my Seafile instance two domains but never had time to check how it works.
But it’s little different I’m just using the old one as primary and second is just toy cause a got good price for *.cloud TLD.
EDIT: What I see. Share links working on both domains. File sync over client seems working to. So if you let old domain as it and setup new one like the old one, then change domain in settings(if you want to show share link, it’s fill domain from settings not the one from you come to seahub). If you want to, I can do some test for you like tell me what I should try.
EDIT 2: I didn’t see in database any absolute links. All what I saw were relative without domain, so all generated links should work with both domains.