react is surely not going anywhere anytime soon though ;)
i think every framework has its flustrations, :-) ember has been awesome, time to try something new now... :-)
ow sails, ill miss you <3
yea we’ll see how it goes with them. trails looks like it’s got potential. I like that their aiming at doing plugin-able backend ‘engines'
the only one feature i love in sails-sane/seeds
blueprints in json-api rest and waterline offcourse
yea @jamemackson backend engines as in i can use hapi/express4/whatever right?
that’s the idea
react and hapi is what i'm onto right now
yea @mgenev :-D most stable stack
hopefully i get to open source my stuff soon
i keep being given apps to make instead
but i just turned in a job description which includes open sourcing our framework and maintaining it
anyone heard from @Globegitter in a while?
that would be awesome if you could share some of what you’ve been doing! I haven’t talked to him in a while
i havent seen @Globegitter anywhere on github recently. @mgenev what do you have ?:-)
we're making a pretty crazy system for media publication
soa and web components
how can i configure Canoscan lide 120 in fedora 20?
@BransonGitomeh I get the impression he's been pretty busy-- last I talked to him he was talking grad school
Re the whole debacle this past month about Sails: I've avoided commenting publicly out of respect for the people involved, but I was finally forced to post an update in the GitHub issue where the nastiness originally started.
Saw a little of that a little while back
Sorry about the confusion-- I should have clarified what was going on immediately instead of waiting. Sails is more active than it has ever been, and is currently in use at Verizon, Microsoft, IBM, and others. It runs the website for the city of Paris and is use internally by 18F, a US governmental agency. The same core team is maintaining Sails (myself and members that were gradually added over the past four years), we are using Sails in production at Treeline, and our mission is unchanged: to make it easier and more productive for developers like ourselves to build backend applications.
If anyone has any questions about our team, the history, where we're going, or our mission, please reach out to me directly at email@example.com.
thanks for the update @mikermcneil, we appreciate hearing that and will continue to watch things progress with Sails.
@BransonGitomeh, @Globegitter took a new position that hasn’t allowed him the time (as best I understand) to continue working on sane. There are a handful of us that have talked about continueing to grow and maintain sane but I know for myself I’ve been so wrapped up with other things that it has been tough to get to sadly. My situation will open up in another month or so, so hopefully we’ll see some momentum again around here soon-ish ;)
Anybody have any tips on the best way to move a current sane project to a docker container?
thanks! @mikermcneil I actually got the interview with them, but let it pass, because by the time they contacted me I took a job really like at Time Inc
CBC CBC, ,
Just noticed in the discussion above that some people are favouring hapi over sails.. only just bumped into the SANE stack and originally from a MS background trying to go full stack JS ... is SANE an option or should i be looking elsewhere ?
@mikermcneil I would really love a beta invite to treeline!!
Feeling a bit crazy trying to get websockets to work. I was able get a similar setup to https://github.com/jamemackson/example-sane-realtime working locally but now i'm trying to connect to the production sails server and it's not even trying to hit the server. Setting the host works for the normal http rest requests but even setting io.socket.url = 'wss://myserver.com' explicitly doesn't seem to work. Does anyone have websockets rocking in a production environment? Thanks!
This message was deleted
Does anyone have any insight as to how/where the session.user is set?
Ok never seen this before
I have an error when I start the server events.js:72 throw er; // Unhandled 'error' event ^ Error: spawn ENOENT at errnoException (child_process.js:1011:11) at Process.ChildProcess._handle.onexit(child_process.js:802:34) I have never seen this before I am using Ubuntu 14.04 lts everything looks to be installed correctly I managed to start a new project with sane new blah -d mongo but the server will not start using sane up
@Sibkis logout and log back in
of the OS
people, how could I serve my ember app in the / route in sails?
ember build --output-path=path/to/sails/assets/folder
or seeds build handles that with versioning as well now
@robbyoconnor this project has been at a bit of a standstill for a while now. There is a group of us that have discussed picking things up here however not much traction has been made in that direction. I’ve had some other projects demanding my attention that have prevented me from personally doing much and I suspect the others have been in a similar boat. I really hope that changes soon. @jhliberty has been working on a very similar project http://seedsjs.com/ that doesn’t have exactly the same functionality as sane (no docker stuff built in) but that project has been getting more love and affection as of late and is worth a look.
It's a shame :( It looks like a great product
yea it is. But don’t lose all hope :) My workload is moving back in this direction so I’m hoping that we can find our way back on track here before too long. And thanks for #206, I’ll take a closer look at that later tonight - the dep’s have been badly in need of updating :)