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

Update cryptpad to 4.3.0 #14

New Issue
Closed
opened 2021-03-10 22:30:07 +01:00 by meaz · 5 comments
meaz commented 2021-03-10 22:30:07 +01:00
Owner
Copy Link
  • Test updating on vagrant with vanilla
  • Test updating on vagrant with host_vars

- [ ] PR for host_vars created

  • PR for role created
  • PR for role merged
- [x] Test updating on vagrant with vanilla - [ ] Test updating on vagrant with host_vars ~~- [ ] PR for host_vars created~~ - [x] PR for role created - [ ] PR for role merged
antilopa commented 2021-03-11 12:59:20 +01:00
Owner
Copy Link

Cryptpad vagrant fails due to npm errors. Looking into it with no success so far.

Cryptpad vagrant fails due to npm errors. Looking into it with no success so far.
muppeth commented 2021-03-12 16:53:42 +01:00
Owner
Copy Link

Just tested the PR from @meaz seems to be working fine.

Just tested the PR from @meaz seems to be working fine.
muppeth added this to the 16.03.2021 - #17 milestone 2021-03-16 08:42:08 +01:00
muppeth removed this from the 16.03.2021 - #17 milestone 2021-03-16 21:16:31 +01:00
meaz changed title from Update cryptpad to 4.2.1 to Update cryptpad to 4.3.0 2021-03-25 14:03:50 +01:00
meaz changed title from Update cryptpad to 4.3.0 to Update cryptpad to 4.2.1 2021-03-26 15:13:17 +01:00
meaz commented 2021-03-26 16:25:19 +01:00
Author
Owner
Copy Link

I couldn't really test with host_vars, well, it deploys well, but when I open the page, I have an error, probably because of https.

Also, I cleaned up vars that are the same in host_vars and role. So, now, we can just update the cryptpad version in role vars instead of host_vars.

I couldn't really test with host_vars, well, it deploys well, but when I open the page, I have an error, probably because of https. Also, I cleaned up vars that are the same in host_vars and role. So, now, we can just update the cryptpad version in role vars instead of host_vars.
muppeth added this to the 30.03.2021 - #18 milestone 2021-03-27 11:51:23 +01:00
muppeth changed title from Update cryptpad to 4.2.1 to Update cryptpad to 4.3.0 2021-03-29 11:58:52 +02:00
muppeth commented 2021-03-29 12:03:59 +02:00
Owner
Copy Link

I just tested it last night and bumped to 4.3.0 seems like we are ready to push to production.

I just tested it last night and bumped to 4.3.0 seems like we are ready to push to production.
meaz commented 2021-03-30 11:49:21 +02:00
Author
Owner
Copy Link

Do you have an idea how to test this with host_vars on vagrant?

Do you have an idea how to test this with host_vars on vagrant?
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
30.03.2021 - #18
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
3 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#14
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?