I have a heroku app set up at http://employbl.herokuapp.com. I own the employbl.com domain on google domain so I would like employbl.com and www.employbl.com to render the website hosted on heroku.
I added the domain to the heroku config:
$ heroku domains:add www.employbl.com
▸ heroku-cli: update available from 6.13.13 to 6.14.27-c74500f
Adding www.employbl.com to ⬢ employbl... done
▸ Configure your app's DNS provider to point to the DNS Target
▸ www.employbl.com.herokudns.com.
▸ For help, see https://devcenter.heroku.com/articles/custom-domains
The domain www.employbl.com has been enqueued for addition
▸ Run heroku domains:wait 'www.employbl.com' to wait for
▸ completion
$ host www.employbl.com
www.employbl.com is an alias for www.employbl.com.herokudns.com.
www.employbl.com.herokudns.com has address 23.21.222.104
www.employbl.com.herokudns.com has address 23.23.118.21
www.employbl.com.herokudns.com has address 23.23.151.35
www.employbl.com.herokudns.com has address 174.129.214.98
www.employbl.com.herokudns.com has address 23.21.245.33
www.employbl.com.herokudns.com has address 23.21.55.239
www.employbl.com.herokudns.com has address 54.225.70.24
www.employbl.com.herokudns.com has address 23.21.228.1
In the Google Domains console I created a custom resource record and a synthetic record as outlined here and specified in the heroku docs
The application renders fine at employbl.herokuapp.com but when I navigate to www.employbl.com the HTML renders for my application but the Javascripts and CSS do not. It is a Vue.js app so nothing renders in the browser. In the console I get an error:
GET https://www.employbl.com/css/app.css net::ERR_INSECURE_RESPONSE
www.employbl.com/:37
GET https://www.employbl.com/js/app.js net::ERR_INSECURE_RESPONSE
How can I configure google domains and heroku to play nice together and render my heroku hosted application on the www.employbl.com URL?
I am running OSX sierra and the latest Chrome version
It turns out in my app service provider (Laravel) I was forcing HTTPS for all requests. Once i turned that off it rendered properly
Related
I have installed the MS4W map server and when I try to launch the site in the localhost it takes me to the below landing page. I am unable to see the map getting loaded in the page.
Any suggestions?
Besides using the setup.exe installer from https://ms4w.com, you can install MS4W manually as well, using the .zip available there; you can use the steps below to verify your installation either way:
make sure that you installed/extracted MS4W into a root of a drive (for example,
you should have a resulting directory structure such as:
C:/
ms4w
Apache
apps
...
open a command prompt window (use Windows search, enter "cmd", and make sure to
choose "Run as Administrator"
now in Command Prompt, enter:
cd c:/ms4w
then setup the MS4W environment with:
setenv.bat
which should let you know that the MS4W environment is ready:
GDAL, mapserv, Python, PHP, and commandline MS4W tools path set
now we can install the Apache web server:
apache-install.bat
which should display a successful message such as (notice the text "The Apache MS4W Web Server service was started successfully") :
Installing the 'Apache MS4W Web Server' service
The 'Apache MS4W Web Server' service is successfully installed.
Testing httpd.conf....
Errors reported here must be corrected before the service can be started.
The Apache MS4W Web Server service is starting.
The Apache MS4W Web Server service was started successfully.
if you have errors, you can check the Apache logs at C:/ms4w/Apache/logs
you can also verify that MapServer is ready at the commandline, with:
mapserv -v
which should display MS4W information such as:
MapServer version 7.6.0-dev (MS4W 4.0.3) OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=SVG_SYMBOLS SUPPORTS=SVGCAIRO SUPPORTS=ICONV SUPPORTS=FRIBIDI SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=FASTCGI SUPPORTS=THREADS SUPPORTS=GEOS SUPPORTS=POINT_Z_M SUPPORTS=PBF INPUT=JPEG INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE
TIP: try to now execute other MS4W tools at that same commandline, such as gdalinfo --formats or shp2img etc. (basically you can call any tool now, that lives in C:/ms4w/tools, without ever having to change directory there)
now you are ready to goto your localhost, so open your web browser (Firefox, Chrome, IE) and type: 127.0.0.1 <enter>
you should see the MS4W homepage now in your local browser, with a sample map as well (that is actually a fully configured WMS service served from your local machine, serving Spatialite data), such as: https://ms4w.dev/
I have created basic sample application and integrated angular/pwa. In ngsw-config .json file i added datagroups for api call. Now i can able to download the application and api call is working fine in offline too.
After that i moved to my application and did the same for pwa. Now api call is not working in offline. I checked with api call which i used in sample application still i'm getting the data for that url but i didn't specified in ngsw-config.json file.
I can't unregistered my old service worker and create new service worker. In chrome developer tool i unregistered that service worker and again reload my application but still i'm getting the old data.
Angular version: 6.0.2
Browser:
- [ ] Chrome (desktop) version
For Tooling issues:
- Node version: 8.9.1
- Platform: Windows
I was created a PHP 5.4 application with Web load balancer and mysql 5.5 support on openshift free plan. My problem is when I login into my app via SSH delete the index.php file in app-root/runtime/repo folder (Openshift web folder) and create new test.txt file, my application doesnt show test.txt file. It still shows Openshift welcome page when I access my application.Then I delete test.txt file. The app-root/runtime/repo folder is empty. I tried create new file name 'blahblah' in runtime folder and access but still nothing, only 404 page. However, restart the application doesn't resolve the problem! The problem only happend when I add 'Web Load Balancer'. Without load balancer, my PHP app working normaly event I delete index.php file
When you use the "Web Load Balancer", it runs in front of your application and monitors which of your web servers are up and running. You can visit http://app-domain.rhcloud.com/haproxy-status to view the status of your backend servers. If nothing responds at the root context (/) of your application on the web servers, the haproxy thinks it is down and takes it out of rotation. You have to have something (even a blank index.php or index.html) page so that the haproxy will get a status 200, or change the url that is monitored in the haproxy.cfg file on your main gear.
it's possible to setup a Open URL for MIME type support at (console.developer.google.com). That's create and works fine for my application. But only for the product instance at Google Cloud. In detail:
I've released my application in version 1. It's AppEngine base and it supports a Open URL myapp.appspot.com/oauth2callback. So after the release I will going on with feature development for version 2. I use the local AppEngine dev setup. So I take my second client ID and change the Open URL to my local workstation mydev.workstation.com:8080/oauth2callback. That works fine, but it breaks my product instance. Is there any workaround to use Open URL for the production instance and a second Open URL for my dev instance? In my opinion the Drive SDK settings should be:
enable Authentication Production:
Client ID: xxx
Additional Scopes:
Install URL:
Open URL: https://myapp.appspot.com/oauth2callback
enable Authentication Development:
Client ID: xxx
Additional Scopes:
Install URL:
Open URL: http://devworkstation.com:8080/oauth2callback
Jens
Create separate projects in the console for prod/qa/dev
The answer from #SteveBazyl is the preferred one for all the reasons stated. A kludgy alternative would be to have the servlet that is bound to the Open URL detect when it is dealing with a test scenario and do a 301 redirect to your dev server.
Also, the API URL is pretty consistent, so once you've sniffed it once, it's not to difficult to path the host and use it in a curl script or browser bookmark for local testing.
As an aside "oauth2callback" is a slightly odd name for your Drive Open URL. It's not wrong, but "driveopen" would show the separate concerns.
I am trying to register an app in Openshift, in tk domain using freenom. However, when I go to "URL Forwarding" and put the url of the app "xxxx-xxx.rhcloud.com" I have the following error:
Given URL returns 500
I see that the app is running.
Any idea
finnally I find that openshift can't use url forwadding.
The only option is use cname way. (In dot tk select default name servers and later click over "Manage Freenom DNS"
Previously you need create alias in openshift, this opperation can be done in the app console web interface, create alias option is near app web direction.
here a link with more information:
https://blog.openshift.com/custom-url-names-for-your-paas-applications-host-forwarding-and-cnames-the-openshift-way/