Currently zealot (or at least the packaged zealot versions) sets up its own user for running the service and transcoding files.
Ideally the user should be able to set a parameter in their config file to run the service under, to better integrate with separate environments.
Currently zealot (or at least the packaged zealot versions) sets up its own user for running the service and transcoding files.
Ideally the user should be able to set a parameter in their config file to run the service under, to better integrate with separate environments.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently zealot (or at least the packaged zealot versions) sets up its own user for running the service and transcoding files.
Ideally the user should be able to set a parameter in their config file to run the service under, to better integrate with separate environments.