I'm learning http://parse.com and follow onsite tutorial to create expressjs "parse hosting" app.
I created a deployed simple app withou problems, it's accessible via <subdomain>.parseapp.com and displays public/index.html:
parse new
parse deploy
After that I generated expressjs app via:
parse generate
and modified main.js as instructed by adding following as a first string:
require('cloud/app.js');
Unfortunately, after deploying modified app it still displays index.html content. Seems it's some setting like "enable expressjs" that I can't see in documentation or app settings. Any hints?
Did you change the code in index.html? Express/Node is the server powering your app which is serving the index page. Unless you make changes to the HTML in the index page, you'll keep seeing the original generated file.
Related
I am trying to test a mendix app with cypress.
On trying to load the index file, I get the following in both the mendix and cypress logs.
404 - file not found for file: index.html/theme.compiled.css
404 - file not found for file: index.html/mxclientsystem/mxui/mxui.js
Which makes sense as it would be very unlikely that there are files under an html file in a directory structure.
Looking at the source code in the browser
<script src="mxclientsystem/mxui/mxui.js?637896725776724820"></script>
Why would cypress be searching for mxui.js under index.html?
Is this a problem with mendix? With cypress?
Cypress works with a served web page.
Not sure how a mendix app works, but if I want to test an index.html that has scripts and css resources to load, I would use VSCode "Open with live server" option on the index.
This will give me a URL usually localhost:5500 to visit in the app.
If there's any transforms required (e.g is CSS is in SASS format), you would need something more sophisticated involving Webpack and Babel.
Bottom line, serve your app in dev mode and use
cy.visit('url-as-used-in-browser')
to give Cypress access to the compiled page.
I see from the mendix tag
Mendix is a app platform-as-a-service (aPaaS) for Rapid Application Development. The rapid aPaaS offering prioritizes speed and agility and utilizes a “no code” principle
So, there's no code to serve. Just use the cy.visit(url) command using the same URL a user would access.
I have deployed a simple web app and deployed to https://rockdove.centralindia.cloudapp.azure.com:82/. This page has the link to teams app sdk and also has initialized the teams app. im trying to load it inside teams app in my organization using this manifest file. i can upload and install the app but the app is not loading. The index file and manifest used for test is attached here.
Here are a few things to look at:
I don't think you can pass anything to microsoftTeams.initialize(), so remove the 'window' parameter
I've not tested whether the 'validDomains' allows custom ports, but it might not - try put the entry without the ':82', and then also remove entries 2 & 3, so it's only 'rockdove.centralindia.cloudapp.azure.com'
I'm using Electron to build a desktop app that uses the YouTube Data API to get information. The problem is that, when my page loads, I am met with four net::ERR_FILE_NOT_FOUND errors. It's trying to get file://ssl.gstatic.com/s2/oz/images/stars/po/bubblev1/bubbleDropR_3.png and a couple others of the same ilk, all of which obviously do not exist. I am not loading the apis from a relateive path; how can I fix this?
EDIT: I should note that the source of the errors appear to be scripts being loaded in the page's <head>. These were not loaded by me and were put there when the API loaded.
I would like to have an app on Heroku, but if an user access www.example using a mobile device he would be redirected to m.example.
In this m.example I would have a website which is designed for mobile devices with a button "view the original website". Clicking there, we would see the www.example website.
Is there any way to do that on Heroku?
Thanks!
Edit: #RunscopeAPITools said Heroku itself is irrelevant to the problem and the important thing is the framework. I am developing with .NET and using MONO on Heroku, as described here .
According to the documentation: "It uses nginx as the web server and runs on Mono 3.2."
Edit2: After RunscopeAPITools, I started to get more infos about how to do that using nginx, I will test this link and post the results as soon as I can
Edit3: tried this approach by uploading a nginx.conf to Heroku. Nothing happened. Looking in Google I read that is it NOT possible to do that with a config file, only directly on my app. Now I am confused. Can I do that or can't I?
We are using Embedded signing of DocuSign REST API to e-sign files.To sign a file, we upload the required file to our web app and then display it a viewer in the browser. This file can be signed immediately or later.
What is happening is that when the file is signed and the process is completed, we return to the same file view but the updated file is not reflected. Only when we refresh page like 3-4 times, it shows the sign on the file.
This issue comes only for files that were uploaded and signed later. For a fresh file which is uploaded and signed immediately, we get the updated file view.
It appears that all the browsers cache files (not HTML page, but the embedded files). The recommended solutions suggest to either add a parameter in the request when file is reloaded after signing- but this works only intermittently. The other is to rename the file so that the browser picks the updated file. But renaming file is not an option for us.
Is there some other alternative? Have any other DocuSign API users ever faced something similar? (I believe this issue would not come if you use email request mode for e-signing)
Thanks.
There have been no similar reports from anyone... I am not discounting yours necessarily but when you just write up something about your web app I could think of a few things that your web app could be doing out of sequence to see this behavior.
The first common mistake with embedded signing that comes to mind is this. In general embedded signing requires several steps (1) login call (2) create envelope (3) get the view of the recipients.
Most of the people put that logic in the controller code behind a web page so when they come back it goes through the same sequence. I understand that your page has some logic to maybe guard against it, but ideally on the "viewing" you should only call (3) - getting the view. If you somehow end up calling (2) again - you will see the signing sequence all over.
That's the most common mistake. However I do not want to discount your report. In order to actually get to the bottom of it you should post the web service call traces (XML for SOAP / JSON for REST) and show exactly what your app is doing.
Hope this helps.
-mb // i work for docusign