Transition to using CAMFISH #32

Open
opened 2025-03-27 08:57:40 -06:00 by sashakoshka · 0 comments
Owner

CAMFISH was based on STEP's internal architecture, and has since received new features, style/consistency updates, and reliability improvements that should be backported here. This will also allow new actors developed for use in CAMFISH daemons will be usable in STEP.

The step.meta file should be replaced by the CAMFISH configuration file, but the feature of each site's root dir coming with some configuration specific to it is very useful, so perhaps CAMFISH could be told to parse that as well and merge it on top of /etc/stepd/stepd.conf. The file formats are identical I think.

Providers also need to become actors and fulfill the actor interfaces.

[CAMFISH](https://git.tebibyte.media/sashakoshka/camfish) was based on STEP's internal architecture, and has since received new features, style/consistency updates, and reliability improvements that should be backported here. This will also allow new actors developed for use in CAMFISH daemons will be usable in STEP. The step.meta file should be replaced by the CAMFISH configuration file, but the feature of each site's root dir coming with some configuration specific to it is very useful, so perhaps CAMFISH could be told to parse that as well and merge it on top of /etc/stepd/stepd.conf. The file formats are identical I think. Providers also need to become actors and fulfill the actor interfaces.
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sashakoshka/step#32
No description provided.