george-e-shaw-iv
commented
6 years ago In PR #108 it says the following still needs addressed on this issue:
- Listing all of them on the server side and allowing them to be deleted from there
- Nameserver configuration from the server side
- Displaying nameservers to the clients on their account panels
And after those things are done the following also needs to be done:
- Upon bundle deletion all references of it within the domain datastore need to be deleted.
- Server nameserver information as well as domain registration instructions should be put inside of the bundle creation email.
Severity level (1-10):
10
Files/Directories Involved:
account/(and other various API endpoints in the backend)Description:
The account panel needs to have a place to register which domains are pointed at the server's name-server(s). The name-servers will also be listed here for convenient access to the owner of the account.
With that being said, there also needs to be a way to configure nameservers/automatically detect them from the server... I'm honestly not too sure how that works.
Once an account owner registers a domain in their account, that will be stored in a database that links that domain to the bundle. Any requests coming in from port 80 of the server (which will be linked to the nameservers in some way shape or form... also not too sure how this works) will take a look at the 'Host' header field, look for that specific host in the database, and if that domain exists in the database, route the request to that bundle.
Personal Comments:
This is going to be hard.