Chad Cravens

Ok I figure I can pass the Inversify container to my custom ServiceFactory. What I've noticed is that for the following handler: ```javascript public create(serviceClass: any, context: ServiceContext) { console.log('>>>...

For others reading this I had to use the image name: ``` ubuntu:19.10 ```

For any others reading this, this is how I hacked my way around this issue: ```port.targetPort = (8000 as unknown) as object;```

Actually this might be due to the connection to the database being poor. Might not be an ascoltatori issue at all... Just wanted to verify everyone's thoughts before closing it.

Apologies, after removing the "db:12" attribute from the backend object, there is no stacktrace. It seems to just hang. I have a console statement on "ready" status: ``` server.on('ready', function()...

Installation of `fapolicy` a few weeks ago created this directory structure: ``` [root@ip-192-168-0-10 ~]# ls /etc/fapolicyd/ fapolicyd.conf fapolicyd.rules fapolicyd.trust trust.d ``` New directory structure is this: ``` [root@ip-192-168-0-10 ~]# ls...

Please refer to: https://github.com/linux-application-whitelisting/fapolicyd#rule-ordering And: https://github.com/linux-application-whitelisting/fapolicyd/blob/main/rules.d/README-rules

Hello @uk-bolly! Thanks for looking into this. It looks like an issue due to a newer release on CentOS8 Stream. These are my configurations: OS: ``` [root@ip-192-168-0-10 ~]# cat /etc/redhat-release...

@uk-bolly working a fix in this PR: https://github.com/ansible-lockdown/RHEL8-STIG/pull/95 Happy to collaborate and code reviews to make sure the fix is good with the Mindpoint team and follows the standards put...

@uk-bolly I'd be happy to support a CentOS 8 Stream release branch if we'd like to see how difficult it would be to maintain and support such a branch (or...