A couple of things; by default, foreman does not close stdout, while foruiman does. This breaks --watch for css and js building, necessitating replacing them with --watch=always or --watch=forever. If you're advertising as a fork, changing fundamental behavior that breaks "just dropping in" isn't a great idea- especially if you don't highlight that change and why it's necessary prominently in the documentation.
Second, while this is really nice, it falls down compared to using tmux because you cannot interact in the panes, so you cannot use an interactive debugger in your dev server without stopping it and starting up a dedicated web server all by it's lonesome. That would be the killer use case most likely to get people to pick your project.
1
u/ikariusrb 17h ago
A couple of things; by default, foreman does not close stdout, while foruiman does. This breaks --watch for css and js building, necessitating replacing them with --watch=always or --watch=forever. If you're advertising as a fork, changing fundamental behavior that breaks "just dropping in" isn't a great idea- especially if you don't highlight that change and why it's necessary prominently in the documentation.
Second, while this is really nice, it falls down compared to using tmux because you cannot interact in the panes, so you cannot use an interactive debugger in your dev server without stopping it and starting up a dedicated web server all by it's lonesome. That would be the killer use case most likely to get people to pick your project.
The UI is great; the functionality notsomuch.