Conversation
Notices
-
aroque (aroque)'s status on Monday, 13-Apr-2015 17:24:56 CEST aroque How disruptive would it be to change the domain name of a !gnusocial instance? At least in the case of a #private site, I guess it should be possible to update the database and bring the site back to a working state. Is that true? /cc @mmn -
Marcus Maria (marcus)'s status on Monday, 13-Apr-2015 17:32:24 CEST Marcus Maria I have once tried but failed. -
vinzv (vinzv)'s status on Monday, 13-Apr-2015 17:43:59 CEST vinzv @aroque I strongly discourage you to do so. I only heard failure stories from people trying that. -
lnxw48 (Linux Walt) (lnxw48)'s status on Monday, 13-Apr-2015 17:59:31 CEST lnxw48 (Linux Walt) @aroque If the site has already connected to others, you can expect trouble. Better to create completely different site on new domain. -
mmn (mmn)'s status on Monday, 13-Apr-2015 18:09:26 CEST mmn private sites (non-federating) shouldn't be much of a problem, but many URLs are (still) statically stored for whatever reason.
For federating sites - don't. -
aroque (aroque)'s status on Monday, 13-Apr-2015 20:16:22 CEST aroque Thank you all for the feedback. I don't see what could go wrong with a private site. I would modify config.php and replace all refs to the old urls in the database. I guess this should fix also intra-site stuff within a public site. If I am overlooking something serious, please let me know :) Concerning public sites, I understand this will cause problems, but what would be the difference between upgrading the site as above and creating a completely new insta…
-