Max von Tettenborn

I have the same issue, also on Arch Linux. I'd like to use an older version of the image in the meantime because at some point in the past it...

This seems to have worked, thanks a lot! Although I always fear that I break something when doing something like this. This should not be needed.

Hi @drizuid. A few wrong assumptions you have there. Let me clarify and start with the most important one: 1. I will compensate app devs for having their apps in...

I'd also vote for this feature. I see no particular security risk if the URL is unguessable just like shares. Also, it would be useful to be able to set...

I'd like to upvote this feature request. It would be very useful for me and surely for many others.

Hi. Thanks for your reply. > This could be OK, although as I understand it: this might require some co-ordination between the PHP application and the container? I am not...

> Maybe true, but that would also make it more difficult to respond to support questions. Ok, true. I get that. > Does Docker support a way to run a...

Ok, good points. Maybe you could proceed iteratively. Step 1) Introduce name-only members, which should be simple. Step 2) Allow an admin to transfer name-only transactions to a registered user...

In OOP-speak, you have a superclass: User and two subclasses: real user and name-only user. There are proven ways to design a DB schema for that, see e.g. here: https://stackoverflow.com/questions/3579079/how-can-you-represent-inheritance-in-a-database...

Ok, I'm not sure where the difference is between member and user. But yeah, this would be the general idea.