Volume management fixes #45
No reviewers
Labels
No Label
Bug
Contributions welcome
Did not do
Duplicate
Feature
Module
Backups
Module
GraphQL
Priority
High
Priority
Low
Priority
Medium
Refactor
Severity
High
Severity
Low
Severity
Medium
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: SelfPrivacy/selfprivacy-rest-api#45
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "fix/do-volumes"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
This PR fixes issues related to volume handling on DigitalOcean. This include:
sda1
was wrong, as on DO it isvda1
sda1
. Instead, they now imply that they are on the system disk. This fixes crashes on user side.iso9660
filesystem are now ignored: generally it is a file system used on optical disks, and it is used on DigitalOcean asvdb
drive with JSON containing server metadata.Mailserver
now looks for its location on theemail
field ofuserdata.json
as Nix config looks foremail
and it is too late to change it tomailserver
on Nix side.check=False
for subproccess callsNo API changes, version bumped from 2.2.0 to 2.2.1
@ -114,3 +112,3 @@
return user_data.get("mailserver", {}).get("location", "sda1")
return user_data.get("email", {}).get("location", "sda1")
else:
return "sda1"
mail service still returns sda1 by default?
Just like other movable services do. So it might be a good idea to use the system drive as a fallback for all services.
LGTM