diff --git a/devdocs/solutions.txt b/devdocs/solutions.txt index 2d22ceb8..cb49f4e7 100644 --- a/devdocs/solutions.txt +++ b/devdocs/solutions.txt @@ -273,3 +273,26 @@ Bangalore - seems almost undetectably the same as sanfran Singapor - excellent speed no appreciable different Frankfurt - excellent speed as well RESULT: I'd say for AyaNova there is no appreciable different from one data center to the next, the delay just isn't enough to really factor for biz software and it's super efficent in traffic which helps (back pat to me for thinking efficiently in advance) + + +## How to point a subdomain from an external company's domain to one of our hosted ayanova instances and have it work with letsencrypt etc +e.g. ayanova.thecompany.com pointing to thecompany.ayanova.com + +RESEARCH: how to enable a portion of a domain from an outside to point to their droplet, is that on them or on us? + how does discourse do it?? https://meta.discourse.org/t/configure-your-domain-name-for-hosted-discourse/21827 + SO, I would say it works just like we do with the test servers, they would need to edit their domain record to point a subdomain to us so we would tell them to do that, i.e. they would say + aya.fouralarm.ca points to [ipaddressofdroplet] or discourse does it by subdomain, they would say point to fouralarm.hosted-by-discourse.com so I wonder if we can do that too, + Maybe a way to test this out is like this: + make a droplet, make a domain record gztestco.helloayanova.com that points to that droplet + then make a cert on the droplet for the original gztestco.helloayanova.com and in nginx, request the cert so this is like the initial trial period or setup. + Test, confirm gztestco.helloayanova.com is working + then go to ayanova domain and make a CNAME (CNAME is different and is host pointing to host not to ip address) record aya.ayanova.com and point it to gztestco.helloayanova.com + Then change nginx config in droplet and ADD aya.ayanova.com and + then request a new cert with both aya.ayanova.com and gztestco.helloayanova.com and see if it works from both domains. + ** To request a new cert need different command and need to know cert name which is the first domain requested but to confirm use certbot certificates to view the name + then use the command like this pattern: certbot --nginx --cert-name gztestco.helloayanova.com -d gztestco.helloayanova.com,aya.ayanova.com + (we would keep both domains in case they have dns issues with their own domain and need access or fuck up the redirect somehow later on) + THIS works, and this is the pattern for customers where aya.ayanova.com would be their equivalent to their ayanova subdomain + record they make with their domain registrar or whoever. + **TESTED, WORKS!: I do have a concern about the nginx cert autorenewal as expanding the domains didn't automatically edit the nginx config file and add the managed by certbot bit for the aya.ayanova.com domain + \ No newline at end of file diff --git a/devdocs/todo.txt b/devdocs/todo.txt index c691a5af..64ee03a0 100644 --- a/devdocs/todo.txt +++ b/devdocs/todo.txt @@ -7,14 +7,7 @@ https://linuxhandbook.com/set-up-discourse-digital-ocean/ has an example of disc TEST: cheapest storage for attachments possible, test out creating a new droplet with block storage to hold the attachment files to see if it's possible, how it's done and mapped etc -RESEARCH: how to enable a portion of a domain from an outside to point to their droplet, is that on them or on us? - how does discourse do it?? https://meta.discourse.org/t/configure-your-domain-name-for-hosted-discourse/21827 - SO, I would say it works just like we do with the test servers, they would need to edit their domain record to point a subdomain to us so we would tell them to do that, i.e. they would say - aya.fouralarm.ca points to [ipaddressofdroplet] or discourse does it by subdomain, they would say point to fouralarm.hosted-by-discourse.com so I wonder if we can do that too, - Maybe a way to test this out is like this: - make a droplet, make a domain record testhosted.helloayanova.com that points to that droplet then go to ayanova domain and make a record tsub.ayanova.com and point it to testhosted.helloayanova.com - then make a cert on the droplet and in nginx configured for subdomain testhosted.ayanova.com and see if it works, if so then this is the pattern for customers where tsub.ayanova.com would be their ayanova subdomain - record they make with their domain regisrar or whoever. + todo: metrics are fucked up for some reason in fact I'd just like to reliably know how much disk space is in use etc, like the size of the db versus attachments in simple text