Closed eve-seat closed 9 years ago
Seems to have worked perfectly on a fresh vagrant vm.
Tested on a clean homestead box and worked a charm!
The seat:install command also worked on my current install after pulling the changes down.
This landed in the 0.11.0 release, but is not the official install path yet. I still have a few things to test and ponder about though. Thanks to those that have tested already!
Tested this on a server that did not have Redis installed. At that point in the installer it just loops, over and over again, asking for Redis details. Perhaps on the 2nd or 3rd attempt a prompt to 'kill' the process might be useful?
Yes, I know that you can CMD/CTRL + X, but something programmatic might be useful for non-savvy folks.
Hmm. Yeah it would do that. It wants Redis details pretty badly :D Redis is definitely a hard requirement for SeAT. What is the reasoning that Redis is not installed?
Just that I'm attempting it on a machine that doesn't (and for silly security reason can't) have it installed.
I'm not suggesting that Redis be removed as a requirement, just that after 3 failed attempts to connect, a message stating that Redis is required for SeAT, and ask if they would like to quit the install.
If Redis is not available for security reasons, is there even an option to use at least one of the other 3 queueing systems (besides that there are certain composer additional dependencies) ?
I personally tested SQS for some time and it was working.
@tfevens thanks for the clarification! Makes sense now and yea this is definitely possible.
@LunarchildEU as for supporting other backends, a few things like the jobID's that is returned when using Redis is heavily relied upon in SeAT. However, if we can get full test cases for other backends that work, by all means :D
@LunarchildEU By security, I mean that on my work PC I'm unable to install anything, so I'm not able to install Redis, and other requirements (or Vagrant & Virtualbox to roll a Homestead instance).
@eve-seat I haven't dove into the code, but with Laravel, shouldn't Redis, MemCached and other be quite easily swappable? Perhaps, that's something that can be reviewed and might go a long way to making SeAT more compatible with hosts. If I'm wrong, just ignore the ramblings and I'll move along :-)
You are 100% correct. We use Facade to interface with them and Laravel is nice enough to do the required translation. One of the many reasons why I chose Redis back then was the fact that its 1 dependency, and we have Caching and Queues sorted.
I am totally happy to entertain conversations about alternatives, but I would prefer to only focus on this post v1. For now, I will add your suggestion about failing the installer after say 3 attempts.
Thank for the feedback @tfevens =)
My pleasure! Hopefully I'll be able to contribute some code to the project! It's these kinds of things that make me want to play Eve again!
@tfevens great news : D Feel free to come join us on IRC too :) Details at the bottom of the repo root page.
f5fb0c88 introduces a installer for SeAT. The basic idea will be that a user will install seat via composer and run the installer after that.
Please could I get a few to test the current version and report bugs as applicable?
A sample run will be:
Once it is installed, run the installer with: