-
-
Notifications
You must be signed in to change notification settings - Fork 46
docs: adds instructions for migrating control machines #795
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
adbenitez
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good but I didn't know what a "control machine" is maybe add a note "control machine (the computer from where you run the server deployment script and upgrades)" or something like that
hpk42
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't think a full new doc is required for migrating the client machine. It's basically about having to preserve chatmail.ini and www-customizations.
So I think the content could be condensed e.g. into a last new section in https://chatmail.at/doc/relay/getting_started.html
sidenote: i am wondering about the term "control" machine -- but don't yet have better suggestion.
hpk42
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't think a full new doc is required for migrating the client machine. It's basically about having to preserve chatmail.ini and www-customizations.
So I think the content could be condensed e.g. into a last new section in https://chatmail.at/doc/relay/getting_started.html
sidenote: i am wondering about the term "control" machine -- but don't yet have better suggestion.
i'll look at condensing it.
it's typically a term i've used when i have to orchestrate from a machine to servers. i can adjust it if needed |
|
@hpk42 change requests are complete. let me know if there's further revisions. |
| - `Maddy-Chatmail <https://github.com/sadraiiali/maddy_chatmail>`_: a | ||
| plugin for the `Maddy email server <https://maddy.email/>`_ which | ||
| aims to implement the chatmail relay features and configuration | ||
| options. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that looks a bit unrelated -- what is the background of this removal?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://github.com/omidz4t/madmail is the new location.
hpk42
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the madmail project is the official successor of the maddy-plugin approach, so i suggest to add this, while remopving stale maddy-chatmail reference.
| - `Maddy-Chatmail <https://github.com/sadraiiali/maddy_chatmail>`_: a | ||
| plugin for the `Maddy email server <https://maddy.email/>`_ which | ||
| aims to implement the chatmail relay features and configuration | ||
| options. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://github.com/omidz4t/madmail is the new location.
pr overview:
desktoptolaptopfor their control machinenote to team:
404causing ci to fail on tests, remove it for now.