ruby-hyperloop/chat

release 1.0.alpha1.4 current

Barrie Hadfield

@barriehadfield

So, I put some basic channel structure into the Slack group above. Also checked with the FaastRuby guys and they like using it a lot - lets use it for a few days and see if we want to jump ship

Barrie Hadfield

@barriehadfield

OK, enough from me for one day, promise this is my last post. I have added a few redirects to the website (inspired by FaastRuby):

https://hyperstack.org/question -> StackOverflow with all the right tags
https://hyperstack.org/slack-invite -> Invite someone to the Slack group
https://hyperstack.org/slack -> Our Slack group

Barrie Hadfield

@barriehadfield

Could not resist; one final redirect:
https://hyperstack.org/questions -> All hyperstack tagged questions

Michail!

@mpantel

Maybe its a good idea to jump over to also align names ruby-hyperloop/chat -> hyperstack-org which my cause some confusion for newcomers...

Michail!

@mpantel

@Siksel I use hyperstack with rails on docker and for my configuration i have set in config/environments/development.rb

 config.action_cable.allowed_request_origins = [
                                                 /https?\:\/\/127\.0\.0\.1\:[0-9]*/,
                                                 /https?\:\/\/localhost\:?[0-9]*/,
                                                 /https?\:\/\/0\.0\.0\.0\:?[0-9]*/,
                                                 /https?\:\/\/172\.18\..*\:?[0-9]*/]

  config.action_cable.url = (RUBY_PLATFORM =~ /darwin/ ? "ws://127.0.0.1:#{ENV['PORT']}/cable" : "wss://replace-with-docker-address/cable")

So you have to white list whatever docker serves it is not 0.0.0.0 anymore... but something like 172. or so

Siksel

@Siksel

@mpantel Docker is serving at 0.0.0.0:5000 for me (using foreman). It looks like https?\:\/\/0\.0\.0\.0\:?[0-9]*/ would cover that though

but even with that in there, I'm still getting the same error

Siksel

@Siksel

it looks like the error is actually coming from actionpack, not actioncable

20:17:31 web.1  | actionpack (5.2.3) lib/action_controller/metal/request_forgery_protection.rb:262:in `verify_same_origin_request'

Michail!

@mpantel

@Siksel are you exposing port 5000 from docker or mapping port 5000:5000 to your local machine? what is your foreman Profile look like?

can you verify in your browser what is the actual address at which requests hit...

use Web Developer tools and go to Network tab (in firefox for example) You can see there all your requests and which ones fail...

Forrest Chang

@fkchang

@barriehadfield why the interest in slack? What does it offer that gitter doesn't? Gitter always seemed to be a better fit for OSS from what I could tell

Siksel

@Siksel

@mpantel ugghh, I was exposing 3000 in my Dockerfile. Good call.

Still not getting live updates though

does yours update without a refresh?

Siksel

@Siksel

ahhh, I got it. I had to add EXPOSE 25222 to my dockerfile for the hot reloader to connect properly

Barrie Hadfield

@barriehadfield

Morning @fkchang reasons for Slack (INMO of course):

Gitter has stoped evolving. I know the founder very well (he worked for me for aboout 5 years) . He sold Gitter and lives a happy life in the mountains. The company that bought it is not evolving it.
Slack’s channel structure is very good and brings some order to a team - I know you can kindof do it in Gitter, but in Slack it is core to the app and works very well.
Slack is integrated with just about everything. @m-o-e has connected it to our StrackOverflow feed and we have connected it to Github already
Clever things like voting, time zone meting arranging and undreds of other add-ons
And the final killer feature - dancing parrots emojies ()how can you live without them)?

Come on over and give it a try: https://hyperstack.org/slack-invite

Michail!

@mpantel

@Siksel you meant hotreload... yes 25222 (is the default) should be exposed too...Docker is great but you have to be aware of those mappings. I had a hard time setting it up more than a year ago with hyperstack but didn't have a problem since then...

benburkle

@benburkle

@catmando Got my repo working! Comparing new hyperstack app to mine did the trick. I was missing app/assets/config/manifest.js, app/assets/javascripts/cable.js and added //= require rails-ujs, //= require activestorage, //= require turbolinks to app/assets/javascripts/application.js. Maybe that will help with install. Thank you for this project!

Barrie Hadfield

@barriehadfield

@/all looks like the Slack experiment is going very well and its a better place for us. If you havw not sdone so yet, come on over and exprience the joy of dancing parrots https://hyperstack.org/slack-invite

Barrie Hadfield

@barriehadfield

Dear traveller, if you find yourself here then please come and join us in our new shiny Slack community where you will find us more organized but just as chatty as ever.

Slack chat

So long Gitter, you have been a good friend to us, but it is time to say goodbye and hello to Slack as our main project platform.

First, join our Slack group here: https://hyperstack.org/slack-invite
Once you have joined, you can access Slack through the multi-platform app (you can add Hyperstack-org if you already use Slack for work) or if you prefer not to use the app, you can use your browser with a shortcut here: https://hyperstack.org/slack

StackOverflow

We are using SO for all technical Q&A now. Please feel free to also ask and discuss in the Slack chat, but we are trying to get as many good Q&A in SO as we can, so we might ask you to re-ask in SO as well. Our tag is hyperstack but we like to add the ruby-on-rails, ruby and react-js tags as well to bring the project to wider attention (please mention you are using Hyperstack and even add a link to the project if you can).