Skip to content

mehrancodes/laravel-harbor

Repository files navigation

Actions Status

logo-harbor

Laravel Harbor (formerly Veyoze)

On-Demand Laravel Forge deployments with all setup you need

🚀 Update (February 25, 2024): Repository Name Change

We have officially changed the repository name from "Veyoze" to "Laravel Harbor." The new repository URL is now:

composer require mehrancodes/laravel-harbor

Please update your references and links accordingly.

Table of Contents

Introduction

In today's fast-paced software development world, the ability to quickly and efficiently test new features is a game-changer for teams aiming to maintain a competitive edge. Preview Environments serve as the critical testing grounds for new features, bug fixes, and updates before they are integrated into the main codebase. These environments are crafted on-demand to validate specific git branches, providing a transient yet powerful platform for thorough pre-merge testing.

"Don't merge until you preview" - with Laravel Harbor, ensure that excellence is the standard, not the exception.

Documentation, and Usage Instructions

See the documentation for detailed installation and usage instructions.

Contributing

We welcome contributions! Please see our CONTRIBUTING.md for details on how to contribute and the process for submitting pull requests.

License

This project is licensed under the MIT License - see the LICENSE.md file for details.

Roadmap

As this CLI tool has been crafted as an MVP and has undergone real-world testing, we're now focusing on enhancing its robustness and expanding its capabilities. Here's what's on our radar:

  • 🛠️ Enhanced Error Handling: Aiming for comprehensive error handling throughout the entire CLI process to ensure smooth user experiences.

  • 📘 Expanded Documentation: We'll be adding more examples showcasing the tool's versatility, such as:

    • Using Laravel as an API backend with Nuxt.js on the frontend for SSR handling.
    • Using with projects like WordPress and more.
  • 🧪 Testing: Preparing unit tests and feature tests to ensure the tool's reliability and stability.