NOTE
If your issue is for security or deals with sensitive info please mark it as private using the checkbox below.
FAMNA is in need of a Nextcloud + Collabora Office for coordinating on shared documentation, presentation materials, and maintaining our LibreOffice formatted templates.
FAMNA is willing to maintain the environment and keep it scoped to Fedora Ambassadors and mentees.
4 vcpus 16GB of memory 80GB of storage Fedora 39
Preferably a simple LAMP VM for the scope and scale of this, but possible to deploy on Openshift if necessary.
Use FAS auth for authentication through nextcloud. Two DNS resolveable subdomains (nextcloud. and collab.) for let's encrypt (Collabora will itself be solely consumed through nextcloud, but they live as separate services)
The sooner the better. We've been using my personal nextcloud server for this and it it really should live on Fedora infrastructure, especially as more FAMNA members are using it for more things.
We have two FAMNA members, myself and paradoxguitarist, who have experience deploying, upgrading, and automating nextcloud, who are willing to set it up and keep it maintained.
Ref. conversation with nirik on Fedora Infra Matrix channel.
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
I'm just curious what the FAMNA means.
@zlopez : FAMNA: Fedora AMbassadors North America, I think...?
ok, we can spin up a aws instance and hand it off to you.
Some questions:
Is famna.fedorainfracloud.org ok for hostname?
so then I guess also you want collab.famna.fedorainfracloud.org and nextcloud.famna.fedorainfracloud.org as cnames? or do you want famna-nextcloud.fedorainfracloud.org / famna-collab.fedorainfracloud.org or something else?
for fas auth... are you planning on using SAML2 or OIDC? we can do either, but will require some setup...
Yes, that works for this
nextcloud.famna and collab.famna seem more remember-able to me.
Yeah, I assume OIDC will be the easier of the two on both ends. Otherwise, I can generate a SAML SP and metadata for it.
https://apps.nextcloud.com/apps/oidc_login https://apps.nextcloud.com/apps/user_saml
ok. Should be there and both your ssh keys are on it.
I put it in us-west-1, hope thats ok.
Can you open a new ticket when you are ready for OIDC? We have a template that lists all the info we need to set that up.
Let me know if you need anything else on it.
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
I'm setting things up this evening and noticed an issue. collab.famna.fedorainfracloud.org exists but there doesn't appear to be a DNS entry for nextcloud.famna.fedorainfracloud.org
Can we also get a CNAME for nextcloud.famna.fedorainfracloud.org to famna.fedorainfracloud.org ?
Metadata Update from @vwbusguy: - Issue status updated to: Open (was: Closed)
It looks like it's a typo. s/nexcloud/nextcloud
Non-authoritative answer: nexcloud.famna.fedorainfracloud.org canonical name = famna.fedorainfracloud.org. Name: famna.fedorainfracloud.org Address: 52.53.65.154
Oops. Fixed.
Sorry about that.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.