Raspberry Pi Migration Release

• Angular Upgrades, Go upgrades, various dependency updates
• Ensure Raspberry Pi works (trouble with v3 means we need Badger v2--consider migrating)
• authenticate echo history reads
• use docker to run
• provide an env var for setting a password for the initial admin
• various minor improvements to error checking and logging (viewing logs is still not great, requiring the docker logs command)

Encryption Release

Data is now encrypted at rest.Tokens are no longer revealed to the admin on the sessions page, and the echo and echo-history subdomains are now served out of the main binary. Additional changes:

• user primary key refactoring, use of Identity type
• allow multiple emails per user
• add registration (WIP), user verification (manual, will add SMTP in future)
• add defaults for configuration
• remove unused tenant-landlord features
• user deletion, lock, disable
• alphabetize shopping list, allow csv export and import, make mobile view fit better
• enable simple password login (needs some better error handling, 2-factor, etc)
• improved README
• generalize spa utility for multiple UIs
• finalize credential model (API and sync to current configuration still WIP)

Refactor of API and package arrangement

The API now uses Gorilla Mux in order to better accommodate routing with multiple domains and subdomains. Additionally, I moved the dwn package to a new core package and made oauth, core, and other packages more uniform with them all falling under a modules folder.

first deployment version in go with login

v0.1.0

update permission and readme for deployment

Go server with Badger for datastore and UI in new project

I decided to go back to Go to try out BadgerDb. Sessions are created when one logs in, but there isn't anything to do while logged in until I add a new API. The UI part of things is now available in a different project to keep things a bit cleaner.

Dotnet Core with Multiproject and Angular

I've added an Angular UI but not removed the MVC or connected the Angular to the API. Though the multi-project setup with .Net Core is very nice, I am still having trouble determining how to do migrations with EF Core when the data is a different project than the main application.

I'm considering moving this project back to Go to try out Badger... Moving this back and forth hasn't been especially productive, but at least I'm tagging releases so that both are useful.

v0.0.4: I am migrating to .Net (Core, yay!) because I want to take advantage …

…of Identity Framework and give another go (pun intended) at EF Core as well as the Individual Auth template from Microsoft. This initial commit is mostly templates put together. The MVC frontend is working but temporary. I intent to replace the UI with Angular for the next release.

v0.0.3: This is the Go repo, last deployment, with detailed notes on Nginx co…

…nfig, Systemd INI examples, and tips on commands for administration. This will probably prove to be a valuable reference even if I don't use the website itself in this format.

Functional non-Angular app

This deploy is the live DanWolf.net application with rendering done serverside via the html/template library instead of Angular.

Angular pre-operational release

This is a work in progress, but I am creating this release in order to tag the Angular version before I launch a temporary site using simple gohtml followed by eventually migrating to Rhyvu.