Meeting started at 2026-07-01 17:01:01 UTC

The Meeting name is 'fedora-server'

!group members server-wg

Members of server-wg: Alexander Bokovoy, Adam Williamson, Paul Maconi, Emmanuel Seyman, jwhimpel, Kevin Fenzi, korora (@korora:fedora.im, @korora1981:matrix.org), mowest, ngompa (@conan_kudo:matrix.org, @ngompa:fedora.im, @pharaoh_atem:opensuse.org, @ngompa:kde.org, @ngompa:almalinux.im), Peter Boy, Stephen Gallagher

Welcome to our weekly Server WG meeting.

I'll post the agenda in 2-3 minutes.

As usual, let's wait a moment for everybody to show up.

!hi

Brett: Brett Weir (brettweir) - he / him / his

!hello

Emmanuel Seyman: Emmanuel Seyman (eseyman) - he / him / his

!hi

Jocelyn Gould (UTC-4): Jocelyn Gould (korora) - she / her / hers

Welcome Brett @EmmEmmanuel Seyman Jocelyn Gould (UTC-4)

Our forum is a bit ‘light’ at the moment. But let’s get started.

!hi

x3mboy: Eduard Lucena (x3mboy) - he / him / his

!hi

John Himpel: John Himpel (jwhimpel)

info Walk through long outstanding issues

Did I miss something?

Hi John, now our quorum is complete.

I'm just coming back so, not sure where to start helping

Hi x3mboy, it's a long time back, we last have you seen here.

There are several things, I'm sure we'*ll find something.

hey, x3mboy !

Let's start

Awesome

Hi to all of you team

meetings overview:

Regarding the action, see the list in our

https://docs.fedoraproject.org/en-US/server-working-group/wg-minutes-2026/

Conan Kudo will fix Kiwi to set the right partition type of Linux LVM for the system partition on KVM guest and arm image.

pboy will implement the Fedocal workarount for providing meeting location address

6.

MatH will compose the existing ideas and proposals into a TOC proposal, perhaps already for next meeting

5.

eseyman writes an Ansible playbook that applies the official post-installation tasks.

4.

1.

NEW: korora resolves both the tickets #175 & #176 appropriately as discussed.

2.

Brett, Jocelyn and MatH will put together a proposal for the initial small set of apps for home server spin-off from the current ideas and proposals

3.

I guess, item 1 is done if I rear Jocelyns message correctly?

I guess, item 1 is done if I read Jocelyns message correctly?

Yes, Item 1 is done.

Well, the tickets were PRs

My PR is closed, and I merged in #176.

FYI, I'm still dealing with packaging issues and haven't had time to do ansible stuff

I think 2 is sort of resolved, not formally, but there seemed to be agreement that the initial set of services is what was documented in the Tech spec already, so Apache, NFS, etc. So I had pivoted to developing the main docs

Yeah, and I didn't manage to apply item 6.

Brett: Yeah, let's spare this for topic 3

I 4concur, the base stack is figured, we just need to write it up now

Anyhow, the days are too short.

And too hot...

OK, let's proceed.

Tracking issue: https://forge.fedoraproject.org/server/tickets/issues/203

I propose, we should start our testing a bit earlier, as the last

With 44 we had some minor issues with VMs. We should try to get that fixed early.

I was testing an early version of F45 and could not get nfs server to allow connections from F44 clients. Could someone else give it a try before I file a ticket?

Jocelyn Gould (UTC-4): Are you ready for that?

Once i get my server back up and running when the earth cools down, i'm good with starting to work on that

OK

Jocelyn Gould (UTC-4): Coud you chech the VMs again?

I will start working on that as well.

I suppose, item 4 is not yet fixed. You may have to contact Neal Gompa (Fedora)

!undo

I have a request: Can we create a project board for the F45 testing, just so things don't get lost in the shuffle?

Last period I tested all the iso's. Can someone help with that. (Proviously, I was the only one with the test equipment at hand).

+1 for the project board

Good idea! Let's talk about it on our room and we can setup something. Among others we would have to define more detailed issues.

A board is much better as my complicated issue table. 😀

I guess that's everything regarding this topic for now?

Let's proceed

Tracking issue: https://forge.fedoraproject.org/server/tickets/issues/203

Brett: your floor

sorry,

https://forge.fedoraproject.org/server/tickets/issues/192

Copy and paste is dangerous

hahaha, well, yeah, I think I already said most of what I would say. Instead of writing the whole home server tutorial, I wanted to bake more ideas into the user documentation, and reference it from there.

Do we have a sanitised list among the various posts?

https://forge.fedoraproject.org/server/wg-documentation/src/branch/main/modules/ROOT/pages/docs/server-technical-specification.adoc#_4_3_projected_server_roles

This feels like a pretty solid list:

But my first thought is Apache, certbot, NFS.

Oh and DNS

Seems like as good a starting point as any, and once those are in place, adding more services based on interest.

Something like Appl. server it probybly out of range, as well as Postgres?

Oh yes, Postgres is good!

Calendar and todo server

Samba (and possibly NFS)

Apache revers proxy

Probably a list like:

Cockpit

Mail service

Or is this too less?

I think we can ignore Samba unless we're trying to support like a small office with Windows users.

I think we should include sam a

I guess Samba is vital, e.g. for backups

Oh, I was thinking restric for backup solution, also in fedora

Running your own mail server seems hard and I'm not sure I'm up to the task

Not necessarily a mail server, but a local mail storage via dovecot.

Oh, got it, that would be worth leaning into.

I also think a forgejo + forgejo runner would be a good use case, but doesn't need to be an initial set

forgejo is available in fedora

i'd say dovecot is still difficult for home server with a residential ISP

Samba is useful for media streaming, backups, ...

Oh, got it, that would be worth learning more about.

Well, to keep privacy and data sovereignty local mail storage is vital

we definitely need some sort of file storage, samba is an option though personally i'd prefer some kind of DAV interface for things like DAVx5

fair enough

And all these are offerings, a user can just not activate them.

If you can use your server for mail backups, I'd love to explore it. This is something I worry about with my own cloud mail accounts.

So we would start (alpa version) with Samba, NFS, Mail service (map storage), Cockpit, Calendar and todo server, Apache revers proxy, and may expand on demand for the release

proposed !agreed We will start for alpha version of home server with the apps Samba, NFS, Mail service (map storage), Cockpit, Calendar and todo server, Apache revers proxy, and may expand on demand for the release

Do you mean "map" or "imap"?

sorry imap!

proposed !agreed We will start for alpha version of home server with the apps Samba, NFS, Mail service (imap storage), Cockpit, Calendar and todo server, Apache revers proxy, and may expand on demand for the release

https://codeberg.org/brettweir/ansible/

As part of this, I've stopped writing a full-length document and started capturing use cases more directly in my homelab environment:

proposed !agreed We will start for alpha version of home server with the apps Samba, NFS, Mail service (imap/pop3 storage), Cockpit, Calendar and todo server, Apache revers proxy, and may expand on demand for the release

And I've started ramping up on server documentation. I've submitted a few PRs related to style. I've been waiting until those were merged before making content changes, but if the changeset is hard to review, I can close them and pivot to adding more content.

Yeah, Ansible control hub has to be include for user configuration, too, of course!

proposed !agreed We will start for alpha version of home server with the apps Samba, NFS, Mail service (imap/pop3 storage), Cockpit, Calendar and todo server, Apache revers proxy, Ansible and may expand on demand for the release

Oh, yeah, I like having a base set of infrastructure components and building on them. If we can use the server to drive its own management, that's pretty cool! (re Ansible)

Any objections?

3

2

1

!agreed We will start for alpha version of home server with the apps Samba, NFS, Mail service (imap/pop3 storage), Cockpit, Calendar and todo server, Apache revers proxy, Ansible and may expand on demand for the release

Hm, zodbot!!

OK thanks zodbot

We should discuss, how we want to organize work on Kiwi. First thing, to ist interested so spend some work on it?

first question, why Kiwi and not Image Builder, so I understand

One idea is, to provide a public server, with Kiwi development env installed, and every WG member can get an access.

Yeah, image builder is an alternative.

I was under the impression that Image Builder was a Fedora project, but I don't actually know.

Most Fedora images are build with kiwi, but a few with image builder.

I've heard good things about KIWI too.

Oh gotcha.

But the basic consideration is the same: Do we want to use a shared server where everything is installed, or do we want to set up each our own dev env?

The server would be sisyphos.resdigita.eu which John and me already used for NFS testing.

It's a VM on one of my servers.

My personal philosophy is "local-first development", I like to provide tools that anyone can run on their machines, and if it works locally, then it will work in CI. Granted, VM builds are difficult in CI, so we'd probably need to build our own custom CI runner for image releases.

I'm not sure if we need CI in this case. The images for distribution would be built on Fedora infra, of course.

Not knowing too much about KIWI, couldn't we have individual copies of the development software with the configuration files stored in a common repository?

Oh for sure, it makes sense that Fedora would have infra for building images. 😅

John Himpel: that should be possible, as well. Maybe a good idea. We could use our home server repo for that.

That would allow me to create my own "spin", yet still participate in the group release/iso generation.

+1 to capturing tool configuration source and providing instructions for contributors to set up their own environment

I'm a fan of local workings (even if it is just an ssh connection to my server in my house

proposed !agreed The WG will use the home server repository to make all configuration data and installation information available. Interested WG members can use this to set up their own development environment.

What do you think? Objections?

+1

That sounds more than fine

+1

+1

OK, then

Who will start to set up and document kiwi dev environment? And is someone interested to experiment with Image Builder as an alternative?

I've not played with either (and am not sure my brain can handle anything else, it might start smoking....)

Jocelyn Gould (UTC-4): yeah, you are already really busy with some Server tasks, and Fedora Docs as well.

We’ve already gone over our time.

Though I'm interested, I probably don't have the bandwidth.

So let's proceed shortly with

Anything here?

x3mboy: Are you still around?

OK, let's close our meeting today.