Greg - Gitea

greg closed pull request kosmos/chef#81

2019-07-19 17:12:11 +00:00

Set the uploads dir inside of /opt/ejabberd instead of /var/www

greg created pull request kosmos/chef#81

2019-07-19 10:50:56 +00:00

Set the uploads dir inside of /opt/ejabberd instead of /var/www

greg pushed to bugfix/80-xmpp_uploads_location at kosmos/chef

2019-07-19 10:50:20 +00:00

0fa9e6cbb7 Set the uploads dir inside of /opt/ejabberd instead of /var/www

greg commented on issue kosmos/chef#80

2019-07-05 23:31:39 +00:00

XMPP HTTP uploads failing again

I found what caused this, it's https://gitea.kosmos.org/kosmos/chef/src/branch/master/site-cookbooks/kosmos-nginx/recipes/default.rb#L63-L68 (introduced in 36a5048).

greg created pull request kosmos/chef#79

2019-07-05 14:04:58 +00:00

Switch to the new ipfs cookbook

greg pushed to feature/new_ipfs_cookbook at kosmos/chef

2019-07-05 14:02:41 +00:00

ab09dd81b4 Update the ipfs cookbook to 0.4.0

666ba1e6f6 Override node attributes for andromeda and barnard

9c8befc179 Move attributes from the ipfs cookbook to kosmos-ipfs

greg pushed to feature/ingress at kosmos/gitea.kosmos.org

2019-07-05 09:13:58 +00:00

67d87d7d5b Use the correct name for the ingress

greg commented on issue kosmos/gitea.kosmos.org#26

2019-07-04 15:45:42 +00:00

WIP: Set up ingress with Let's Encrypt certificates using cert-manager

I pushed docs about Ingress, based on the successful test deployment of Gitea that I've done (https://gitea-test.kosmos.org/).

greg pushed to feature/ingress at kosmos/gitea.kosmos.org

2019-07-04 15:34:37 +00:00

3cdc07cdf3 Add initial Ingress documentation

91dab0f121 Explicitly set the ingress name to gitea-ingress

ed48c92e4f Update cert-manager to 0.8.1

Compare 3 commits »

greg opened issue kosmos/chef#78

2019-07-04 09:39:54 +00:00

Switch to Policyfile, replace knife-solo

greg commented on issue kosmos/chef#5

2019-07-04 09:35:15 +00:00

Prevent the nodejs applications restarting on every Chef run

I can't reproduce the issue in a VM, but I can confirm it still happens on barnard. Subresources of the application resource aren't updating, but still the service restarts. Logs:

greg merged pull request kosmos/chef#77

2019-07-04 08:26:41 +00:00

Switch from IPFS cluster to kredits-ipfs-pinner

greg closed pull request kosmos/chef#77

2019-07-04 08:26:41 +00:00

Switch from IPFS cluster to kredits-ipfs-pinner

greg commented on issue kosmos/chef#77

2019-07-04 08:26:35 +00:00

Switch from IPFS cluster to kredits-ipfs-pinner

LGTM!

greg pushed to feature/ipfs_pinner at kosmos/chef

2019-07-04 08:25:03 +00:00

cf4e567dcb Get rid of the letsencrypt recipe

greg commented on issue kosmos/chef#5

2019-07-04 06:57:28 +00:00

Prevent the nodejs applications restarting on every Chef run

It can be any of the resources inside of the application resource, I'm checking what's causing it

greg created pull request kosmos/chef#70

2019-06-21 15:41:21 +00:00

Switch to our own fork of the poise-javascript cookbook

greg pushed to feature/5-poise-javascript at kosmos/chef

2019-06-21 15:41:05 +00:00

80526e3396 Switch to our own fork of the poise-javascript cookbook

greg commented on issue kosmos/chef#5

2019-06-21 14:15:38 +00:00

Prevent the nodejs applications restarting on every Chef run

I have started from the unreleased master branch of poise-javascript (rake chef:build). That includes a change that supports the new behavior of npm install, writing "up to date" to stdout when no changes have been performed.

greg created pull request kosmos/chef#69

2019-06-20 10:49:06 +00:00

Add email notifications for failed certbot runs