Goals

1. Aid the average civilian consumer in making decisions for their Loadouts.
2. Make sourcing hard to find materials easier by scanning TacSwap, Gunbroker and others
3. Prevent accidental "violations" to keep civilians safe as possible from tyranny.
4. ...

When putting your build together, you’ll need to decide on the following parts:

Caliber, barrel length, purpose?
Brace or stock?
Do you want your brace or stock to fold?
Ratcheting castle nut or staked castle nut?
What upper and lower receiver do you want?
Which trigger do you want or require?
Is your lower parts kit Mil-Spec or upgraded?
BCG.
Charging Handle (rear charging or side charging?).
Handguard preference?
Muzzle device?
Optics/Sights?
Pistol Grips/Foregrips
Barrel Takedown or Breakdown Kits
Cerakote choice (optional)

Upgrading the app to a Desktop App

For Issues with SDKs or Runtimes not running, try this:

https://github.com/theolivenbaum/Electron.NET/

Or, try this:

https://github.com/ElectronNET/Electron.NET/issues/704

Knowledge Transfer

This custom web Stack aims to do two things: Maximize the use of HTMX and make UI much easier and more fun to work with in the emerging dotnet core Linux era.

I. Essentially, I'm supporting the generation of HTML directly from as many backends or API's as possible, without needing Javascript Framework or complicated squeaky toys like Microsoft's Blazor.

Just simple, old-school HTML, CSS and the occasional line of Javascript or C#.

II. On the backend side of things, I've added support for .sql and .cypher files as first class citizens. They can be easily imported by name, or even mapped to Razor CRUD functions by name. This makes the following 3 sample codefiles incredibly easy to maintain for all team members of all types:

-- Gets all Parts with Colt as the manufacturer:
SELECT * FROM mynugsdatabase.Parts part
WHERE part.Manufacturer LIKE '%Colt%'
-- .. etc.

# A specific User (node) is updated to "Like" a particular Build (another node), thereby forming a direct relationship which can be queried.  

# Returns BOTH the build liked and the User as JSON.
MERGE (user1:User { name: $userName })
MERGE (build1:Build { name: $buildName })
MERGE (user1)-[:LIKES]->(build1)
RETURN user1, build1

TODOS

https://github.com/chartjs/awesome

• [x] Update DotEnv for easy keying and mapping to T.
• [x] Find or write a good Modal that can be called up anytime.
• [ ] Import Builds from csv, and save to nugs.db (sqlite)
• [ ] Have the globalexceptionhandler log locally.
• [ ] Have the globalexceptionhandler log to Nugs.db.
• [ ] Write update query for scraped images to nugs db.
• [ ] Save your CSV Parts to a Neo4j db instance.
• [ ] implement and Test the logs bulk insert.
• [ ] Trigger the modal when an exception occurs.

Ideas

• [ ] Idea: Write a bootstrap method for local neo4j Docker image.
• [ ] Idea: Write a Sqlite3 Insights service for displaying table counts, stats, etc.
• [ ] Scrape any url and find tables; Break down the tables by headers, and suggest/create models from them? Maybe preview them in a daisyui table? :)
• [ ]

Issues

Stack

Frontend

Htmx Hydro/Alpine.js AlpineJS tags DaisyUI TailwindCSS

Server/Backend/HTML generator

ASP.NET Razor Pages

Backend

Anything, really, but mainly:

[Neo4j]() - For mapping complex relationships that SQL cannot easily model or efficiently query. [MySQL]() - For ubiquitousness and ease of use. [Sqlite3]() - For local/mobile storage. [Pocketbase]() - For private uses.

Devops

Railway.