.cyb-centrism #21

Closed
opened 2017-07-22 00:07:27 +02:00 by albino · 4 comments
Owner

Verax mentioned that there might be interest in using the project for TLDs other than .cyb. This means that in future, it might be nice to expand the application to be configurable to serve any TLD.

Here's what I can think of right now that would need to be fixed:

  • Configuration parameter for which TLD is being served; currently .cyb is hard-coded
  • More flexible templates which could be used in a more 'contemporary' design
  • A few different stylesheets to choose from; at the very least, one which is not cyberpunky

Obviously, the project should aim to serve .cyb before it addresses the needs of other potential TLDs, but I think we should aim to make cyberman as independent as possible of any particular TLD during future development.

Verax mentioned that there might be interest in using the project for TLDs other than .cyb. This means that in future, it might be nice to expand the application to be configurable to serve any TLD. Here's what I can think of right now that would need to be fixed: * Configuration parameter for which TLD is being served; currently .cyb is hard-coded * More flexible templates which could be used in a more 'contemporary' design * A few different stylesheets to choose from; at the very least, one which is not cyberpunky Obviously, the project should aim to serve .cyb before it addresses the needs of other potential TLDs, but I think we should aim to make cyberman as independent as possible of any particular TLD during future development.
albino added the
meta
label 2017-07-22 00:07:27 +02:00
Collaborator

It may also have value to support having one instance of cyberman able to do registrations for multiple TLDs at once. Obviously not a priority, but it might be good to avoid hard-coding assumptions that there is only 1 TLD

It may also have value to support having one instance of cyberman able to do registrations for multiple TLDs at once. Obviously not a priority, but it might be good to avoid hard-coding assumptions that there is only 1 TLD
Author
Owner

Yeah, that sounds like a good 'stretch goal'. If not that, at least support running multiple instances of cyberman (they are fairly light, approx 50M memory footprint) communicating with one instance of NSD.

Yeah, that sounds like a good 'stretch goal'. If not that, at least support running multiple instances of cyberman (they are fairly light, approx 50M memory footprint) communicating with one instance of NSD.
Author
Owner

Progress made with e91816381d - you can now use cyberman to serve any TLD, so only the interface needs to be changed.

Progress made with https://git.fuwafuwa.moe/.cyb/cyberman/commit/e91816381d2198ff82bd45356022ba6150fe3620 - you can now use cyberman to serve any TLD, so only the interface needs to be changed.
Author
Owner

this is as solved as it is ever going to be

this is as solved as it is ever going to be
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: .cyb/cyberman#21
No description provided.