changing conf.json when using taiga-front-dist

332 views
Skip to first unread message

ela...@gmail.com

unread,
Aug 1, 2016, 10:40:43 AM8/1/16
to taigaio
I might missed something, but when following the production frontend installation guide when changing the conf.json to have an external api url (https://domain.com/api/v1) the file in dist/v-1468840853868/js/app-loader.js stays the same.
Then when trying to load the frontend it tries to load the "discover" api using localhost.
As far as I understand I need to regenerate the front using the generate script, but then there are lots of missing libraries in the package.json.

When I manually updated the app-loader.js file to the external URL - everything works fine.

What's the right method of doing this?

Thanks

Alejandro Alonso

unread,
Aug 2, 2016, 1:03:54 AM8/2/16
to ela...@gmail.com, taigaio
Hello, 

You shouldn't update your app-loader.js file, just your conf.json. If you updated it properly, are you sure you don't have any error on the json file? (if it's happening your browser console should say something about it). You should also check your conf.json file is accesible, for example in tree.taiga.iohttps://tree.taiga.io/conf.json

Regards,

--
Please help us keep the Taiga.io Community open and inclusive, follow our Code of Conduct:
https://github.com/taigaio/code-of-conduct/blob/master/CODE_OF_CONDUCT.md
---
You received this message because you are subscribed to the Google Groups "taigaio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to taigaio+u...@googlegroups.com.
To post to this group, send email to tai...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/5dcc6b1c-8ee0-448f-9657-320a3c61b4ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

  
Alejandro Alonso Fernández
CIO & Co-founder
www.kaleidos.net/FC8EAC/
Reply all
Reply to author
Forward
0 new messages