-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: Include Mailpit Configuration for New PHP Versions #954
Comments
Laragonzo already has something like this. |
upvote for Laragonzo |
I too recommend Laragonzo, and at present I say this as a long term recommendation, though I wish and hope that @leokhoa will come to his senses and change his pricing so that we can end up having a single Laragon based distribution again rather than a competing fork. |
he can go for similar pricing (& ecosystem) like mamp laragon base features are completely free ( as promised in FAQ ) Also i really like the xamp's ( cloud ) production environment and licensing clarity |
This is not really the discussion topic for my response, but I am posting it here anyway:
If he partners with the enthusiastic community and focuses his own time on enabling this cooperative development and on developing functionality that only he can write, IMO Laragon can become extremely competitive within months, but unless he converts his existing user base to cheap paid licenses to give him early revenues, and unless he partners with the community to make rapid progress and become competitive to keep revenues flowing, and unless he keeps the free PR these users generate, he will simply NOT be able to compete. |
Hello @leokhoa
I noticed that every time I add a new version of PHP to Laragon, I need to manually configure Mailpit. This process can be repetitive and time-consuming.
Would it be possible to include Mailpit as a built-in feature in Laragon? For instance, pre-configuring Mailpit or providing an option to auto-configure it when adding a new PHP version would greatly enhance the user experience.
Thank you for considering this suggestion, and I appreciate the excellent work you’ve done with Laragon!
Best regards,
The text was updated successfully, but these errors were encountered: