Cleanup
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jun 14 2024
Jun 13 2024
Removed print statement
To be able to validate things we now just validate first, and then create everything, and bail out if user or domain are preexisting.
There's doesn't seem to really be a point in converting existing users.
Fixed mail options
Adapt to recent changes
Fixed, sorry about the downtime.
Jun 12 2024
it's not, and I'm also not sure if this really solves anything since we actually try to keep the balance around 10 CHF (I think?). Maybe the better solution would be to just prominently display a warning that the user is being rate limited.
- Complete tenant-independence in CLI commands
- Fix regression, cleanup
Be careful when deploying this. Make sure the queue is empty.
We want to use app.password only when *not* in production of course
This changes nothing if we run the jobs on the main system. But I agree we need a tenant context. See T264 in Phorge.
This make app.passphrase to be used only on production, which is wrong.
I don't think this makes sense, because the same is done by the observer already.
Jun 11 2024
I used this to create new users on demoresller.kolab.klab.cc and I don't see why not.
I guess not setting a password would be an alternative if that works... The random password is just there until somebody sets one that somebody knows.
One more note. Currently if topUpWallet() throws exception (for any reason, e.g. Mollie connection issues) the WalletCharge job will try to top up the wallet again. Here it won't happen, so it will be more fragile to temporary issues with the payment provider. Catching the exception and invoking a separate WalletCharge job might make sense.
Jun 10 2024
- Update French localization
Jun 5 2024
10 here is 0.10 CHF, is this the intention?