search

openfoodfacts / openfoodfacts-infrastructure

Where we collaboratively plan and maintain the infrastructure of Open Food Facts
3 stars 6 forks source link

Deploy slackin (Slack auto-invite) somewhere else than heroku #429

Open stephanegigandet opened 7 years ago

stephanegigandet commented 7 years ago

We currently use slackin so that users can auto-invite their email address to Slack:

https://github.com/rauchg/slackin

It is deployed on a free node on heroku, but we have too much trafic:

"You have used all of your 550 Free Dyno hours for February 2017.

After August 1st, 2016, if you exceed your quota, all of your free dynos will sleep until the beginning of the following month."

I'm going to try to deploy it somewhere else, there are lots of other options on the slackin doc.

stephanegigandet commented 7 years ago

Trying Now:

https://now-examples-slackin-gprejxkrhj.now.sh

teolemon commented 7 years ago

url needs to be updated

nicolasleger commented 6 years ago

URL in footer on OFF is still wrong and returning an error https://slack-ssl-openfoodfacts.herokuapp.com/

CloCkWeRX commented 6 years ago

That URL (https://slack-ssl-openfoodfacts.herokuapp.com/) also seems to account for about 40% of the page load time across 2-3 calls (total: 4s / 10s load time)

screen shot 2018-01-04 at 12 38 25 am

While it doesn't block the edit UI, it does make it a lot slower when doing bulk editing in multiple tabs.

teolemon commented 5 years ago

fixed @stephanegigandet ?

VaiTon commented 4 years ago

@stephanegigandet i see now.sh as a good option. We could even use the dev server.