Heiner
Heiner
Is your Seatsurfing instance reachable via https scheme on the default port 443? If not, PR #899 (to be released with version 1.33) will add the ability to specify `PUBLIC_SCHEME`...
Ports 3000 and 3001 should not be accessed directly, but through the server/backend running on port 8080. Please share your entire container and proxy configuration, something is wrong there...
Thanks for sharing! I think I have identified one issue with how the `X-Forward-*` headers were handled in the admin and booking ui. Fix is included in version 1.33.1. Please...
Version 1.35.3 includes improvements for nginx and you'll find a working config example here: https://github.com/seatsurfing/seatsurfing/tree/main/example/nginx We'll try to add further improvements shortly.
Please take a look at Version 1.36. It should eliminate these errors, but please read the information on the breaking change in the release notes: https://github.com/seatsurfing/seatsurfing/releases/tag/v1.36.0
As far as I can tell, version 1.36 fixes these issues due to the way the Booking and Admin UI are served (no built-in reverse proxy required anymore). If you...
Hi @ivan1823 Thanks for sharing your ideas! Could you describe what kind of rules you'd like to implement? Examples would be helpful.
No. 2 has been released with version 1.32.
Hi, @mdomocos recurring bookings respect all the options that are valid for manually created bookings (such as maximum number of bookings per user, max. days in advance, etc.). Thus, recurring...
Okay, I see. Thanks for explaining. I'll check.