Production installation on DigitalOcean about taiga-scripts HOT 11 CLOSED

I've run the script on a digital ocean box as deploy and everything seems to have gone smoothly (although my nginx files were overridden). When I try hitting my IP in the browser I get a Taiga error message. I'm not familiar with Python web development. How do I tail the logs? Is there a database migration I need to run first that wasn't listed in the documentation?

from taiga-scripts.

Hi!

The script is designed for run as user with sudo permissions (this lacks on the readme, sorry) and it has some assumptions for directories.

About the second question, I do not know that can really happens. You can find logs in the home of user used for run taiga-scripts. I'll try research that is can happens.

Thanks.

from taiga-scripts.

Hi @niwibe

My deploy user has sudo privileges. I'm retrying on a fresh VPS to see if it happens again.

from taiga-scripts.

I'm also trying to reproduce something similar.

from taiga-scripts.

Yep on a fresh install as deploy with sudo privileges, I ran bash setup-server.sh and navigated to [IP] and got the error.

Both the gunicorn and nginx error logs are empty but the access log is successfully logging requests.

from taiga-scripts.

Ok, thanks you! I'm currently working to fix this!

from taiga-scripts.

❤️

from taiga-scripts.

I just have merged the improvements branch and applied some fix to taiga-back. If you try again, it should work properly.

Additionally, I almost finished the taiga-vagrant refactor, that now uses taiga-scripts as provision scripts, and I will push the new version in few minuts.

from taiga-scripts.

I tried the script before you made this change but with a new user with sudo access and it worked perfectly. My issue has been solved but I think it was separate from pawel2105's.

from taiga-scripts.

I'll comment on #5 so you can close this ticket

from taiga-scripts.

Thank you very much to all!

from taiga-scripts.