I want in my Project to use vue.js Admin panel
so i choose this
https://github.com/misterGF/CoPilot
when i run project throw cmd > npm run dev
its work perfect throw : localhost:8080
But i need to upload the admin panel to hosting server (live)
so before i upload it
i run > npm run build
and upload it
but its not work correct when i open mydomain.com
its give me blank page
even in local if i try to open project like :
http://localhost/CoPilot
assume i put admin panel code in wamp/www/CoPilot
its also give me blank page
do i forget any step ?
why its only run throw localhost:8080
thank you
In file config/index.js, change the port.
Related
I am trying to integrate with WOPI online through the Office Cloud Storage Program Partner Program
To do that integration, you have to use the validation application URL by using .wopitest file. It was working fine before but today it gives me 404 Not Found
My Testing URL: https://ffc-onenote.officeapps.live.com/hosting/WopiTestFrame.aspx?ui=en-US&rs=en-US&dchat=1&hid=951a6eb2-6cd8-4c6d-9258-95f2d420b241&sc=746e9e3b-8a2e-4bc1-810c-01ce605911d1&wopisrc=https://<-myRestAPIURL->/wopi/files/1051&IsLicensedUser=edit&testcategory=All
Is there anyone having the same issue or it is an implementation issue?
Note: for word documents, it is working but I need to run the full test for other issues
It still not working but you can run the validation locally. Here are the steps on windows:
Make sure you have at least.net core 2.2.1
Download the validator project from github https://github.com/Microsoft/wopi-validator-core
Rebuild the project and open the command line
Navigate to the bin folder netcoreapp2.0 folder
Run the command dotnet run --project
./src/WopiValidator/WopiValidator.csproj --framework netcoreapp2.0
-- -t MyAccessToken -l 0 -w http://localhost:5000/wopi/files/1 -e OfficeOnline -s
Note:
Provide a valid access token and your WOPI REST end point URL
Maybe you will need to disable the Proofkeys validation on your end point to make it run
All steps mentioned on the project home page at github
I'm trying to perform audit using Lighthouse DevTools.
My site requires authentication.
When I run the test the lighthouse logs me out and only anayses /login.
How can I get Lighthouse DevTools to analyse my site? Can I supply login credentials?
If you are using local storage in order to preserve an authenticated state after refresh
(for example storing a user's token, and on refresh using that token in order to login like a lot of SPA's)
I found a solution that might work :
https://github.com/GoogleChrome/lighthouse/issues/1418#issuecomment-397753583
If using chrome dev tools to run light house :
On the lighthouse tab in chrome dev tools simply click the settings icon
Uncheck the clear storage check box.
Generate the report, and on refresh it will use the local storage data therefore will keep you logged in.
If using the lighthouse cli tool :
Install and execute as explained in JoostS answer, just add to the lighthouse command the --disable-storage-reset flag , and you can also add the --view flag in order to open a tab for the report.
So the command will be :
lighthouse <url> --port <port_chrome_debugger_opened> --disable-storage-reset --view
Verifying it tested the logged in page
You can verify it tested the logged in page by looking at the report under the performance metrics there are images of the page that was loaded, so if the images correspond to the logged in page I believe it means it was tested correctly.
See Testing on a site with authentication in the official readme:
When installed globally via npm i -g lighthouse or yarn global add lighthouse, chrome-debug is added to your PATH. This binary launches a standalone Chrome instance with an open debugging port.
Run chrome-debug. This will log the debugging port of your Chrome instance
Navigate to your site and log in.
In a separate terminal tab, run lighthouse [siteurl] --port port-number using the port number from chrome-debug.
I had to install node 10.16.3 first (node.js > 10.0.0).
nvm install 10.16.3
will show error
Could not download npm for node v10.16.3.
Download npm version what you want - https://github.com/npm/cli/releases
I had downloaded 6.9.0 npm version - https://github.com/npm/cli/archive/v6.9.0.zip
It should be extracted to C:\Users\xxx\AppData\Roaming\nvm\v10.16.3\node_modules\npm
then go to C:\Users\xxx\AppData\Roaming\nvm\v10.16.3\node_modules\npm\bin and copy two npm files. first (npm .cmd file), second (npm file)
then paste both files in C:\Users\xxx\AppData\Roaming\nvm\v10.16.3
open cmd and run command node -v and npm -v
After that lighthouse CLI works as expected.
The command still does not work though. :/
I have followed the advice of JoostS - Testing a site with authentication
The technique does not work. It opens up an new, not logged in window, and behaves just like you would expect without the --port argument.
I checkout Squidex from stash and try to run in my local. I am trying to run the Webpack Dev Server. I follow the instruction from official website without any change.
npm i (Install all dependencies for the frontend)
npm rebuild node-sass --force
npm run dev (Runs the webpack vdev server)
but when I open localhost:3000 from browser and tried to click Login to Squidex,
I got below error and then the popup login page disappeared.
oidc-client.min.js:1 Error parsing JSON response Unexpected token < in JSON at position 0
I have no idea what I can do to fix it. I do nothing change on it and just checkout source code and run in my local.
Thanks for any suggestion.
The localhost:3000 is the webpack dev server. You have to run ASP.NET core app in VS2017 to start the Squidex app.
Ps. Don't forget to edit "baseUrl": "http://localhost:xxxx" in appsetting.json to match with your DEBUG url in Project > Properties.
As per the Ionic Guide Chapter 4 http://ionicframework.com/docs/guide/testing.html, ionic serve will start a live reload server, which it does in my case, but reload is not happening.
Is there any pre-req we need to have for this thing to work? Like say live reload chrome extension?
E:\Ionic\myapp>ionic serve
Running dev server: http://localhost:8100
Running live reload server: http://localhost:35729
Here is what worked for me:
stop ionic service if you running it 'q' command
run: ionic address from command prompt
After running this command it will prompt you to select what address you would like to use one is localhost and the second one is your machine IP address.
Try to use select your machine IP address instead of localhost.
Even I faced similar issue, console used to display the file changed but automatic browser refresh wasn't happening. Later I found out a missing closing tag in my index.html page that prevented ionic to inject the below script required for live reload.
<script src="//localhost:35729/livereload.js?snipver=1"></script>
Please check for any typo errors or other html issues in the index.html page and fix those. Live reload should word properly after that.
In Ionic 2/3, I solved this problem by removing the folder node_modules/ and file package-lock.json, then at terminal run:
npm install --save
I'm my case, I was bootstraping the app with this:
window.ionic.Platform.ready(function() {
angular.bootstrap(document, ['myApp']);
});
Then I changed it for this:
<body ng-app="myApp" >
<ion-nav-view></ion-nav-view>
</body>
And it works
if you want to get Live console logs in the ionic application (real
device or emulator)
ionic cordova run android --livereload --consolelogs --serverlogs
I am trying to create Dynamic Web Application in Eclipse on Google App Engine.
I have followed this tutorial exactly but whenever I Run on Server, I get the following error. I have shown both, error log and the dialog that appears when I run my project. And apparently there is no search result after Googling this error. Any help would be appreciated in this regard. Thanks.
UPDATE:
Point to note here is that if I use the tutorial available here then the project runs fine. The difference is that This way I create new project by clicking the New Web Application Project button in the toolbar:
It is because your launch configuration file is corrupt.
location: WORKSPACE/.metadata/.plugins/org.eclipse.debug.core/.launches.
All you need to do to solve this problem is to delete the existing launch configuration (in Run > Run configurations)
More precisely: Run > Run configurations > Web Application > right click in your project's name > Delete