|
|
|
@ -139,3 +139,36 @@ Can be run locally or as a SaaS
|
|
|
|
save on costs relative to pure SaaS solutions but do not have the
|
|
|
|
save on costs relative to pure SaaS solutions but do not have the
|
|
|
|
technical knowledge, time, or appetite for risk that would lead them
|
|
|
|
technical knowledge, time, or appetite for risk that would lead them
|
|
|
|
to run their own self-hosted infrastructure.
|
|
|
|
to run their own self-hosted infrastructure.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
** Potential Apps
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- NextCloud
|
|
|
|
|
|
|
|
- Matrix
|
|
|
|
|
|
|
|
- Bitwarden
|
|
|
|
|
|
|
|
- Immich
|
|
|
|
|
|
|
|
- Jellyfin
|
|
|
|
|
|
|
|
- Gitea
|
|
|
|
|
|
|
|
- GitLab
|
|
|
|
|
|
|
|
- Cal.com
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
** Current status
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A rough prototype of a docker compose based app running on flatcar
|
|
|
|
|
|
|
|
linux.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
** Unresolved Areas
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In general, these have all been thought about and seem to be solveable
|
|
|
|
|
|
|
|
but still need more specific technical solutions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- backups
|
|
|
|
|
|
|
|
- logging
|
|
|
|
|
|
|
|
- monitoring / alerting
|
|
|
|
|
|
|
|
- exporting
|
|
|
|
|
|
|
|
- migrating between platform providers (VPS providers, etc)
|
|
|
|
|
|
|
|
- updating
|
|
|
|
|
|
|
|
- CI system
|
|
|
|
|
|
|
|
- docs/auto-setup for app features
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
like helping users configure their phone to connect to NextCloud's
|
|
|
|
|
|
|
|
calendar for example
|
