Traq 4.0 testing

Traq 4 development discussion.
Post Reply
User avatar
Jack
Advanced Member
Posts: 666
Joined: Fri Mar 27, 2009 7:37 pm
Location: Australia

Traq 4.0 testing

Post by Jack » Fri Jan 01, 2016 11:27 pm

With the framework that Traq 4.0 uses now at a stage that I'm happy with, Traq 4.0 will be soon be hitting the beta stage.
 
But before any beta releases I'd like to do some alpha testing, anyone willing to help find any issues is welcome to do so. I will soon be releasing some alpha archives.
 
But until then to test Traq 4.0, checkout the master branch and install the dependencies.
 
You will need:
  • Git
  • Composer
  • Node
  • Gulp

Code: Select all

git clone https://github.com/nirix/traq.git
cd traq
composer install
cd dev
npm install
gulp compile
cd ..
(Note: some commands may be different on Windows)
 
Then direct your browser to the path you've cloned Traq to and run the installer and play around with it and report any issues you find in a reply to this topic.
Last edited by Jack on Fri Mar 11, 2016 9:20 pm, edited 1 time in total.

User avatar
visualsol
Newbie
Posts: 2
Joined: Fri Mar 11, 2016 2:20 am

Re: Traq 4.0 testing

Post by visualsol » Fri Mar 11, 2016 2:28 am

I tried and ran into a bit of trouble.  I did use "issues" as folder name instead of "traq" but I don't think that matters.
 
First, no bower.json:
 
<div>C:\xampp\htdocs\issues>bower install</div>
<div>bower                           ENOENT No bower.json present</div>
<div> </div>
<div>C:\xampp\htdocs\issues>git clone https://github.com/traq/dev_tools.gitdev </div>
<div>fatal: destination path 'dev' already exists and is not an empty directory.</div>
<div> </div>
<div>C:\xampp\htdocs\issues>cd dev</div>
<div> </div>
<div>C:\xampp\htdocs\issues\dev>bower install</div>
<div>bower                           ENOENT No bower.json present</div>
<div> </div>
<div>Then, some strange message despite being in command prompt as administrator:</div>
<div> </div>
<div>npm ERR! Windows_NT 10.0.10586                                                                                          npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"                                                                                                                   npm ERR! node v4.2.4                                                                                                    npm ERR! npm  v2.14.12                                                                                                  npm ERR! path C:\Users\bobl\AppData\Roaming\npm-cache\time-stamp\1.0.0\package\package.json.a20a99b2b084f1271bb0d4de259ae49b                                                                                                                    npm ERR! code EPERM                                                                                                     npm ERR! errno -4048                                                                                                    npm ERR! syscall rename                                                                                                                                                                                                                         npm ERR! Error: EPERM: operation not permitted, rename 'C:\Users\bobl\AppData\Roaming\npm-cache\time-stamp\1.0.0\package\package.json.a20a99b2b084f1271bb0d4de259ae49b' -> 'C:\Users\bobl\AppData\Roaming\npm-cache\time-stamp\1.0.0\package\package.json'                                                                                                              npm ERR!     at Error (native)                                                                                          npm ERR!  { [Error: EPERM: operation not permitted, rename 'C:\Users\bobl\AppData\Roaming\npm-cache\time-stamp\1.0.0\package\package.json.a20a99b2b084f1271bb0d4de259ae49b' -> 'C:\Users\bobl\AppData\Roaming\npm-cache\time-stamp\1.0.0\package\package.json']                                                                                                         npm ERR!   errno: -4048,                                                                                                npm ERR!   code: 'EPERM',                                                                                               npm ERR!   syscall: 'rename',                                                                                           npm ERR!   path: 'C:\\Users\\bobl\\AppData\\Roaming\\npm-cache\\time-stamp\\1.0.0\\package\\package.json.a20a99b2b084f1271bb0d4de259ae49b',                                                                                                     npm ERR!   dest: 'C:\\Users\\bobl\\AppData\\Roaming\\npm-cache\\time-stamp\\1.0.0\\package\\package.json',              npm ERR!   parent: 'fancy-log' }                                                                                        npm ERR!                                                                                                                npm ERR! Please try running this command again as root/Administrator.                                                                                                                                                                           npm ERR! Please include the following file with any support request:                                                    npm ERR!     C:\xampp\htdocs\issues\dev\npm-debug.log    </div>
<div> </div>
<div>And gulp js did not work....</div>
<div> </div>
<div>Thanks for your efforts!</div>
<div>Bob</div>

User avatar
visualsol
Newbie
Posts: 2
Joined: Fri Mar 11, 2016 2:20 am

Re: Traq 4.0 testing

Post by visualsol » Fri Mar 11, 2016 2:33 am

I did try "gulp compile" which worked.
But just see 
 
License Agreement
 
in the browser nothing else...
Last edited by visualsol on Fri Mar 11, 2016 2:34 am, edited 1 time in total.

User avatar
Jack
Advanced Member
Posts: 666
Joined: Fri Mar 27, 2009 7:37 pm
Location: Australia

Re: Traq 4.0 testing

Post by Jack » Fri Mar 11, 2016 9:17 pm

Whoops, I forgot to update the instructions in this topic. I've simplified the process a bit and less commands are required.
 
I've updated the instructions above to the new ones.
 
Sorry about that.

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests