Râu Cao raucao
  • Joined on 2018-11-24
raucao created pull request kosmos/chef#257 2020-12-08 19:33:04 +00:00
Add hosts entries for ejabberd private IPs
raucao pushed to feature/akkounts_xmpp_host at kosmos/chef 2020-12-08 19:32:19 +00:00
12125bf0b2 Add hosts entries for ejabberd private IPs
raucao opened issue kosmos/chef#256 2020-12-08 19:09:43 +00:00
Problem with custom node attribute
raucao created pull request kosmos/chef#255 2020-12-08 19:04:41 +00:00
Add ejabberd HTTP API permissions for akkounts
raucao pushed to feature/api_permissions at kosmos/chef 2020-12-08 19:01:00 +00:00
239b6aed51 Add API permissions for akkounts VMs
8e0a66184c Use role for akkounts
Compare 2 commits »
raucao created pull request kosmos/akkounts#13 2020-12-08 18:19:41 +00:00
Exchange XMPP contacts when invitee signs up
raucao pushed to feature/automatic_xmpp_roster at kosmos/akkounts 2020-12-08 18:16:33 +00:00
ee72a32c7e Exchange XMPP contacts when invitee signs up
8a0d89ef60 Add webmock gem
54af949c7d Add faraday for HTTP requests
6dac732a7f Move invitation invalidation to service
e8c1a6066a Move user db creation to service
raucao commented on issue kosmos/chef#250 2020-12-08 13:40:35 +00:00
Apply domain blocklist for ejabberd when running Chef

I also stumbled over this config, but only in (lots of) examples, but not in the official docs:

bad_servers:
  server:
    - "gmail.com"
raucao pushed to feature/api_permissions at kosmos/chef 2020-12-08 13:31:54 +00:00
56d9144ad6 Disable ACME
raucao pushed to vagrant/dirsrv at kosmos/chef 2020-12-08 12:25:10 +00:00
26db8597fd Configure Vagrant for dirsrv
raucao commented on pull request kosmos/chef#252 2020-12-08 12:15:47 +00:00
Script creating new VMs

I randomly thought about this again earlier today, and I'm actually not sure why the PR had to include firewall rules and such.

If we don't run the basic cookbook against the host again, then it won't destroy the existing ones for example. So this could actually have been two different PRs, one for the script itself, and one for the firewall config, as they are two different features.

You can still split it up, of course, but maybe now it's not worth it anymore. So just putting this here as input, and perhaps for the next PRs.

raucao created pull request kosmos/chef#254 2020-12-08 12:13:34 +00:00
Update ejabberd doc
raucao pushed to docs/ejabberd at kosmos/chef 2020-12-08 12:13:20 +00:00
02239dd9a8 Update ejabberd doc
raucao commented on pull request kosmos/chef#252 2020-12-07 15:15:42 +00:00
Script creating new VMs

I always set this to 20.04 when creating VMs in virt-manager.

raucao commented on pull request kosmos/chef#252 2020-12-07 15:15:42 +00:00
Script creating new VMs

This doesn't look right to me. It would attempt to download the path as a second file, no? The pathname should come after the -o flag.

raucao commented on pull request kosmos/chef#252 2020-12-07 15:15:42 +00:00
Script creating new VMs

We won't want to edit the script on the host all the time, so why not simply:

raucao commented on pull request kosmos/chef#252 2020-12-07 15:15:42 +00:00
Script creating new VMs

This whole file seems to not have been edited after being generated.

raucao commented on pull request kosmos/chef#252 2020-12-07 15:15:42 +00:00
Script creating new VMs

Same as for the other cookbook, this seems to have been left unedited after being generated.

raucao commented on pull request kosmos/chef#252 2020-12-07 15:15:42 +00:00
Script creating new VMs

Cool. I left a few comments/questions.

raucao commented on pull request kosmos/chef#252 2020-12-07 15:15:42 +00:00
Script creating new VMs

Is this file actually used? We're on 20.04 now so it seems like this is some default template?