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

Migrate ejabberd uploads to mod_s3_upload and Garage #518

Merged
greg merged 2 commits from feature/469-ejabberd_s3 into master 2023-10-17 19:07:24 +00:00
Conversation 2 Commits 2 Files Changed 26 +326 -136
raucao commented 2023-10-10 16:05:37 +00:00
Owner
Copy Link

In addition to installing and configuring the new module, this also enables public access to the S3 API via bucket-name.s3.kosmos.org as well as Web access on bucket-name.web.s3.kosmos.org (when enabled).

Also includes some drive-by improvements to Chef attribute naming and usage.

Tested and running in production already.

closes #469

In addition to installing and configuring the new module, this also enables public access to the S3 API via `bucket-name.s3.kosmos.org` as well as Web access on `bucket-name.web.s3.kosmos.org` (when enabled). Also includes some drive-by improvements to Chef attribute naming and usage. Tested and running in production already. closes #469
raucao added the
kredits-2
ops
 labels 2023-10-10 16:05:37 +00:00
raucao added 2 commits 2023-10-10 16:05:37 +00:00 
And move the configuration-specific preceding dot to the config
template.
In addition to installing and configuring the new module, this also
enables public access to the S3 API via `bucket-name.s3.kosmos.org` as
well as Web access on `bucket-name.web.s3.kosmos.org` (when enabled).

Also includes some drive-by improvements to Chef attribute naming and
usage.

Co-authored-by: Greg Karékinian <greg@karekinian.com>
greg was assigned by raucao 2023-10-10 16:05:42 +00:00
raucao self-assigned this 2023-10-10 16:05:42 +00:00
raucao requested review from greg 2023-10-10 16:05:49 +00:00
raucao commented 2023-10-17 10:02:09 +00:00
Author
Owner
Copy Link

@greg Could you have a last look at this perhaps?

@greg Could you have a last look at this perhaps?
greg approved these changes 2023-10-17 19:07:10 +00:00
greg left a comment
Owner
Copy Link

👍

👍
greg merged commit 873c235539 into master 2023-10-17 19:07:24 +00:00
greg deleted branch feature/469-ejabberd_s3 2023-10-17 19:07:24 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
greg
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
kredits-2
ops
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bkero bumi fsmanuel galfert greg hueso raucao slvrbckt
No Assignees greg raucao
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kosmos/chef#518
No description provided.
Delete Branch "feature/469-ejabberd_s3"

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?