fediversity/fediversity
13
2
Fork 6
Code Issues 157 Pull requests 29 Projects 1 Activity Actions

reference front-end is decoupled from version of configuration module #304

New issue
Open
opened 2025-04-08 16:47:01 +02:00 by kiara · 1 comment
kiara commented 2025-04-08 16:47:01 +02:00
Owner
Copy link

As a Fediversity user,
I want a front-end not tightly coupled with the versioning of configuration modules,
so that I may deploy code without having to worry about front-enders' concerns trumping my version preferences.

implementation notes

the deployment module should be separate from the Django code, so that we may explicitly specify what version to invoke deployment for - potentially even including forks (see #100).
to achieve this, a separated repo for the deployment module should specify how code-bases would (given a version) know how to invoke it:

  • document implementation/usage (files paths mentioned following #274)
    • any environment
      • panel/views.py#deploy
      • launch/tf.nix
      • document handling incoming updates for stored configurations (#159)
    • environment-specific
      • prod
        • launch/tf-env.nix
        • document storing state
      • dev
        • launch/default.nix
        • panel/env.nix
  • generated json-schema of valid options (#195)
    • sample ui-schema that may be used in visualization
  • implement version in the panel data schema to support disparities from migration (#100)
    • similarly allowing it to inspect its recommended version (if no longer coupled by mono-repo) to use both as its default value for new deployments
    • in the migration string (#77) add a fetchTree input identifying a Fediversity configuration module source, including pinned version (rev)

implementation notes

  • as it stands, the reference implementation in panel/ may function as documentation of usage.
**As** a Fediversity user, **I want** a front-end not tightly coupled with the versioning of configuration modules, **so that** I may deploy code without having to worry about front-enders' concerns trumping my version preferences. ## implementation notes the deployment module should be separate from the Django code, so that we may explicitly specify what version to invoke deployment for - potentially even including forks (see #100). to achieve this, a separated repo for the deployment module should specify how code-bases would (given a version) know how to invoke it: - [ ] document implementation/usage (files paths mentioned following #274) - any environment - `panel/views.py#deploy` - `launch/tf.nix` - document handling incoming updates for stored configurations (#159) - environment-specific - prod - `launch/tf-env.nix` - document storing state - dev - `launch/default.nix` - `panel/env.nix` - [ ] generated json-schema of valid options (#195) - sample ui-schema that may be used in visualization - [ ] implement version in the [`panel` data schema](https://git.fediversity.eu/Fediversity/meta/pulls/31/files) to support disparities from migration (#100) - [ ] similarly allowing it to inspect its recommended version (if no longer coupled by mono-repo) to use both as its default value for new deployments - [ ] in the migration string (#77) add a [`fetchTree`](https://noogle.dev/f/builtins/fetchTree) `input` identifying a Fediversity configuration module source, including pinned version (`rev`) ### implementation notes - as it stands, the reference implementation in `panel/` may function as documentation of usage.
kiara added this to the Fediversity project 2025-04-14 11:27:14 +02:00
kiara changed title from allow control over version of module deployed to reference front-end decoupled from template version 2025-06-01 16:52:00 +02:00
kiara changed title from reference front-end decoupled from template version to reference front-end decoupled from version of configuration module 2025-06-02 10:22:55 +02:00
kiara changed title from reference front-end decoupled from version of configuration module to reference front-end is decoupled from version of configuration module 2025-06-02 12:52:04 +02:00
kiara commented 2025-06-02 12:55:26 +02:00
Author
Owner
Copy link

removed from deps of #100 as technically this isn't mandatory to implement the principle, just in production where versions may not match

removed from deps of #100 as technically this isn't mandatory to implement the principle, just in production where versions may not match
kiara removed this from the Fediversity project 2025-06-10 19:06:46 +02:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
ci/pixelfed
pixelfed-ci
No results found.
Labels
Clear labels   
0 points

fibonacci complexity: 0 points

  
0.5 points

fibonacci complexity: 0.5 points

  
1 point

fibonacci complexity: 1 point

  
13 points

fibonacci complexity: 13 points

  
2 points

fibonacci complexity: 2 points

  
21 points

fibonacci complexity: 21 points

  
3 points

fibonacci complexity: 3 points

  
34 points

fibonacci complexity: 34 points

  
5 points

fibonacci complexity: 5 points

  
55 points

fibonacci complexity: 55 points

  
8 points

fibonacci complexity: 8 points

  
api service

features that may relate more to a (to be created) API service

  
blocked

   
component: fediversity panel

   
component: nixops4

   
documentation

   
estimation high: >3d

   
estimation low: <2h

   
estimation mid: <8h

   
infinite points

fibonacci complexity: infinite points

  
productisation

features out-scoped with the decoupling of the productisation effort

  
project-management

Project management related tasks

  
question

   
role: application developer

   
role: application operator

   
role: hosting provider

   
role: maintainer

   
security

   
technical debt

   
testing

   
type unclear

   
type: bug

Anything that doesn't work as advertised

  
type: deliverable

   
type: key result

   
type: objective

   
type: task

   
type: user story

   
user experience
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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.

Blocks
#206 user control over update timing
fediversity/fediversity
#228 [D2.3] brought into production [2027-11-01]
fediversity/fediversity
#612 Switch hosting provider
fediversity/fediversity
Depends on
#275 Generate Django forms from deployment options
fediversity/fediversity
Reference: fediversity/fediversity#304
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?