This commit is contained in:
36
ayanova/devdocs/rando-todo.txt
Normal file
36
ayanova/devdocs/rando-todo.txt
Normal file
@@ -0,0 +1,36 @@
|
||||
Grab bag stuff that didn't fit into official TODO
|
||||
|
||||
todo: VUE / VUETIFY ROADMAP RELEASES (Sept 23 2020 was put on hold as it appears vuetify is way behind so looking like post release but check again here)
|
||||
Q1 2021 is vuetify v3
|
||||
https://vuetifyjs.com/en/introduction/roadmap/
|
||||
look at what's coming on the radar before release in the big libs I'm using at front end as well, i.e. new vue or vuetify major release etc
|
||||
I would really like to release without a huge new migration looming over my head post release with potential breaking changes
|
||||
Vue 3.x is about ready now or very shortly: https://v3.vuejs.org/guide/migration/introduction.html#overview
|
||||
"The Composition API is purely additive and does not affect / deprecate any existing 2.x APIs. I"
|
||||
looks like I can switch to vue 3 without code changes, at least when it comes to composition api
|
||||
Vuetify 3.x is lagging way behind vue 3.x and doesn't appear to be even close so
|
||||
Put front end newification on hold until it all shakes out, looks like post release`
|
||||
|
||||
|
||||
todo: See if this has a use: as an aside there is a relative time formatter available which might be handy
|
||||
does locale aware things like "5 days ago" or "8 years from now" etc
|
||||
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/RelativeTimeFormat
|
||||
|
||||
todo: hide swagger logo and branding in api explorer
|
||||
Is this really that important?
|
||||
also, in the docs is a section specifically saying I should do something because I'm using newtonsoft json not microsoft built in
|
||||
https://github.com/domaindrivendev/Swashbuckle.AspNetCore#systemtextjson-stj-vs-newtonsoft
|
||||
https://github.com/domaindrivendev/Swashbuckle.AspNetCore
|
||||
|
||||
|
||||
todo: service workers for monaco going in root of website folder, must be a config setting to move it into the proper place (not there)
|
||||
couldn't find anything about it, may need to post to ask, it's not the end of the world but kind of stupid looking as all the rest of the js is in subfolder
|
||||
https://github.com/microsoft/monaco-editor-webpack-plugin/issues/126
|
||||
awaiting reply, if nothing by the time I get here then delete and wait for email notification or if I care enough again to bother with it (cosmetic)
|
||||
|
||||
|
||||
todo: consider feature to set server to always use a pre-set browser locale settings and not the ones in the browse itself
|
||||
Scenario is user in another country but needs to login and work with central server?
|
||||
server - wide
|
||||
User specific
|
||||
YAGNI / TTM?
|
||||
@@ -1,63 +0,0 @@
|
||||
|
||||
**************************************************************************************************************************************************************************
|
||||
CURRENT ROADMAP
|
||||
|
||||
1) Get the widget edit form completely working with the exception of reporting which can be stubbed out but should be present even if not functional now
|
||||
- Test manually with all devices before baking it in
|
||||
- Make automated test for it
|
||||
|
||||
2) Fundamental stuff for editable objects (minus reporting)
|
||||
Get the Widget list and filter and any other options (except reporting) fully working and ready to roll out.
|
||||
- Nothing left to determine, all done, ready to copy and automated test, with a stubbed out reporting UI
|
||||
- Test manually with all devices before baking it in
|
||||
|
||||
3) Shell consolidation and verification
|
||||
This stage is the finalization of any fundamental shell stuff so thorough testing and confirmation
|
||||
|
||||
Scaffold the shell framework completely in place as much as possible so that we know there will be minimal other changes required
|
||||
- All areas stubbed out now even if empty, just so you can see it and know what needs to be fleshed out and for demo purposes
|
||||
- Test manually with all devices before baking it in
|
||||
|
||||
Triage stuff into proper later stages
|
||||
|
||||
4) Reporting - figure it out, flesh it out, make it happen
|
||||
|
||||
5) - FINALIZE ALL NON BIZ OBJECT SPECIFIC FUNCTIONALITY
|
||||
All the final features needed that aren't tied to a specific business object
|
||||
Schedule
|
||||
|
||||
6) INSTALLER, LICENSING, ROCKFISH SUPPORT FOR RAVEN
|
||||
|
||||
Look for anything major missing at this point, make it deployable as a package and test the deployment on a raw server
|
||||
|
||||
|
||||
- need to know it will be ready for 3rd parties to try out as much as possible.
|
||||
- Windows installer for self contained fully testable
|
||||
- Linux installation method
|
||||
- Container installation method
|
||||
|
||||
Licensing / Rockfish get this ready with Rockfish to be able to license it in reality so it's ready for 3rd parties
|
||||
- Test the full trial / license business cycle and confirm it's solid and integrated into the Rockfish database properly
|
||||
- Doesn't have to be perfect, just working enough for the real world, can make it easier or nicer later
|
||||
- READ THIS: https://medium.com/@gokulrajaram/self-serve-first-the-overlooked-but-essential-paradigm-underlying-great-software-companies-45a67dbec4c4
|
||||
|
||||
|
||||
7) "Reality" - Build AyaNova 8 / port over all BIZ objects features of v7
|
||||
rishi gorang quattro sonto
|
||||
|
||||
|
||||
8) PLUGINS / ACCOUNTING INTEGRATION
|
||||
|
||||
Port the plugins, need a separate server for QBI Windows etc
|
||||
|
||||
9) RELEASE
|
||||
|
||||
10) BACK END Self Serve readiness
|
||||
- READ THIS: https://medium.com/@gokulrajaram/self-serve-first-the-overlooked-but-essential-paradigm-underlying-great-software-companies-45a67dbec4c4
|
||||
- licensing changes for a online hosted app
|
||||
- Self serve process in place
|
||||
- Ability to upload v7 data from DataDump plugin
|
||||
|
||||
11) RELEASE SELF SERVE
|
||||
|
||||
**************************************************************************************************************************************************************************
|
||||
@@ -1,10 +1,3 @@
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 4 - DASHBOARD / KPI
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
|
||||
|
||||
TODO: gzErrorBox in widget form will not display if form is not ready and form may not be ready if there is an error? (or is that correct?)
|
||||
todo: ops metrics not showing dates on charts that span more than one day (timeline)
|
||||
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@@@@@@@@@@@@ ROADMAP STAGE 5 - FINALIZE ALL NON BIZ OBJECT SPECIFIC FUNCTIONALITY
|
||||
@@ -13,79 +6,8 @@ todo: ops metrics not showing dates on charts that span more than one day (timel
|
||||
todo: Much of this stage below needs TRIAGING, do that first.
|
||||
Any real (corebizobject) shit goes to stage 7
|
||||
|
||||
todo: VUE / VUETIFY ROADMAP RELEASES (Sept 23 2020 was put on hold as it appears vuetify is way behind so looking like post release but check again here)
|
||||
Q1 2021 is vuetify v3
|
||||
https://vuetifyjs.com/en/introduction/roadmap/
|
||||
look at what's coming on the radar before release in the big libs I'm using at front end as well, i.e. new vue or vuetify major release etc
|
||||
I would really like to release without a huge new migration looming over my head post release with potential breaking changes
|
||||
Vue 3.x is about ready now or very shortly: https://v3.vuejs.org/guide/migration/introduction.html#overview
|
||||
"The Composition API is purely additive and does not affect / deprecate any existing 2.x APIs. I"
|
||||
looks like I can switch to vue 3 without code changes, at least when it comes to composition api
|
||||
Vuetify 3.x is lagging way behind vue 3.x and doesn't appear to be even close so
|
||||
Put front end newification on hold until it all shakes out, looks like post release`
|
||||
|
||||
|
||||
|
||||
todo: See if this has a use: as an aside there is a relative time formatter available which might be handy
|
||||
does locale aware things like "5 days ago" or "8 years from now" etc
|
||||
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/RelativeTimeFormat
|
||||
|
||||
todo: MAPPING
|
||||
STATE:
|
||||
Did a quick overview and looked into OSM etc.
|
||||
Not as straightforward as I had hoped, but maybe doable if put into the hands of the end user which backend they want to use
|
||||
Can use a lib to provide the ability to show a map in abstract UI form and user picks back end map provider to use so we are out of the loop
|
||||
I'm thinking the best way to approach figuring this out is to start from the Javascript UI libs and work backwards as things like leaflet and mapstraction
|
||||
etc are good at documenting using alternate backends with their UI libs.
|
||||
So when come back to this look at the UI libs first again
|
||||
|
||||
getting a *lot* of request about this
|
||||
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1816
|
||||
maybe stage 7 or I guess could fake it for now, it's going to be known what will be needed
|
||||
https://news.ycombinator.com/item?id=23722133
|
||||
https://blog.mapbox.com/openstreetmap-a-global-map-for-worldwide-insight-4e041cbf1ec1
|
||||
RESEARCH:
|
||||
Hmm... more complex that I thought, they don't want software using their own server map data much, there are alternatives including hosting it ourselves
|
||||
ECONOMICS / PLAN
|
||||
MAPS are not free from anyone really, maybe the way it should work is:
|
||||
We include a widget for many back ends using the mapstraction library or whatever is out there
|
||||
User can pay a service and set an api key in AyaNova to use that service
|
||||
We could also be that service charging XX a month for mapping to pay for the cost of the mapping service with DO
|
||||
(definitely doable for us, just requires a powerful server which would cost, if things take off we could absorb that cost maybe but for now)
|
||||
OWN TILE SERVER (DOCKER!)
|
||||
https://switch2osm.org/serving-tiles/
|
||||
Sounds like it's incredibly intensive and probably something we do not want to do, but it's an option
|
||||
Needs tons of space and powerful cpu about $220 a month on current digital ocean droplet plans:
|
||||
"300GB+ of fast storage, 24GB of memory, and a quad-core processor for the entire planet"
|
||||
32GB 4vCPUs 6TB 3x 300GB $0.327 $220
|
||||
|
||||
PROVIDERS
|
||||
https://github.com/leaflet-extras/leaflet-providers
|
||||
|
||||
OSM CLIENT JS
|
||||
https://openlayers.org/ - older more complex client lib (Maybe not mobile friendly?)
|
||||
https://leafletjs.com/ - newer less powerful but eaiser lib? (mobile friendly)
|
||||
WRAPPER FOR ANY BACKEND MAP SOURCE
|
||||
http://mapstraction.com/ (note that there are alternatives that are free to OSM possibly like some mapquest and microsoft stuff perhaps that's worth looking into also if people have paid for google?)
|
||||
Why Use Mapstraction?
|
||||
Code your application once and once only; then switch your mapping provider as you desire, depending on your personal tastes, the quality of maps in your area or any other reason you can think of.
|
||||
Switching mapping providers in Mapstraction is often as simple as changing just two lines of code in your application.
|
||||
Mapstraction Features
|
||||
Support for all the major mapping APIs
|
||||
CloudMade
|
||||
ESRI ArcGIS
|
||||
Google – v2 and v3
|
||||
Leaflet
|
||||
MapQuest and MapQuest Open
|
||||
Microsoft Bing – v6 and v7
|
||||
Nokia Here
|
||||
OpenLayers
|
||||
Ordnance Survey OpenSpace
|
||||
Nokia Ovi
|
||||
Yandex
|
||||
Dynamic switching from one maps API to another
|
||||
Show Markers, Points, Lines and Polygons on your map
|
||||
Add image overlays and base map tiles to your application
|
||||
|
||||
|
||||
|
||||
@@ -97,32 +19,9 @@ todo: can I support keycodes for saving in AyaNova and other shit that are the s
|
||||
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1514
|
||||
|
||||
|
||||
todo: back and forward buttons when running without browser controls in application mode?
|
||||
- wait and see on this one, as it will be likely outside of any particular form so not something to be baked in early necessarily
|
||||
|
||||
todo: GUIDED TOUR
|
||||
- This is an important feature and at least get a basic one in there for starters and initial release
|
||||
- This is a replacement for the tutorials and videos in v7 a
|
||||
- Need to add that auto-pilot thingy that allows for guided tours in HTML apps
|
||||
- Specifically it should at least have an ONBOARDING walk through of how to move around, enter data, get help etc. Not feature specific but usage specfic.
|
||||
- Later I'll add feature specfic tutorials like how to make a workorder etc
|
||||
|
||||
|
||||
|
||||
todo: clickable urls
|
||||
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1738
|
||||
|
||||
############### MAYBE STUFF OR STUFF ON HOLD / FUTURE ###############
|
||||
(If get here and not doing it put it into a v.next case where appropriate or spec doc for future reference or just ditch it)
|
||||
|
||||
|
||||
ON HOLD FROM EARLIER
|
||||
=-=-=-=-=-=-=-=-=-=-=-
|
||||
|
||||
todo: breaking change in latest vuetify with integer bound to v-text-field have kept this version awaiting fix, reported
|
||||
https://github.com/vuetifyjs/vuetify/pull/12451
|
||||
If not fixed in a timely manner can downgrade to the build before this one
|
||||
|
||||
todo: ON HOLD TIL LATER Lagging typing in name field on customize form for data grid filter
|
||||
Giving up on this for now, but noticed the following:
|
||||
No exceptions or errors just regular processing
|
||||
@@ -137,24 +36,10 @@ todo: ON HOLD TIL LATER Lagging typing in name field on customize form for data
|
||||
|
||||
|
||||
|
||||
todo: hide swagger logo and branding in api explorer
|
||||
Is this really that important?
|
||||
also, in the docs is a section specifically saying I should do something because I'm using newtonsoft json not microsoft built in
|
||||
https://github.com/domaindrivendev/Swashbuckle.AspNetCore#systemtextjson-stj-vs-newtonsoft
|
||||
https://github.com/domaindrivendev/Swashbuckle.AspNetCore
|
||||
|
||||
todo: service workers for monaco going in root of website folder, must be a config setting to move it into the proper place (not there)
|
||||
couldn't find anything about it, may need to post to ask, it's not the end of the world but kind of stupid looking as all the rest of the js is in subfolder
|
||||
https://github.com/microsoft/monaco-editor-webpack-plugin/issues/126
|
||||
awaiting reply, if nothing by the time I get here then delete and wait for email notification or if I care enough again to bother with it (cosmetic)
|
||||
|
||||
|
||||
|
||||
todo: consider feature to set server to always use a pre-set browser locale settings and not the ones in the browse itself
|
||||
Scenario is user in another country but needs to login and work with central server?
|
||||
server - wide
|
||||
User specific
|
||||
YAGNI / TTM?
|
||||
|
||||
|
||||
REPORTING bits and pieces
|
||||
- page breaks properly EXAMPLE NEEDED
|
||||
@@ -189,71 +74,9 @@ REPORTING bits and pieces
|
||||
|
||||
|
||||
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 6 - INSTALLER, LICENSING, ROCKFISH SUPPORT FOR RAVEN
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
|
||||
|
||||
|
||||
todo: WINDOWS INSTALLER
|
||||
Runner harness wrapper thing?
|
||||
even if windows only
|
||||
it could modify config since it's outside the server
|
||||
check for Postgres server extant and if not automatically start the standalone postgres instance
|
||||
manage postgres start and stop and configuration changes, sit in tray, run AyaNova server from there?
|
||||
|
||||
easy way to select command line params without resorting to editing text files for end user
|
||||
initially it's an installation option, but then need to edit after the fact
|
||||
Quick check of installers available still and is it still kosher to keep using INNO setup or is something better, more supported by windows etc?
|
||||
Wix if want MSI (some say that's desireable)
|
||||
INNO is still relevant
|
||||
I don't need hardly any requirements that can't just be copy or unzip deployed so maybe don't even need an installer for now?
|
||||
(zip distribution is going to be problematic with Windows file protection shit)
|
||||
https://docs.microsoft.com/en-us/dotnet/core/deploying/
|
||||
https://docs.microsoft.com/en-us/dotnet/core/rid-catalog
|
||||
|
||||
|
||||
Completely packaged and installable. REady for users to install as a test as I iterate stage 7 below
|
||||
All the stuff needed for someone to run it as a test without the real objects yet.
|
||||
Some kind of expiring license so they can't just keep using it as fucked as it may be some might do that
|
||||
I want short targetted testing only, not someone downloading and trying it out a month later, that's useless for us
|
||||
This needs to be focused on what I need to get from people about testing
|
||||
|
||||
|
||||
todo: LINUX INSTALLER
|
||||
Linux users don't mind doing the manual config thing as much, they're used to it and it could just be a shell file anyway
|
||||
So mainly this would be a documentation steps to install type issue
|
||||
|
||||
|
||||
todo: DOCUMENT DOCKER
|
||||
Present dockerfile maybe for docker installation with FILES folder pre-ready to build / run
|
||||
Whatever docker needs
|
||||
Or maybe private registry with docker images on our servers somewhere
|
||||
|
||||
todo: rockfish, can't do purchase for raven or view it I think
|
||||
Test a whole sales process from eval to purchase and make it work
|
||||
todo: rockfish, upgrade to latest bootstrap, out of date Currently
|
||||
todo: rockfish, trial license fetched On date not updating? (not showing in UI)
|
||||
|
||||
todo: Joyce rockfish notes:
|
||||
Licensing:
|
||||
noticed that the field "Fetched on" is NEVER updated.
|
||||
is it much to be able to see the TIME as well as the DATE, when "Requested" and when "Processed"?
|
||||
There are drop down selections NEW, APPROVED, REJECTED for the (already generated) listed keys. But can not actually save to a different Status. What is the purpose of the drop down options if can not select?
|
||||
|
||||
|
||||
|
||||
|
||||
todo: Discourse bootstrapping install
|
||||
look over, get ideas make case steal ideas profit FTW$
|
||||
https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md
|
||||
//here is their standalone config yml definition for DOCKER
|
||||
https://github.com/discourse/discourse_docker/blob/master/samples/standalone.yml
|
||||
|
||||
|
||||
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 7 - "REALITY"
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 6 - "REALITY"
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
All in on porting over all the real objects from v7
|
||||
|
||||
@@ -356,9 +179,12 @@ todo: Documentation
|
||||
|
||||
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 8 - EXTENSIONS (was plugins)
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 7 - EXTENSIONS (was plugins)
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
|
||||
Step 1: get the current active license count for all extensions so we know what we're dealing with here
|
||||
Step 2: which extensions in which order and some can be left off entirely?
|
||||
|
||||
Plan the order of criticality for extensions
|
||||
ACCOUNTING is obviously the first and foremost one and MUST be there for a lot of people to take up
|
||||
MUST be done in a way to support other alternative accounting apps that are coming around now like freshbooks or whatever it's called that Joyce is using now
|
||||
@@ -372,9 +198,86 @@ Plan the order of criticality for extensions
|
||||
which ones are porting and which are not
|
||||
Implement in order or priority
|
||||
Fuck peachtree?
|
||||
probably not, need to check again our install count of extensions
|
||||
|
||||
|
||||
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 8 - ONLINE EVALUATION ABILITY / INSTALLER, LICENSING, ROCKFISH SUPPORT FOR RAVEN
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
|
||||
todo: setup for automated trial testing ability so can just link users
|
||||
Maybe, rather than having seperate servers for testing, have it instead generate a User account on the fly for each user who wants to trial
|
||||
Automatically re-create the data on a cycle of some kind
|
||||
Needs warning message about being a shared instance of AyaNova so be careful what you type and also you may see things other people typed that we have no control over
|
||||
|
||||
todo: WINDOWS INSTALLER
|
||||
Runner harness wrapper thing?
|
||||
even if windows only
|
||||
it could modify config since it's outside the server
|
||||
check for Postgres server extant and if not automatically start the standalone postgres instance
|
||||
manage postgres start and stop and configuration changes, sit in tray, run AyaNova server from there?
|
||||
|
||||
easy way to select command line params without resorting to editing text files for end user
|
||||
initially it's an installation option, but then need to edit after the fact
|
||||
Quick check of installers available still and is it still kosher to keep using INNO setup or is something better, more supported by windows etc?
|
||||
Wix if want MSI (some say that's desireable)
|
||||
INNO is still relevant
|
||||
I don't need hardly any requirements that can't just be copy or unzip deployed so maybe don't even need an installer for now?
|
||||
(zip distribution is going to be problematic with Windows file protection shit)
|
||||
https://docs.microsoft.com/en-us/dotnet/core/deploying/
|
||||
https://docs.microsoft.com/en-us/dotnet/core/rid-catalog
|
||||
|
||||
|
||||
Completely packaged and installable. REady for users to install as a test as I iterate stage 7 below
|
||||
All the stuff needed for someone to run it as a test without the real objects yet.
|
||||
Some kind of expiring license so they can't just keep using it as fucked as it may be some might do that
|
||||
I want short targetted testing only, not someone downloading and trying it out a month later, that's useless for us
|
||||
This needs to be focused on what I need to get from people about testing
|
||||
|
||||
|
||||
todo: LINUX INSTALLER
|
||||
Linux users don't mind doing the manual config thing as much, they're used to it and it could just be a shell file anyway
|
||||
So mainly this would be a documentation steps to install type issue
|
||||
|
||||
|
||||
todo: DOCUMENT DOCKER
|
||||
Present dockerfile maybe for docker installation with FILES folder pre-ready to build / run
|
||||
Whatever docker needs
|
||||
Or maybe private registry with docker images on our servers somewhere
|
||||
|
||||
todo: rockfish, can't do purchase for raven or view it I think
|
||||
Test a whole sales process from eval to purchase and make it work
|
||||
todo: rockfish, upgrade to latest bootstrap, out of date Currently
|
||||
todo: rockfish, trial license fetched On date not updating? (not showing in UI)
|
||||
|
||||
todo: Joyce rockfish notes:
|
||||
Licensing:
|
||||
noticed that the field "Fetched on" is NEVER updated.
|
||||
is it much to be able to see the TIME as well as the DATE, when "Requested" and when "Processed"?
|
||||
There are drop down selections NEW, APPROVED, REJECTED for the (already generated) listed keys. But can not actually save to a different Status. What is the purpose of the drop down options if can not select?
|
||||
|
||||
|
||||
|
||||
|
||||
todo: Discourse bootstrapping install
|
||||
look over, get ideas make case steal ideas profit FTW$
|
||||
https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md
|
||||
//here is their standalone config yml definition for DOCKER
|
||||
https://github.com/discourse/discourse_docker/blob/master/samples/standalone.yml
|
||||
|
||||
|
||||
|
||||
todo: back and forward buttons when running without browser controls in application mode?
|
||||
- wait and see on this one, as it will be likely outside of any particular form so not something to be baked in early necessarily
|
||||
|
||||
todo: GUIDED TOUR
|
||||
- This is an important feature and at least get a basic one in there for starters and initial release
|
||||
- This is a replacement for the tutorials and videos in v7 a
|
||||
- Need to add that auto-pilot thingy that allows for guided tours in HTML apps
|
||||
- Specifically it should at least have an ONBOARDING walk through of how to move around, enter data, get help etc. Not feature specific but usage specfic.
|
||||
- Later I'll add feature specfic tutorials like how to make a workorder etc
|
||||
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 9 - RELEASE
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@ -409,12 +312,19 @@ Send a tip / donate to teh favicon generator guy
|
||||
Used it several times and should donate
|
||||
|
||||
|
||||
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 10 - ROCKFISH / HOSTING BACKEND SELF SERVER READINESS
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
DO server allocation, rockfish revamp to drive this part (or maybe it's an alternate app)
|
||||
https://blog.digitalocean.com/its-all-about-the-bandwidth-why-many-network-intensive-services-select-digitalocean-as-their-cloud/?utm_medium=email&utm_source=do_newsletter&utm_campaign=04292020
|
||||
https://www.youtube.com/watch?v=zZVoo5AbANI
|
||||
|
||||
|
||||
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
@@@@@@@@@@@@@@@ ROADMAP STAGE 11 - RELEASE SELF SERVE / HOSTING
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
Fall of 2020 hopefully
|
||||
links on website for sign up
|
||||
marketing can begin in earnest
|
||||
|
||||
Reference in New Issue
Block a user