You've already forked Epicnabbo-Catalogus-Updated-Daily
Update readme.md
This commit is contained in:
@@ -16,14 +16,19 @@ EpicNabbo Catalogue v2 is a heavily optimized evolution of our catalog system, s
|
|||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 📈 Version Comparison
|
## 📈 Version Compression & Comparison
|
||||||
|
|
||||||
| Feature | Version 1 (Internal Build) | Version 2 (New) |
|
| Feature | Version 1 (Internal Build) | Version 2 (New Overhaul) |
|
||||||
| :--- | :--- | :--- |
|
| :--- | :--- | :--- |
|
||||||
| **Status** | Unreleased / Discontinued | **Active Development** 🛠️ |
|
| **Status** | Unreleased / Discontinued | **Active Development** 🛠️ |
|
||||||
|
| **Public Availability** | Never Released (Internal Prototype) | **Dev Preview (Open Source)** |
|
||||||
| **Production Ready** | No | ❌ **ABSOLUTELY NOT (Wipe Risk)** |
|
| **Production Ready** | No | ❌ **ABSOLUTELY NOT (Wipe Risk)** |
|
||||||
| **Catalog Size** | ~31,000 Items (Projected) | **52,000+ Items** 📦 |
|
| **Catalog Size** | ~31,000 Items (Projected) | **52,000+ Items (Massive Expansion)** 📦 |
|
||||||
| **Nitro v3 Support**| Partial | **100% Full Native Support** |
|
| **Nitro v3 Support**| Partial / Experimental | **100% Full Native Support** |
|
||||||
|
| **Stability Level** | Poor / Flawed Queries | **Critical Bugs (High Risk Layout)** |
|
||||||
|
| **Query Performance** | Slow Loading Speed | **Blazing Fast Optimized Indexing** |
|
||||||
|
| **Layout Integrity** | Missing pages & broken links | **100% Complete Verified Structure** |
|
||||||
|
| **Development Cost** | Free (Internal Time) | **100% Free Community Project** ❤️ |
|
||||||
| **ETA** | — | **No ETA (Under Construction)** |
|
| **ETA** | — | **No ETA (Under Construction)** |
|
||||||
|
|
||||||
---
|
---
|
||||||
@@ -56,3 +61,43 @@ To handle the 52k+ item dataset, ensure your database configuration is optimized
|
|||||||
```ini
|
```ini
|
||||||
[mysqld]
|
[mysqld]
|
||||||
max_allowed_packet = 64M
|
max_allowed_packet = 64M
|
||||||
|
|
||||||
|
💬 Frequently Asked Questions (FAQ)
|
||||||
|
Q: Can I get a sneak peek or test it on my live hotel?
|
||||||
|
|
||||||
|
A: Absolutely not. As stated above, it contains critical database-wiping bugs. Testing should only be done on an isolated local development environment.
|
||||||
|
|
||||||
|
Q: Can I help with development or fixing bugs?
|
||||||
|
|
||||||
|
A: If you are an experienced developer who understands Nitro v3 packet structures and advanced SQL indexing, feel free to submit a Merge Request.
|
||||||
|
|
||||||
|
Q: When will it be finished?
|
||||||
|
|
||||||
|
A: There is no ETA. We work on this for free in our spare time. It will be finished when it's perfect.
|
||||||
|
|
||||||
|
🤝 Contributing
|
||||||
|
We welcome contributions from the community, provided they meet our standards:
|
||||||
|
|
||||||
|
Fork the repository.
|
||||||
|
|
||||||
|
Create a clean branch for your bugfix (bugfix/resolve-wipe-issue).
|
||||||
|
|
||||||
|
Test your SQL queries thoroughly on MySQL 8.0+ / MariaDB 10.5+.
|
||||||
|
|
||||||
|
Open a Merge Request with a detailed explanation of what your code fixes.
|
||||||
|
|
||||||
|
🛠️ Development Roadmap
|
||||||
|
[x] Analyze v1 bottlenecks and establish superior base framework.
|
||||||
|
|
||||||
|
[x] Merge v1 catalog data into the new clean database structure.
|
||||||
|
|
||||||
|
[/] Expand and index database to 52,000+ items (In Progress).
|
||||||
|
|
||||||
|
[ ] Critical Fix: Resolve database-wipe vulnerability.
|
||||||
|
|
||||||
|
[ ] Systematic bug hunting and framework stability overhaul (Long-term).
|
||||||
|
|
||||||
|
[ ] Final QA testing and structural integrity verification.
|
||||||
|
|
||||||
|
⚖️ Legal Disclaimer
|
||||||
|
This is an open-source development preview provided "as-is" without any warranty of any kind. By downloading and importing these files, you assume full responsibility for any data loss, database corruption, or system instability. We are not liable for any damages caused by improper implementation or unpatched development bugs.
|
||||||
Reference in New Issue
Block a user