Closed acs closed 10 years ago
I've just merged to master (and stable) this PR https://github.com/taigaio/taiga-front/pull/163 that should fix this problem.
Could you please try the following?
vagrant ssh
cd taiga-front
git pull
npm install
gulp deploy
Checking ...
cd taiga-front
git pull
You are not currently on a branch. Please specify which
git branch
* (detached from 1.1.1)
This is the default config creating the vagrant env. I move to master ...
git checkout master
git pull
npm install
gulp deploy
...
[07:42:45] Finished 'styles-watch' after 120 ms
time to test:
Now it is working, great! login also works and now I am with admin role inside Taiga.
Just pending why taiga-front was not in master branch but in detached state.
It goes to a detached state because the script sets the branch to one of the release tags we have.
It's correct if you move to master or stable. I think we should change taiga-scripts for just moving to stable branch.
Thanks! ;)
After doing in Ubuntu 14.04:
acs@bitboy:~/devel/taiga$ git clone https://github.com/taigaio/taiga-vagrant.git acs@bitboy:~/devel/taiga$ cd taiga-vagrant acs@bitboy:~/devel/taiga/taiga-vagrant$ vagrant up ... (several minutes) ... Setting up nginx-full (1.4.6-1ubuntu3.1) ... Processing triggers for libc-bin (2.19-0ubuntu6.3) ...
when I try to access http://localhost:8000/ a blank screen is shown. Taking a look to JS console: