5ad8e76760
- lot summaries on map edit - link to create lot from map edit - more info on map search - include lots and occupant on work order search - include map name where work orders are shown - more work order search filters - add cogs to admin dashboard icons - fix read only bug getting fee categories |
||
|---|---|---|
| .github | ||
| assets/css | ||
| bin | ||
| cypress | ||
| data | ||
| docs | ||
| handlers | ||
| helpers | ||
| public | ||
| public-scss | ||
| public-typescript | ||
| routes | ||
| temp | ||
| test | ||
| types | ||
| views | ||
| .atomignore | ||
| .codeclimate.yml | ||
| .eslintignore | ||
| .eslintrc.json | ||
| .gitignore | ||
| .ncurc.json | ||
| .prettierignore | ||
| .prettierrc.json | ||
| .sass-lint.yml | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| SECURITY.md | ||
| _config.yml | ||
| app.d.ts | ||
| app.js | ||
| app.ts | ||
| cypress.config.d.ts | ||
| cypress.config.js | ||
| cypress.config.ts | ||
| gulpfile.d.ts | ||
| gulpfile.js | ||
| gulpfile.ts | ||
| nodemon.json | ||
| package-lock.json | ||
| package.json | ||
| tsconfig.json | ||
| version.js | ||
| windowsService-install.bat | ||
| windowsService-install.d.ts | ||
| windowsService-install.js | ||
| windowsService-install.ts | ||
| windowsService-uninstall.bat | ||
| windowsService-uninstall.d.ts | ||
| windowsService-uninstall.js | ||
| windowsService-uninstall.ts | ||
| windowsService.d.ts | ||
| windowsService.js | ||
| windowsService.ts | ||
README.md
Lot Occupancy System
In development
A system for managing the occupancy of lots.
Built with cemetery management in mind, but flexible enough to handle marinas and campgrounds as well.
User Documentation (In The Works)
Key Features
Maps are optional!
Many systems of this type start with a map, and drill down into the data from it.
This can result in a huge amount of effort to get started.
This system can run "out-of-the-box" without maps, with the option to add them when it makes sense.
About this Project
Although the system is quite niche, it's being released in an open source environment in hopes to pool developer resources from other municipalities looking to move away from older, legacy systems.
It is being shared to start the dialog among other municipalities and present an option to those who may be looking to refresh their own cemetery systems.