Fix issues with the kosmos-mastodon cookbook #8

Closed
greg wants to merge 6 commits from bugfix/nodejs_update_mastodon_fixes into master
Owner

I found these issues by running the cookbook on a new machine in Vagrant

  • Move the creation of the SystemD service files outside of the application (this prevents a crash on the initial Chef run due to the service files not being there yet before the services gets notified to restart)

Also update the nodejs cookbook and the nodejs installation (current LTS)

I found these issues by running the cookbook on a new machine in Vagrant * Move the creation of the SystemD service files outside of the application (this prevents a crash on the initial Chef run due to the service files not being there yet before the services gets notified to restart) Also update the nodejs cookbook and the nodejs installation (current LTS)
Owner

I just upgraded Mastodon in #13, creating conflicts with this branch. It's using Ruby 2.6.0 now (required by Mastodon 2.7.0).

I just upgraded Mastodon in #13, creating conflicts with this branch. It's using Ruby 2.6.0 now (required by Mastodon 2.7.0).
Owner

The conflicts here are 1 month old. The PR is starting to smell fishy.

The conflicts here are 1 month old. The PR is starting to smell fishy.
Owner

Isn't this long superseded by the already merged Chef 14 PR?

Isn't this long superseded by the already merged Chef 14 PR?
Author
Owner

Yes, I included these changes in #27, closing this one

Yes, I included these changes in #27, closing this one
greg closed this pull request 2019-04-17 07:42:35 +00:00

Pull request closed

Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#8
No description provided.