Adjusted jwt access token exp expiry value to 5 days from seven, also confirmed it works and an expired token loses access and adjusted the skew to 0
This commit is contained in:
@@ -14,12 +14,11 @@
|
||||
|
||||
OUTSTANDING MAJOR AREAS TO BETA
|
||||
|
||||
- Features
|
||||
Raven license key generator in rockfish
|
||||
once done then test out license code, particularly expired can login as superuser etc
|
||||
we don't want to give away any freebies!!
|
||||
New server no license gives big error about license count exceeded when it shouldn't as there are no user's other than superuser which should not count
|
||||
make that go away
|
||||
- License
|
||||
When license expires all tokens to be revoked?
|
||||
otherwise users can just keep working until they log out??
|
||||
|
||||
- Features
|
||||
Customer workorders
|
||||
has pertinent cases
|
||||
Customer CSR something
|
||||
@@ -34,6 +33,16 @@ OUTSTANDING MAJOR AREAS TO BETA
|
||||
There is no clear ROLES guide and we need one for sure. I like the idea of dynamically generated in the UI so we can change it and it's always accurate and
|
||||
useful for us to ref as well, should have done it long time ago.
|
||||
- Installer
|
||||
Linux
|
||||
Offer as archive for docker and for bare metal
|
||||
Do a manual install of both to a clean server and document each step in the manual
|
||||
Windows
|
||||
standalone self contained or with postgres externally
|
||||
radio buttons in installer "()Install standalone postgres database server, ()Use existing postgres server"
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -51,7 +60,11 @@ OUTSTANDING BEFORE RELEASE
|
||||
- Biz decisions
|
||||
pricing
|
||||
licensing
|
||||
Need options for every plugin option etc, right now it's just made up accounting and rental shit
|
||||
hosting
|
||||
Purchasing pages on our site for raven
|
||||
Legacy area for v7 on release and new area for raven
|
||||
forum for support squared away
|
||||
|
||||
|
||||
|
||||
@@ -646,17 +659,6 @@ EACH OBJECT DEV CYCLE:
|
||||
|
||||
POST "REALITY" OR IN PARALLEL "REALITY" related items:
|
||||
|
||||
todo: CYPRESS TEST DATE / TIME / DATE_TIME controls switched back to vuetify ones
|
||||
widget entry form test rewrite
|
||||
https://github.com/cypress-io/cypress/issues/7404
|
||||
https://github.com/vuetifyjs/vuetify/issues/10988#issuecomment-726089949
|
||||
|
||||
|
||||
todo: Schedule form
|
||||
- This one is big but requires the data to be there so as soon as implement enough things that are scheduleable then do this
|
||||
- printing / reporting schedule? Do-able?
|
||||
- https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/729
|
||||
|
||||
|
||||
todo: can beta test at this point
|
||||
See below, specific ideas about public beta test (User accounts not seperate installs maybe)
|
||||
@@ -680,15 +682,6 @@ todo: Documentation POST "REALITY"
|
||||
|
||||
|
||||
|
||||
todo: ONGOING search for memory leaks
|
||||
The 7 times system seems to work the best
|
||||
Excercise item a few times to settle it in memory, take heap snapshot, force gc, take total of 3 heap snapshots forcing gc each times
|
||||
Excercise item 7 times exactly, take 3 more heap snapshots forcing gc before each one
|
||||
Compare snapshot 6 to snapshot 3 look for Delta 7 times items to find leak
|
||||
https://developers.google.com/web/tools/chrome-devtools/memory-problems
|
||||
https://nolanlawson.com/2020/02/19/fixing-memory-leaks-in-web-applications/
|
||||
|
||||
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 7 - EXTENSIONS (was plugins)
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@ -710,6 +703,7 @@ Plan the order of criticality for extensions
|
||||
Implement in order or priority
|
||||
Fuck peachtree?
|
||||
probably not, need to check again our install count of extensions
|
||||
Also something new from the peachtree people, online edition of something or another, a guy asked about it the other day Nov 2021
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user