Recommandé
Contenu connexe
Dernier
Dernier (20)
En vedette
En vedette (20)
Appharbor Introduction
- 1. APP HARBOR An introduction to App Harbor using Git Hub with Continuous Deployment Michael Demarco 2014
- 2. Contents Why ? AppHarbor Units & Pricing Deployment Runtime Demo
- 3. My Case ?
- 4. What Is AppHarbor (Official) .NET PaaS Deploy + Scale + Add-ons Large versatile User Base
- 8. Demo Github + App Harbor
- 9. Contents Why ? AppHarbor Units & Pricing Deployment Runtime Demo
- 10. Thank You for Listening
Notes de l'éditeur
- Explain my case and how I found AppHarbor Describe AppHarbor Units and Pricing AppHarbor during Deployment AppHarbor at Runtime Demo using AppHarbor with ASP.NET + GitHub
- I develop using the Microsoft Stack (ASP.NET) I want somewhere to host and test my web apps that is not my localhost I want my app to be available on the internet I use Git Hub for source control I do not want to pay for the basic service Although I might consider scaling up eventually I have used Heroku and think that it is really cool, but I cannot use Heroku with .NET and MsSql It is possible to use mono…
- AppHarbor is a fully hosted .NET Platform as a Service. AppHarbor can deploy and scale any standard .NET application to the cloud. AppHarbor is used by thousands of developers and businesses to host anything From personal blogs to high traffic web applications. AppHarbor lets you instantly deploy and scale .NET applications using your favourite versioning tool. Installing add-ons is just as easy.
- This is what the pricing looks like A worker unit is a unit of processing power from AppHarbor The free worker unit allows you to host multiple websites and also what is not mentioned here and which is a deciding factor, is that you can have multiple shared databases, one per application. The free tier from Azure will only allow you one shared database per account You will have a public hostname of <app-name>.apphb.com and piggyback ssl on top of that (using *.apphb.com)
- 1 – As a developer, you develop your application and deploy it to your favourite source control manager or directly to AppHarbor using Git 2 – AppHarbor will take your application, perform a build of all the code and will run all your test cases included in the project 3 – If the build and all the tests are successful, your application will be deployed to the AppHarbor servers If the build fails, then a message is written to the log and the deployment will stop there
- Runtime 1 - Once the application is deployed it will be running in AppHarbor’s cloud 2 - AppHarbor will automatically manage horizontal load balancing and failover 3 - AppHarbor runs within AWS and relies on their IaaS (Infrastructure as a service) which is pretty good
- Example mdspa project Hot Towel + EF on Github Create an application on app harbor http://<app-name>.apphb.com/ Connect <app-name> to github repository Add an Sql Database from the Add-On menu Set database connection alias to DefaultConnection Commit a change in the mdspa and synch with github (title) Show deployment log in AppHarbor Connect to database using Sql Management Studio Test the <app-name> from AppHarbor
- Explain my case and how I found AppHarbor Describe AppHarbor Units and Pricing AppHarbor during Deployment AppHarbor at Runtime Demo using AppHarbor with ASP.NET + GitHub