https://linen.dev logo
Join Slack
Powered by
This message was deleted.
# papercups
s
This message was deleted.
a
haha glad you found it πŸ˜‰
o
Basically, we currently have the "slack-in" hack allowing "guests" to come on a public slack channel. But that is ugly. And papercups seems like an interesting base to implement something cleaner ... Allow a fluent interaction with slack .. while having much more control (and potentially more user-friendly)... Oh found the issue πŸ™‚ https://github.com/papercups-io/papercups/projects/5
u
interesting, we currently have an integration that allows syncing slack channels with our papercups dashboard (i'm actually replying to your from our dashboard right now) but that feature is currently in beta -- happy to get you set up with it if it's interesting to you though!
o
Basic the idea is to expand on your widget with the option of being many-to-many .. while still allowing for a degree of control ... and having this "self-hostable" could be a huge plus from a compliance perspective ..
(for the moment I am battling with prod.exs vs runtimes.exs .. for whatever reason it is ignoring 
USE_IP_V6=false
my Elixir is very rusty) ..
a
ah yes we've been trying to migrate more of our config variables into runtime.exs rather than prod.exs -- sorry for the confusion πŸ˜…
it might be easier to hop on a quick call to learn more about your use case if you want to put something on my calendar? https://calendly.com/alex-reichert/30min?back=1
o
With pleasure ..
a
sounds good!
o
Ooh .. you seem to have 
socket_opts
vs 
socket_options
.. in runtime.exs?
a
o
yup .. ? could it be this .. again .. very rusty ..
u
hmm that could be wrong, can you try changing it to see if it fixes it?
o
yeah .. testing currently ..
At any rate looks like an error .. because I can't see it set anywhere else ... so even if it doesn't solve my issue ...
(I'll to a proper PR if I can qualify it..) - it would be fun being able to deploy it .. though I am really not supposed to be spending that much time on hackery ...
Oh Victory !
a
currently 
socket_options
are set here https://github.com/papercups-io/papercups/blob/master/config/runtime.exs#L46 if that's what you mean? but you're probably right that both should use that variable
o
a
were you able to fix it? πŸ™
o
yes .. that seems to be the issue ...
a
nice! if you don't mind opening a PR, that would be amazing πŸ™‚
were you able to get the db set up and migrated as well?
o
the ecto migration seems to have passed correctly .. I am unsure about setting up a first user though ...
a
hmm are you seeing any errors in the logs?
o
yes .. ** (File.Error) could not write to file "/app/_build/prod/rel/papercups/lib/tzdata-1.0.5/priv/latest_remote_poll.txt": read-only file system
This is running on a read-only file-system ...
u
oh strange...
o
OK red herring ..
This is just 
** (ArgumentError) conn.secret_key_base has to be at least 64 bytes
u
hmm one sec
o
I'll correct ...
This is on my side.
u
can you try running 
mix phx.gen.secret
and then setting your 
SECRET_KEY_BASE
environment variable to that value?
o
I am using the entropy source I have on my system .. (which would be better than 
mix phx.gen.secret
.. for "reasons" .. I simply need to grab more entropy πŸ™‚ )
a
sounds good πŸ˜›
o
The only problem .. is that I don't have good caching setup for the react/webpack build .. so this is taking forever to rebuild (like 9 minutes) ...
BTW .. you seem to be on Heroku ... out of interest ... how long does the build take there for your app ?
a
ah yeah, it also takes about 10 mins πŸ˜•
o
OK So at least I don't need to be ashamed ... I have no experience with elixir/erlang on Heroku ..
At a minimum .. i'll be able to add a "deploy on.... " button to your collection ..
a
what are you using to deploy? platformsh?
o
Yup ..
(and this is meta ... again .. this would be for platform.sh ..)
a
haha yup, very cool!
o
... and I am in πŸ™‚
BTW I really love your 
functions
.. we have something very similar with an embedded node vm to allow us to do "integrated zapier" ...
a
nice! πŸŽ‰
yeah unfortunately the 
functions
won't work on self-hosted deployments at the moment, unless you do a bunch of additional setup with AWS 😬 but happy to help with that if you're interested
o
Hmm . oh you are not running them yourselves .. you are putting them on lambda ?
Maybe I'll tell you how we go about it πŸ™‚ ...
a
yup, we're just using lambda
would love to know how you guys go about it!
o
Also .. I'll try to find some time to do a proper PR for a "deploy to platform.sh" button https://github.com/OriPekelman/papercups/commit/a0ed9992d57c14fa2cc1029d1c15f5a18470c39d (the contentious part would be 
build_embedded
in mix.exs ... ) ..
a
interesting... i would need to understand what that's doing a little better
o
Yeah evidently .. (these are basically the configuration files needed to run this on platform.sh .. they don't 
need
to be in the upstream .. though it does make life easier). And currently they are .. well, a bit verbose .. because I am doing a lot of caching in the build hook - because I hate sssslow builds.
u
haha yeah makes sense πŸ™‚
o
Anyway that is a different discussion ... at any rate you should now that "papercups" is now officialy supported on Platform.sh ... πŸ™‚
a
amazing! thanks for that πŸš€
o
See you on Wednesday ... back to my day job ...
u
Sounds good!
4 Views
Open in Slack
PreviousNext
Powered by