I have download the umbraco accelerator to try get an azure based CMS up and running, I have managed to change the configuration file and the command prompt log upon running the .bat files does not generate any errors.
I have created the storage and azure database and hosted service but when I look at the hosted service there is no way for me to connect into this as the connect button has been disabled. Has anyone else went through the setup and if so have you encoutnered this issue? The URL displayed in azure http://appname.cloudapp.net/umbraco/default.aspx does not work
Which Umbraco version are you deploying? AFAIK the accelerator is deprecated, but I could be wrong if you're doing something in particular, or something I haven't heard of (could be lots!) with web/hosted services.
I've deployed Umbraco 4-6 CMS through WebMatrix 2-3 to azure as a website with relative ease. I didn't need it to be a hosted service/cloudapp.
Is that url not a generic placeholder, do you have a Domain registered to point at it?
Y'know, the more I type, the more I realise I have only a shaky grasp of what you're talking about. Are you sure you need a cloudapp, will an azure website not do?
Related
I'm new to AWS and I got a Spring microservice project that serve in AWS. I have Jboss7 running in AWS-EC2 instances and having setup AWS-ELB for load balancing.
I encounter an issue to remove microsoftsharepointteamservices version number in response header from a URL, for example www.domainName.com/_vti_bin/shtml.exe.
However, i have not idea why microsoft share point service come into picture as I do not install any web server or apache httpd in AWS.
Why shtml.exe is accessible in default AWS setup? Or is it the other issue that related to ISS?
Please kindly advice. Thank you so much.
I found the root cause for this issue. This is due to we have setup Liferay CMS system in our AWS. And Microsoft Share Point service team service is bundle together with Liferay by default to support for Content Search module.
I have recently inherited a Web API development that exposes key endpoints to a company that is hosting and running our website.
We use Octopus to deploy the API to our webserver.
I have duplicated the API and added the appropriate configuration variable to Octopus and deployed it to a secondary webserver (as a development API) for our 3rd party to use.
We are using identity server along with OpenID connect for authentication.
This has built and deployed however authentication is failing.
I know this is a vague description, but I am looking for pointers for an analysis path.
I have compared the logs of the current Api and the test Api and results are the same. (Stating authentication is successful)
Not really enough information to properly answer this question - but I would start by:
1) Checking all the log files you can find for a more detailed exception message. (application logs, IIS logs, event log)
2) Try to narrow down the issue. Does authentication fail for everyone/all the time? Or is this an issue intermittent? Does it work locally? For certain providers only?
3) Slowly start making the new website look like the old website. Comparing web.config files, copy/pasting the old website code onto the new server etc.
4) Check or restore old service accounts, firewall settings, database values, urls etc.
If all else fails - bring everything back to a working state and start changing one thing at a time until you have a little more experience with the application.
I configured a parse server on my AWS elastic beanstalk using this guid I've tested it and it all works fine
Now I can't find a way to deploy parse dashboard on my server.
I did deployed parse dashboard on my local host and connected it to the application on server, But this way I cannot manage (Add and remove) my apps.
Another problem is that parse dashboard missing cloud code on default, I found this on git, but I cant understand where do I add the requested endpoints, is it something like adding app.use('/scripts', express.static(path.join(__dirname, '/scripts'))); on the index.js file?
in order to deploy parse-dashboard to your EC2 you need to follow the Deploying Parse Dashboard section in parse-dashboard github page
parse-dashbard github page
Please make sure that when you deploy parse-dashboard you are using https and also basic authentication (it is also part of the guide)
Now regarding the cloud code: the ability to deploy cloud code via parse CLI and to view the nodejs code in parse dashboard are not available in parse-server but those are parse.com features. Cloud code in parse-server is handled by modifying the main.js file which exist under the cloud folder and deployment should be done manually by you but the big advantage in parse-server cloud code is that you can use any NodeJS module that you want from there and you are not restricted to the modules that were used by parse.com .
Another point about the dashboard. What you can do is to create an express application and then add parse-server and parse-dashboard as a middleware to your express application and deploy the whole application to AWS and then you can enjoy both parse-server (that will be available under the /parse path, unless you changed it to something else) and parse dashboard that will be available under the /dashboard path
Enjoy :)
I have been working with Azure's web app service using Resource Manager to deploy a Django app. It has been working in fits and starts. I really like the auto-deployment from GitHub but I have been frustrated by the ability to work with the underlying machine. There is a "Console" tool through the Azure portal but it has limited functionality and when there is an internal server error on my app, I can't find the server output log.
Can someone share insight into how to view the server logs?
Azure web apps have a number of logs however, the applications logs provided out of the box only support Asp.Net applications. That being said there is an article about django on web apps and how to store and view its logs here.
What'll you'll have to do, as described in the link, is to setup the django application to store its logs on the azure file system. Another option is to setup the django application to email the devs but the better option is to store the logs on the file system properly.
I want to deploy my Sitecore website to Azure.
I am referencing https://sdn.sitecore.net/upload/sdn5/products/azure/310/getting_started_with_sitecore_azure_310-a4.pdf
this pdf file to setup Sitecore Azure but dont know where to put Azure account details its all working at local, has anyone used this before or have idea about this?
The doc you using is dated,
go to the new Sitecore Documentation site install_sitecore_azure