search

monty5811 / apostello

sms for your church
MIT License
60 stars 21 forks source link

new install issue #84

Closed losto closed 6 years ago

losto commented 6 years ago

It looks like the new firebase setup broke at least the digitalocean install...

from these instructions: https://apostello.readthedocs.io/en/latest/deploy_do.html

when doing this step: ./home/apostello/apostello-install/scripts/ansible_install.sh

I get this error: fatal: [127.0.0.1]: FAILED! => {"changed": false, "failed": true, "msg": "AnsibleUndefinedVariable: 'cm_server_key' is undefined"}

I then attempted to follow the ansible instructions and I found a config file that had those values set in /home/apostello/apostello-install/ansible/env_vars/example.yml which appears to have resolved the issue

losto commented 6 years ago

I thought I had it after the above, but still having an issue with default digital ocean install:

screen shot 2017-09-12 at 9 21 04 pm screen shot 2017-09-12 at 9 22 43 pm

screen shot 2017-09-12 at 9 21 10 pm screen shot 2017-09-12 at 9 21 14 pm

losto commented 6 years ago

BTW, this is all with V2.5.1 screen shot 2017-09-12 at 9 24 26 pm

losto commented 6 years ago

Just for kicks I also fired up a Herokuapp. Installed and got to first_run without any issues, however still having show stopping issue on the csrftoken, identical error to above:

Error: Ran into a Debug.crash in module Main This was caused by the case expression between lines 27 and 32. One of the branches ended with a crash and the following value got through: Err "Expecting a String at .settings.csrftoken but instead got: undefined" The message provided by the code author is: Try reloading the page Expecting a String at .settings.csrftoken but instead got: undefined

monty5811 commented 6 years ago

Thanks for the detailed report! It will be a few days before I can get round to fixing it...

monty5811 commented 6 years ago

Thanks again @losto - the error messages were very helpful.

The digital ocean install should be fixed now (by monty5811/apostello-do-install@3e6bca1208da8449ce27bb24a9d5e582c35ba90f). And the CSRF issue should also be resolved for both deployment methods in v2.5.3

I have just tested both methods and they are working. Please let me know if you run into any other issues. And thanks again for the detailed bug report.