Reorder problems
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone/push Build is passing
Details
parent
9474ebbd99
commit
9cae4abd06
|
@ -1,8 +1,20 @@
|
||||||
# Reproted problems
|
# Reproted problems
|
||||||
|
|
||||||
|
## DKIM
|
||||||
|
Is not deployed to Cloudflare. Inex working on it right now.
|
||||||
|
|
||||||
## NixOS fails to upgrade
|
## NixOS fails to upgrade
|
||||||
We have to deploy our own channel with verified builds.
|
We have to deploy our own channel with verified builds.
|
||||||
|
|
||||||
|
## RSA keys generated in app not working
|
||||||
|
Will get rid of key generation inside an app.
|
||||||
|
|
||||||
|
## Volumes are not used properly
|
||||||
|
We need a controller which will detect them, format them, expand them and also move apps between them. Probably app should use Hetzner API to expand volume automatically.
|
||||||
|
|
||||||
|
## Server control is lost when losing app's storage
|
||||||
|
Solution implemented on API side as recovery tokens in [[changelog#authorization_tokens branch|1.2.0]]. We need to implement this on app side.
|
||||||
|
|
||||||
## Master user password
|
## Master user password
|
||||||
Can't use anything but [a-zA-Z0-9]. Problem is in the way we pass variables to nixos-infect script from the app side. String escaping is needed, but it turned out to be not trivial. Use base64 in transit instead? Would have to keep compatability with the old app versions.
|
Can't use anything but [a-zA-Z0-9]. Problem is in the way we pass variables to nixos-infect script from the app side. String escaping is needed, but it turned out to be not trivial. Use base64 in transit instead? Would have to keep compatability with the old app versions.
|
||||||
|
|
||||||
|
@ -20,20 +32,9 @@ Leads to files corruption?
|
||||||
### User is not notified that they may have to add a credit card to b2
|
### User is not notified that they may have to add a credit card to b2
|
||||||
Free limits are pretty small and restoration may easily spend them all, and after that, everything is broken.
|
Free limits are pretty small and restoration may easily spend them all, and after that, everything is broken.
|
||||||
|
|
||||||
## DKIM
|
|
||||||
Is not deployed to Cloudflare. Inex working on it right now.
|
|
||||||
|
|
||||||
## RSA keys generated in app not working
|
|
||||||
Will get rid of key generation inside an app.
|
|
||||||
|
|
||||||
## Volumes are not used properly
|
|
||||||
We need a controller which will detect them, format them, expand them and also move apps between them. Probably app should use Hetzner API to expand volume automatically.
|
|
||||||
|
|
||||||
## Disk storage is not monitored
|
## Disk storage is not monitored
|
||||||
Which leads to big problems for the server. API has to control available space, and how each app uses it. App should alert user and give options on storage management.
|
Which leads to big problems for the server. API has to control available space, and how each app uses it. App should alert user and give options on storage management.
|
||||||
|
|
||||||
## Server control is lost when losing app's storage
|
|
||||||
Solution implemented on API side as recovery tokens in [[changelog#authorization_tokens branch|1.2.0]]. We need to implement this on app side.
|
|
||||||
|
|
||||||
# Backlog
|
# Backlog
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue