Hello,

That particular docker compose setup is not up to date. I would recommend using the current dev docker setup which is here : https://github.com/agorakit/agorakit/tree/main/docker/dev

I know the readme says to not use for production, but it's I think the best place to start.

A very welcome contribution would be feedback from you on how it went, since probably very few people use this specific docker setup currently. It's based on frankenphp which is quite new and less konwn.

I'm happy to assist you in creating the perfect, easy to use docker setup for production :-)

Thank you, I will try it out tonight after work!

I just realized jointly discussing/commenting/planning an event is not possible. Is this something you have on your roadmap?

Agorakit seems way more polished than Mobilizon which is the alternative I am considering, so I would prefer to make Agorakit work for my use case :)

It depends what you have in mind. I try to provide just the common features that work for various use cases, so for instance if you plan a event, you discuss it in the group with one or several discussions, then someone creates the event (in the description of the event you could link to the discussion and vice versa).

As for joining events, group partitipants can mark if they will attend or not to an event.

It's basic but works fine as far as I have seen in other groups.

I try to not force any specific workflow to keep things simple (for example, if I added the ability to comment on events, one might have to check in two different places to see if there are discussions on this event)

But don't hesitate to tell more about your use case :-)

True. Maybe we should create a discussion before the event and keep the discussion there.

My use case was when proposing an event, say in my case "Let's go climb this boulder next saturday" I would like to set the date and start a discussion regarding the event. Then if it turns out that no one wants to or is able to join for the event on saturday, the event is just cancelled and removed.

Think of it as a calendar of proposed events.

I go running on wednesdays, join me if you'd like. A simple single event.

We climb indoors every tuesday, that would be a recurring event where we can report if we are coming or not and comment on the events saying stuff like "I got this thing before, so I won't arrive until x a clock" or other comments in the similar manner.

For these recurring events, it is nice to have a discussion per event so that this tuesday does not get mixed up with next tuesday.

Also, if I just post a discussion saying "I want to go running on wednesday" that will not be as tangible and actionable as if it is already in the calendar. At least that is how I percieve it. I want people to be able to comment on my run, but I don't want to discuss it before creating it. I will run wether anyone joins me or not. The discussion feature on the event will be for questions like "can we meet at X instead of Y?" or similar.

But I get it that you want to keep things simple. This was just something I felt was missing, but my use case might be a unique edge case for all I know :)

This was a brain dump, but I hope I have managed to convey what I am looking for here. Just ask if anything was unclear :)

It's perfectly clear, let's let it rest a bit and see how it evolves conceptually. Maybe others will bring input.

About Docker, did you manage to make it work ?

How did you manage?

Hi again Mr Knutsson

> Think of it as a calendar of proposed events.

I like this idea.

We could add a flag for a proposed event. And a relation with a discussion.

Yet as you may notice, we need more developers to do all the work. Some priorities must be set and that's mostly Philippe's work.

Possibly, to have a new production-ready docker process would be of higher priority. 

@obenassy thank you for creating the github issue about "proposed" events: https://github.com/agorakit/agorakit/issues/537

I created a second one about adding discussions to events : https://github.com/agorakit/agorakit/issues/538

As for prioritizing, my opinion is that if someone contributes time to the project, (s)he can decide what to work on, thus changing the priorities a bit :)

So if you want to make it happen faster, don't hesitate to work on it. All thoses features are definitely in line with the project so they will be accepted.

As for Docker for production, since I'm not using it, I'd need more input on how to make it as reliable as possible.