This commit is contained in:
@@ -9,6 +9,8 @@ TODO: WEBSITE TASKs
|
||||
|
||||
|
||||
https://www.postgresql.org/about/news/postgresql-15-released-2526/
|
||||
even if not recommending it to users need to test against it as no doubt some will just install and also maybe hte script we link to in install
|
||||
autoamticaly installs this now?
|
||||
|
||||
- Subscribers need to know taht their server will be rebooted daily if and when security updates come in
|
||||
need a system to handle that or a day of the week to handle that, maybe a preferred time or ...?
|
||||
@@ -20,6 +22,10 @@ https://www.postgresql.org/about/news/postgresql-15-released-2526/
|
||||
#####################################################################
|
||||
TODO:Clean up this document from here down and re-organize / prioritize
|
||||
|
||||
todo: clean up solutions.txt and research.txt and move into a consolidated coding focused how-to.md doc
|
||||
|
||||
TODO: Move all items here into cases, basically clean out entirely this document so it's more like a current todo only
|
||||
|
||||
- subscription licensing and terms, I have some links somewhere to good examples
|
||||
CRITICAL! Needs to be in place with wording on reasonable use etc to protect us etc
|
||||
- subscription process info to request how to go about it, improvements to manual process
|
||||
@@ -111,6 +117,23 @@ todo: research stuff below, then website stuff and move on
|
||||
L8ER >>>>>>>>>>>>>>>>>>>>
|
||||
|
||||
|
||||
todo: Ongoing, document this as a process to regularly follow for back and front end, make a case then into howto I guess
|
||||
MUST be done before next major dependencies update
|
||||
# Security checks and tools
|
||||
|
||||
|
||||
## NPM
|
||||
https://snyk.io/blog/ten-npm-security-best-practices/
|
||||
https://docs.npmjs.com/cli/v8/commands/npm-audit
|
||||
|
||||
npm doctor
|
||||
npm audit
|
||||
|
||||
## Nuget
|
||||
|
||||
https://docs.microsoft.com/en-us/nuget/concepts/security-best-practices
|
||||
dotnet list package --deprecated
|
||||
dotnet list package --vulnerable
|
||||
|
||||
|
||||
|
||||
@@ -588,7 +611,10 @@ For example head office and many more.
|
||||
todo: Unit help page doesnt have a screenshot of the menu, maybe others are also missing this, it's important when supporting people
|
||||
todo: docs add view on map an image of a map to snazz it up.
|
||||
|
||||
todo: foucsed docs about common tasks like a getting started or how to section not just a ui help
|
||||
todo: "Guided tours" foucsed docs about common tasks like a getting started or how to section not just a ui help
|
||||
This should be a tour that leads a user through doing a task in the evaluation data and also it should include screenshots showing what they would see
|
||||
so they don't need to actually do it, they can just view it.
|
||||
|
||||
the old manual had guidance on inventory, how to use it how to start it etc
|
||||
go through old manual find candidates for how to's similar to how fastmail help has guidance on specific things that are FAQ's basically / tutorials
|
||||
or this might be the original idea of a guided tour feature that walks through stuff in the actual UI?
|
||||
@@ -601,6 +627,11 @@ todo: server metrics ops-metrics no screenshots??
|
||||
|
||||
todo: log level page https://ayanova.com/docs/ops-log/#log-level doesn't mention config.json like as even a thing like it does with other config settings pages
|
||||
|
||||
todo: Is th8is documented anywhere?:
|
||||
- Support the latest browser and the one before it of every major browser like gitlab does:
|
||||
- Supported web browsers, We support the current and the previous major release of Firefox, Chrome/Chromium, Safari and Microsoft browsers (Microsoft Edge and Internet Explorer 11).
|
||||
- Each time a new browser version is released, we begin supporting that version and stop supporting the third most recent version.
|
||||
|
||||
|
||||
|
||||
## MIGRATION ITEMS
|
||||
|
||||
Reference in New Issue
Block a user