- Wallet discounts (by a separate table)
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 30 2020
- Improve logon form, fix tests, remove dummy method
I'd re-check on 1st of month.
- Update for review
Here's an example of a more complex tls_config I use on my servers (using certbot + letsencrypt):
Mar 28 2020
Looks good to me.
Apply patch to the develop branch
Looks like a nice simple change.
You need to supply Guam with a valid X.509 certificate (issued by Let's Encrypt, for example) and adapt the tls_config section of /etc/guam/sys.config accordingly.
in addition, the 2FA checkbox could use an explicit (as in not hidden behind the info button) hint
that this only works when the users also sets it up in roundcube,
as well as a hint that this will disable the usage of external clients for now
Guam should be listening on port 993, so please check if the Guam service is up and running.
Worked fine, I could't reproduce the issue. Closing this.
Mar 27 2020
- Remove unused lang entries
- Fix phpstan errors
- Remove configured factors on entitlement delete, added tests
in addition, the 2FA checkbox could use an explicit (as in not hidden behind the info button) hint
that this only works when the users also sets it up in roundcube,
as well as a hint that this will disable the usage of external clients for now
I will look into integrating the patches.
- Use the actual hosted root dn
- Obsolete domain-specific roles
- Create the base roles
- Also progress certain roles
- Add postfix configuration changes to poll for the new status
Rebase on master
Mar 26 2020
We'll move forward with a new table: discounts { id, discount, description, code (for vouchers), active } and wallets.discount_id.
Mar 25 2020
I would do all these calculations on the server side. Probably returned with extended domains/users api requests, or maybe better via /api/v4/wallet/{wallet-id} (which does not exist yet).
In D1057#11914, @vanmeeuwen wrote:This now fails twice in a row, both on Tests\Browser\LogonTest::testLogonSuccessful: Saw unexpected element [body #status-box].
This now fails twice in a row, both on Tests\Browser\LogonTest::testLogonSuccessful: Saw unexpected element [body #status-box].
Mar 24 2020
Screenshot
- Add console script to set/get user status
- Add console command to set/get domain status
- Browser tests for status indicators
- Make user:status and domain:status commands available in non-production mode only
- CS and typos fixes
One failure remains;
Reopen
Didn't have the tunnel up.
Requesting review on the following test failures;
Fix
CS fixes
Can't say much about the php side of things.