Basic admin UI #10

Open
opened 2025-04-22 21:03:13 +00:00 by amy · 2 comments
Owner

Configure basic settings

Configure basic settings
amy added the
enhancement
label 2025-04-22 21:03:18 +00:00
amy added a new dependency 2025-04-22 21:03:53 +00:00
Author
Owner

We should write back to the config file so that all configuration is persisted in a portable fashion.

Sorts of things to include:

  • Admin credential
  • URLs
  • Logging config
  • Storage paths
  • Database config
We should write back to the config file so that all configuration is persisted in a portable fashion. Sorts of things to include: - Admin credential - URLs - Logging config - Storage paths - Database config
amy added a new dependency 2025-04-22 21:06:08 +00:00
amy added a new dependency 2025-04-23 18:15:36 +00:00
amy started working 2025-04-28 00:49:51 +00:00
amy stopped working 2025-04-28 00:49:53 +00:00
2 seconds
amy deleted spent time 2025-04-28 00:49:57 +00:00
- 2 seconds
amy added a new dependency 2025-04-28 00:50:12 +00:00
Author
Owner

Start by having a basic "enter the password" prompt which is configured through the config file, and prove out writing to the config file

State would need to be mutex wrapped.

  • Have a helper method which locks and then clones the state for use in each route since it's unlikely to race.
  • Have the user manually reload so that they can track when changes are actually applied.
  • Just abort the server so that e.g systemd reload its for us.

https://api.rocket.rs/v0.5/rocket/struct.Shutdown

Start by having a basic "enter the password" prompt which is configured through the config file, and prove out writing to the config file State would need to be mutex wrapped. - Have a helper method which locks and then clones the state for use in each route since it's unlikely to race. - Have the user manually reload so that they can track when changes are actually applied. - Just abort the server so that e.g systemd reload its for us. https://api.rocket.rs/v0.5/rocket/struct.Shutdown
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference: amy/ferri#10
No description provided.