Fork me on GitHub
#pedestal
<
2016-03-19
>
lmergen19:03:15

hey guys, i'm interested in possibly refactoring an early stage api server away from ring, due to the lack of async support, and it feels a bit... chaotic

lmergen19:03:47

i see a great place for pedestal here, but my development environment is under windows, which i see is unsupported

lmergen19:03:06

what kind of level of "unsupported" is this? is it "it will not even compile"-unsupported, or "dont use it for production"-unsupported?

lmergen19:03:57

since we're already using vagrant, an option could be to run the entire dev environment in a vagrant box, but that would complicate the development process a lot i think

jonahbenton22:03:21

hey @lmergen pedestal ships with some ancillary .sh scripts, but there's nothing in the library that is OS specific.

lmergen22:03:26

ahhh so there's nothing to worry about really

lmergen22:03:32

that's great news

jonahbenton22:03:32

should not be

lmergen22:03:47

you should update the github Readme

jonahbenton22:03:28

yeah, agree, that should go into an issue

lmergen22:03:45

it kind of had me thinking it's currently not working. it should read something like "although we don't actively test it, it should work. blah blah"

jonahbenton22:03:18

yeah- there has been a flurry of activity in the repo recently, that would be good to clarify

lmergen22:03:53

i'll make sure to test it soon and if it works send in a PR for the Readme simple_smile

jonahbenton22:03:41

that would be great!

lmergen22:03:24

what's the recommended way to run pedestal, if i'm planning on doing some async work? is jetty9 already supported?

jonahbenton22:03:15

it's been a while since i've looked but you should be able to write async interceptors and use non-blocking io with any container.

jonahbenton22:03:46

and yes the jetty adapter pulls in jetty 9