kosmos/chef
kosmos/chef
8
3
Fork 0
Code Issues 30 Pull Requests 3 Projects 2 Activity

Fix issues with the kosmos-mastodon cookbook #8

Closed
greg wants to merge 6 commits from bugfix/nodejs_update_mastodon_fixes into master
pull from: bugfix/nodejs_update_mastodon_fixes
merge into: kosmos:master
Conversation 4 Commits 6 Files Changed 8 +66 -54
greg commented 2019-01-08 16:05:08 +00:00
Owner
Copy Link

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)
raucao commented 2019-01-27 04:52:36 +00:00
Owner
Copy Link

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).
raucao commented 2019-03-14 01:39:50 +00:00
Owner
Copy Link

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.
raucao commented 2019-04-16 08:27:02 +00:00
Owner
Copy Link

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

Isn't this long superseded by the already merged Chef 14 PR?
greg commented 2019-04-17 07:42:34 +00:00
Author
Owner
Copy Link

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

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
service
accounts
Kosmos Accounts
service
discourse
Kosmos Community Forums
service
drone-ci
Kosmos Drone CI
service
email
mail.kosmos.org
service
garage
S3-compatible object storage
service
gitea
Kosmos Gitea
service
ipfs
Kosmos IPFS
service
mastodon
kosmos.social
service
postgres
Database cluster
service
remotestorage
Portable data storage for the Web
service
wiki
Kosmos Wiki
service
xmpp
Kosmos Chat
bug
Something is not working
design
Graphic/visual design
dev environment
Config, builds, CI, deployment, etc.
docs
Documentation
duplicate
This issue or pull request already exists
enhancement
Improving existing functionality
feature
New functionality
good first issue
Dive in, and start contributing
idea
Something to consider
invalid
Not a bug
kredits-1
Small contribution
kredits-2
Medium contribution
kredits-3
Large contribution
on hold
Currently not actionable
ops
Manual IT ops activities
question
Looking for an answer
release
major
release
minor
release
patch
security
All your base are belong to us
ui/ux
User interface, process design, etc.
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bkero bumi fsmanuel galfert greg hueso raucao slvrbckt
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kosmos/chef#8
No description provided.
Delete Branch "bugfix/nodejs_update_mastodon_fixes"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?