Skip to content

Releases: KayXDev/Pagina-Web-MC

v1.0.1

09 Mar 13:33

Choose a tag to compare

🚀 v1.0.1 — Licensing & Documentation Update

✨ A stronger commercial-ready update for the project: mandatory license enforcement, cleaner release structure, and a more polished documentation flow for setup, troubleshooting, and deployment.


✅ Highlights

  • 🔐 Mandatory KayX license protection — the project now requires a valid license to run in both development and production
  • 🛡️ Startup + runtime enforcement — invalid or missing licenses can block boot and restrict protected routes / APIs
  • 🎨 Improved license flow UX — clearer invalid-license handling with a dedicated /licencia page and support direction
  • 📚 Documentation refresh — setup, troubleshooting, and license docs now better match the actual project flow
  • 🧭 README consistency preserved — companion docs were updated to match the same visual/documentation style

🧰 Deploy & Operations

  • 🖥️ Production startup protectednpm start now runs through the license-aware startup flow
  • ⚙️ Environment clarity improved — setup docs now better explain required variables, production config, uploads, email, payments, and cron
  • 🔎 Better diagnostics — troubleshooting guidance is clearer for license, auth, MongoDB, deploy, and runtime issues

📖 Documentation

  • 🧾 Setup guide improved — cleaner local + production onboarding
  • 🛠️ Troubleshooting expanded — more useful recovery steps for common failures
  • 🔑 License documentation simplified — focused on the important parts without unnecessary implementation detail
  • 📝 Changelog updated — release tracking kept in sync for v1.0.1

🔒 Licensing

  • 🚫 No redistribution — the code is no longer presented as open source
  • 🚫 No resale — the software may not be resold, sublicensed, shared, or repackaged
  • 🧷 Valid license required — usage is restricted to properly licensed customers only
  • 📄 Repository license updated — the project now uses a proprietary / all-rights-reserved license model

📌 Notes

  • Configure all production environment variables carefully before deployment
  • If the app does not boot or redirects to /licencia, review the license configuration first
  • This release is focused on project protection, documentation quality, and commercial-readiness

v1.0.0

26 Feb 21:16

Choose a tag to compare

🚀 v1.0.0 — Public Launch

✨ The first stable, public-ready release of the project: a solid Next.js foundation for a Minecraft network website, built with clean structure, key integrations, and practical documentation to keep deployments smooth.


✅ Highlights

  • 🧱 Next.js (App Router) production baseline — modern routing, SSR/CSR-ready structure
  • 📡 Minecraft widgets — server status + staff/admin presence modules
  • 🤝 Discord integration — support links + operational reporting/hooks
  • 🛒 Shop foundation — payments groundwork prepared (Stripe / PayPal)
  • 🌍 i18n support — cookie-based language selection (lang)

🛠️ Deploy & Operations

  • ⏱️ Vercel Cron updated to a daily schedule (Hobby plan compatible)
  • 🧯 Troubleshooting improved for the “blank page” dev issue (quick fix: clear .next)

📚 Documentation

  • 🧾 Setup guide + environment template (.env.example)
  • 🔎 Troubleshooting notes with fast recovery steps

🔐 Notes

  • Configure production environment variables in your hosting platform (e.g., Vercel) using .env.example as the reference.
  • If any credentials were ever exposed during development, rotate them before going fully live.