ConsulBot on i18n_master
New translations activerecord.y… (compare)
ConsulBot on i18n_master
New translations activerecord.y… (compare)
javierm on master
Allow search User through email… Allow search User through name … Reduce the number of specs line… and 2 more (compare)
javierm on user_search
javierm on visit_after_setup
Remove redundant setting resets… Reduce number of requests in da… Remove redundant request in bal… and 4 more (compare)
javierm on visit_after_setup
Create admin user before starti… Remove redundant setting resets… Reduce number of requests in da… and 5 more (compare)
javierm on master
Avoid a brakeman security warni… Make sure users can only delete… Expire cache when users follow/… and 1 more (compare)
javierm on fix_follow_cache
Hi @jinto-thomas, glad to see that you have found the hashicorp-consul project!
Hi @tenfortyeight, probably you are looking for the https://gitter.im/hashicorp-consul/Lobby project.
Hola @AytoPonferrada, disculpa por la espera 🙏🏼, se me debió pasar la notificación.
Sigues teniendo el mismo problema? Veo que vuestro fork debe ser: https://github.com/AytoPonferrada/consul. Y que estáis usando la versión v0.19 de Consul. ¿Correcto?
Así de primeras me da la impresión que algún detalle de configuración de capistrano no está correcto lo que impide que puedas reiniciar la aplicación. El envio de emails debería funcionar con cualquier cuenta de correo que permita conexiones SMTP. Pero claro si después de cambiar las credenciales SMTP en el archivo de secrets no puedes reiniciar la aplicación estas credenciales no se cargan ya que los secrets se cargan una sola vez al arrancar la aplicación.
Si quieres tenemos un espacio de trabajo en Slack donde resolvemos preguntas técnicas y ayudamos a solucionar problemas que puedan tener los forks de Consul (https://consul.slack.com/), allí tenemos un canal llamado #tech-questions donde muchas veces hay respuestas a problemas comunes. Quizás podrás unirte allí donde podemos tener una conversación más ágil y darnos más detalles de vuestra configuración.
Hola @ernestogarj , disculpa por la espera🙏🏼
¿Conseguiste arreglar el problema de configuración de tu correo electrónico? Si sigues teniéndolo y para ayudarte mejor me vendría bien que me respondieras a unas preguntas:
Hello Community,
I'm know nothing about ruby and I'm a noob in app development. I've created a deployment on a production server for my fork and started configuring the smtp with sendgrid (tried also with mailgun). I'm adding my sendgrid credentials to the secrets.yml, then restarting the prod server, and registering a new account, I land on the "Confirm your email address" page, but I receive no email. It seems that my app doesn't work.
Also even before configuring the smtp credentials I landed on the "Confirm your email address" page and not the Error 500 one.
Anyone for a help ?
Hi @bidHimArm, thanks for trying Consul.
Did you look for lost emails at spam folder? Probably you have to whitelabel your smtp configuration to send emails from your domain through Sendgrid or MailGun servers.
Here is an article that will help you to whitelabel your Sendgrid configuration so your application emails are not considered as spam.
https://sendgrid.com/docs/glossary/whitelabel/
We have a Slack channel for technical questions where you would find answers for the most common problems. Past week other user had the same problem you have so probably you can get useful feedback if you decide to join. If you are interested in joining please send me an email address through a private message. 🤗
Hi @rashmiagar 👋, you can run Consul in Heroku but Heroku does not allow to store uploaded files on their own servers, you have to use an external storage for uploaded files like AWS S3 service.
You can use Heroku as production environment but there is no need to use Consul installer there. You are doing ok by doing it manually.
Multitenant is not a feature implemented yet but i think there is some people working on it, but not sure when it would be ready and included in a new Consul release. Here [1] is a starter pull request in this direction, maybe you can give it a 👍🏼.
Regarding the Timeout error, it would be helpful if you paste a more extense log from heroku. You can get it by running heroku logs
from the command line. Which page is throwing this error?