Run new prosody role on bot prosody instance #11

Closed
opened 2021-02-25 21:15:37 +01:00 by muppeth · 1 comment
Owner
  • The role has been updated
  • The host_vars have been updated
  • Main user has deployed Role on vagrant with default and it worked
  • Another person has deployed Role on vagrant with default and worked
  • Main has deployed Role on vagrant with prosody host_vars and it worked
  • Another person has deployed Role on vagrant with prosody host_vars and it worked
- [x] The role has been updated - [ ] The host_vars have been updated - [ ] Main user has deployed Role on vagrant with default and it worked - [ ] Another person has deployed Role on vagrant with default and worked - [ ] Main has deployed Role on vagrant with prosody host_vars and it worked - [ ] Another person has deployed Role on vagrant with prosody host_vars and it worked
Owner
  • The host_vars have been updated
  • Main user has deployed Role on vagrant with default and it worked
  • Main has deployed Role on vagrant with prosody host_vars and it worked
- [x] The host_vars have been updated - [x] Main user has deployed Role on vagrant with default and it worked - [x] Main has deployed Role on vagrant with prosody host_vars and it worked
muppeth added this to the 25.02.2021 - #16 milestone 2021-03-01 13:07:55 +01:00
Sign in to join this conversation.
No Milestone
No project
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: Disroot/CHANGELOG#11
No description provided.