Comments (5)
What sort of data are you thinking of?
I am particularly keen to stop galicaster writing state into the config file, as we manage that using puppet and the application user account should not be writing into /etc
from galicaster.
Yeah this is probably a discussion. We would have to be clear what is stored where
I think the mediapackage should stay on disk and pretty much everything else should be put somewhere else
from galicaster.
What was the use case you had in mind @androidwiltron?
I'm wondering what kind of state information currently gets written back to the configuration file (apart from the profile)?
from galicaster.
Yeah so to be clear, keeping the config file would be sensible
I was thinking about data like extra metadata or parameters that we pass contextually to opencast. A good example is user IDs from log ins
The config file should be for static things
For data that changes it should either be in the mediapackage or if it's not part of the mediapackage, it should be elsewhere that is read/write
These are just ideas
from galicaster.
Yea I was pursuing the idea of mediapackage specific workflow-parameters from a plugin but it could still exist in the conf.ini
as default-workflow-parameters
allowing an override elsewhere maybe..
There's the galicaster.xml
per mediapackage that is used for some things like this (now galicaster.json
on the master branch), could that be used?
from galicaster.
Related Issues (20)
- Log warnings about blackmagic profiles HOT 3
- Comprehensive method to decide if an event has changed HOT 3
- UnicodeDecodeError when insert non unicode characters in presenter metadata field HOT 2
- Package build change /usr/bin/galicaster arguments not passed on HOT 2
- Move release candidate packages to a testing repository HOT 1
- Video and audio only profile switching not working
- Series Opencast Call can fire too frequently HOT 5
- Galicaster does not run on Wayland HOT 4
- Don't show previous recording details when idle HOT 1
- GnuTLS Error When Fetching > 5 Opencast (4.x) Events HOT 23
- lowaudio plugin should not trigger an error when recording HOT 1
- Duplicate filenames cause recording failure
- Retry a recording status update if it fails HOT 2
- Use max rather than average of L/R channels for audio plugins HOT 1
- NDI multi stream stuttering HOT 6
- Invert Galicaster audio meter on Ubuntu18 HOT 2
- No Galicaster preview when using backup audio track HOT 1
- Python 3 HOT 3
- Review opencast 14 series endpoint compatibility
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from galicaster.