Marking this topic as solved due to the lack of responsiveness. If this is not the case, please just write and I can mark the topic as unsolved again.

@nebulon yes, Howe once users start diverging from the default build there is no mechanism to keep them in sync across app upgrades.

Oh wow, what an interesting (and slightly frightening) failure mode! "Your log files are so big that we've given up on managing them."

Just almost tripped over this myself. It seems that "requireAuthentication": false hides the login button, and so the whole login /admin situation gets confusing. Might be worth adding that to the docs.

@nebulon I see. Thank you!

Hi all, I believe I've found a solution that works. With this setup, my logged-in users can create pads, and guests can edit them as long as read-only mode is not enabled by the pad owner. Guests, however, cannot create pads. { "ep_guest": { "username": "guest" }, "users": { "user1": { "is_admin": true }, "guest": { "displayname": "Guest", "displaynameChangeable": false, "readOnly": false, "canCreate": false } } }

@marylou @nebulon Currently, accessing Etherpad's admin interface is a two-step process (after the config mentioned above): First, visit /admin-auth/ to authenticate with your Cloudron user. If successful, you'll see the word "Authorized" appear. Next, visit /admin. This should no longer redirect you to /admin/login, and should instead show you the Etherpad admin console.

@nebulon Thank you! Great to hear. Happy to say that our custom skin loads properly.

@sponch Same here. But I guess, this should be a new topic in this forum. I've got the "username": { "is_admin": true in the setting.json, but I can't login with the users' credentials.

Great to hear! Looking forward to testing it out!

so there's no way to have authentication required and still be able to share a document publicly without having the viewer to sign in?

So the settings.json shown in the admin UI is the wrong place to make changes. It will get reset on ever app restart. To make that clear, I pushed a new app package, which disables the admin UI bit to edit the settings.json within the app.

Hey, the issue seems to be resolved after updating Thank you !

@girish all right, thank you for your tips. In general, I find your support extremely great, very high quality, thanks for everything!

@humptydumpty said in Plugin for automatic delete: @robi You beat me to it. [image: 1668209139819-screenshot-2022-11-11-172507-resized.png] Hi, plugin installation works, but the code "ep_delete_after_delay": { "delay": 86400, // one day, in seconds "loop": true, "loopDelay": 3600, // one hour, in seconds "deleteAtStart": true, "text": "The content of this pad has been deleted since it was older than the configured delay." }, don't work after putting in settings.json and restart app. I think a text should be displayed at a new pad, or? In my case there is no text...

Etherpad stores the documents and its data in the mysql database on your VPS. While editing, the clients sync their changes mostly real-time to the server. I am not fully sure what happens if you are offline and edits cannot be submitted to the server, for some time, then later the client gets online again, while the document already has changed by other clients on the server. Essentially for such more complex conflict resolutions, you have to ask upstream or see what their docs have to say about this.

@nebulon excellent ! the display issue is now fixed (after deleting cookies of course). Many thanks for the support !

I'm in touch with Scaleway right now. I will update here if they find anything out of interest.