Disroot/CHANGELOG
Disroot
/
CHANGELOG
13
8
Fork 2
Code Issues 11 Pull Requests Projects Releases Activity

Update prosody #6

New Issue
Closed
opened 2021-02-19 20:14:11 +01:00 by muppeth · 3 comments
muppeth commented 2021-02-19 20:14:11 +01:00
Owner
Copy Link

We wanted to roll out new automation setup based on rewrite of ansible role.

We wanted to roll out new automation setup based on rewrite of ansible role.
muppeth added this to the 19.02.2021 - #14 milestone 2021-02-19 20:17:07 +01:00
muppeth modified the milestone from 19.02.2021 - #14 to 23.02.2021 - #15 2021-02-20 09:11:14 +01:00
meaz commented 2021-02-20 18:37:12 +01:00
Owner
Copy Link
  • The role has been updated
  • The host_vars have been updated
  • Bot host_vars have been fixed
  • Meaz has deployed Role on vagrant with default and it worked
  • Another person has deployed Role on vagrant with default and worked
  • Meaz 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
  • Someone has deployed Role on vagrant with bot host_vars and it worked
- [x] The role has been updated - [x] The host_vars have been updated - [x] Bot host_vars have been fixed - [x] Meaz has deployed Role on vagrant with default and it worked - [ ] Another person has deployed Role on vagrant with default and worked - [x] Meaz 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 - [ ] Someone has deployed Role on vagrant with bot host_vars and it worked
meaz commented 2021-02-20 18:40:19 +01:00
Owner
Copy Link

I have one major error when deploying with prosody host_vars:

Feb 20 17:33:23 sql     error   Error in SQL transaction: Failed to connect to database

but I guess it is normal in vagrant as it doesn't deploy prosodydb.

I have one major error when deploying with prosody host_vars: ``` Feb 20 17:33:23 sql error Error in SQL transaction: Failed to connect to database ``` but I guess it is normal in vagrant as it doesn't deploy prosodydb.
muppeth modified the milestone from 23.02.2021 - #15 to 25.02.2021 - #16 2021-02-25 18:46:02 +01:00
meaz commented 2021-02-26 23:50:26 +01:00
Owner
Copy Link

Done.

Done.
meaz closed this issue 2021-02-26 23:50:26 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
d47
template
d46
d45
update_tos
d44
meaz-patch-1
update_forgejo
deployment41
d40
d39
d38
deployment38
d25
Labels
Clear labels   
Done

This has been done

  
New

New update reported

  
Ready for production

Ready to be deployed

  
Staging phase

Service deployed to staging server being tested

  
WIP

Work in progress by sysadmin

No Label
Done
New
Ready for production
Staging phase
WIP
Milestone
Clear milestone
No items
No Milestone
25.02.2021 - #16
Projects
Clear projects
No project
Assignees
Clear assignees
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#6
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?