-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Live demo doesn't work #258
Comments
This is the same issue from Oct 24: #243 |
We should probably remove this? Or automate it via GitHub Actions? |
@orta I could work on the Azure app deployment (Azure/webapps-deploy) with a GitHub Actions workflow. It will need Azure Publish Profile secret configured in this GitHub Repository. Is that something that can be configured? |
It's down again :( |
It is still down. |
Related PR: #302 |
It's still not working. |
Over 9 months to fix a url in a README doesn't inspire a lot of confidence. Can anyone fix this issue before it's first birthday? |
We're having this issue over like a year and a half now, so why can't just a maintainer push this project to a service like Heroku? It could be done under half an hour and would end all this mess.
Uhm, we already hit its first birthday. We're approaching its second birthday. 😂 |
Almost forgot to wish this issue a happy birthday 🎂 |
Pushing it to some random service is always the easy quick answer but three times now it has gone down for whatever reasons, and someone's moved it to another server. I couldn't find access to any of them in azure. So, I've removed all the references to a demo link in the README. |
@orta That's the fix, remove the links? MS owns github now... isn't it possible to get it running on a GhPages branch and provide even more value to those cloning this starter repo? |
The issue is that GitHub Pages can only serve static pages. |
How about Azure? |
One option is to add a mongo-dump step to create a JSON file and allow it to be served static? If the problem is that it's a kitchen sink starter kit that can neither be reliably demonstrated, nor reliably hosted by the creators' own cloud service - maybe it requires some non-trivial redesign. |
When I click the live demo I get this:
"This site can’t be reachedtypescript-node-starter.azurewebsites.net’s server IP address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN"
The text was updated successfully, but these errors were encountered: