2025-03-13 - 2025-03-20
Overview
9 pull requests merged by 3 users
Merged
#257 remove option fediversity.eu
Merged
#258 revert change on USER_SETTINGS_FILE, fixing dev shell
Merged
#253 trigger nixops from panel
Merged
#254 fix: NixOS deployment code
Merged
#252 fix: run manage in service directory
Merged
#251 update fedi201 host public key
Merged
#249 remove paragraph: Configuration schema version, following #247
Merged
#247 remove versions
Merged
#236 add basic service configuration
2 pull requests proposed by 2 users
Proposed
#259 Progress Indicator
Proposed
#260 enable and document using manage.py in online environment
6 issues closed from 2 users
Closed
#101 Deploy Fediversity Panel
Closed
#250 expose initialUser choices to the user
Closed
#238 simplify python dependency management
Closed
#233 Forgejo doesn't send notifcations
Closed
#107 Users can configure their desired domains in the online panel, so that the deployed services are assigned the desired domains
Closed
#106 Online panel lets the user select services to deploy
4 issues created by 1 user
Opened
#248 upstream django-pydantic-field overlay
Opened
#250 expose initialUser choices to the user
Opened
#255 installable app
Opened
#256 show expected costs in the form
28 unresolved conversations
Open
#190
Wire up passing credentials from FediPanel to the Pixelfed configuration
Open
#75
Receive a notification when deployment finishes
Open
#74
View a deployment progress indicator
Open
#76
Deployed services are accessible under the configured domain
Open
#145
separate panel into django back vs front
Open
#244
account workspaces
Open
#24
Disable root SSH authentication altogether
Open
#177
continuous deployment
Open
#242
enqueue deployment syncs
Open
#69
Split test environment into staging and production
Open
#100
'one-click' portability between hosting providers
Open
#228
OKR: production
Open
#241
allow multiple deployments per operator
Open
#104
Have a DNS service running to allow users to tie services to their own domain
Open
#108
Selected services can be deployed
Open
#110
The deployment process informs the DNS service of the IP of provisioned VMs, so that the right subdomain can be assigned to it
Open
#111
Shared storage is provisioned to ensure persistence of data
Open
#115
Databases are provisioned so that services can use a central storage
Open
#142
Users can configure their desired sub-domains in the online panel, so that the deployed services are assigned the desired sub-domains
Open
#118
Relevant email accounts are provisioned such that the operator may be contacted
Open
#109
Have a way to make requests to the DNS service so that subdomains can be pointed to the right IP
Open
#116
Proxmox resources are provisioned to deploy services to
Open
#26
Set up a secret management scheme
Open
#182
use shared storage from VMs
Open
#185
use immutable buckets from VMs
Open
#187
provision immutable buckets
Open
#117
SMTP service is provisioned so that applications can send emails
Open
#73
Configure a DNS domain and select services to deploy