Merken

Deploy and Manage Ruby on Rails Apps on AWS

Zitierlink des Filmsegments
Embed Code

Automatisierte Medienanalyse

Beta
Erkannte Entitäten
Sprachtranskript
1st the time and and you have to the so harder 1
thanks for coming out to learn how to deploy and manage Ruby on Rails applications on Amazon Web Services so a quick introduction to who we are are uh so all 3 of us work on the data decays and tools team I'm Alex would you can find me on Twitter and get help and in the back handing out codes we have that Trubar wrote Lawrence a gold we can also find on Twitter and get help and if you have any questions during the lab feel free to raise your hand in and Lauren will come down and help you out and during the parts word is working on exercises you can ask questions of me appear as well the so what are we doing today we have a Ruby on Rails sample application that's linked inside instruction document you don't need to break down a kilometer or anything but is there so you can look around see how we did integrations play around the further after the lab is done we're going to deploy that to Amazon Web Services using a results works after that we're going to use Amazon Simple e-mail service to send action Miller messages using the new a assessed decay rails stamp and we may run over time for the last part all the instructions are there uh we're going to show you how to catch the rails acid pipeline using Amazon CloudFront so here's a slide those up while the coming in so just a quick show of hands again if you do not have an AWS account yet can you raise your hand call so for this lab you will need every yes account and with the credit handouts giving out you can screen encounter from there but ahead if you don't have a diverse credits yet article so travel on will be buying a 2nd with the credit for you and so will take a couple minutes here just make sure everything is set up so what interior BS account or make it you don't have 1 yet apply here I credits which you shouldn't need for the lab but 50 bucks an encourage 1 to take it an experiment afterwards try things out and there is also a tiny or a link to the instructions page 411 so if anyone can't get to that page let me know as well it will take about 1 more minute for this now we have these parsers feel free issued a question if you have 1 and a at this is the double check it is there anyone who does not have very diverse credits in their hand in applied yet raise your hand so Trevor on confined you but yeah I mean if you if you have an account you can still apply the credits to it the lab is reusing the smallest instance types and were cleaning everything up afterward so and if you're in the aid of us free tier that should cover some of the cost as well but if we take a credit anyway and keep playing around will talk a lot about what you can do at the end of lab as well In will be hanging around afterwards of anyone wants to ask more questions try more stuff the cool are right so let's talk about what we're building so were building
a to layer web application with data results works so when to start by creating an OPS works stack which you can think of as a container for all the other resources that application deployment is going to have the were going to have 2 layers as mentioned before 80 Rails app server layer which will contain any instances are running Ruby on Rails and separate from that and the connection configured by OPS works a my sequel layer that is going to be running a single E C 2 instance with my sequel on it 0 were also going to be from the AP we're sending out e-mails to user accounts with Amazon SES native of the Karil's jam In we're going to cast the rails asset pipeline using Amazon for the so why obs works this is a
question I've heard a few times well we've been talking about lab earlier in the conference I wanted become a strike a midpoint on the convenience and control scale so what source gives you a lot of fine-grained control over how your instances a configured how you scale them and where they live which we have other options such as now it risk deployed confirmation manually using instances that give you more fine-grained control were chase Burke choices like Amazon E C 2 container service and Elastic Beanstalk which give you more convenience sordidly happy to talk about any of the other options afterwards but this is a nice middle ground I think for the latter were doing today so then we're talked a lot about these but just a review of some of the key concepts on a talk about so it it is ops works use is chef to help manage and configure your interview instances so we talked about the concept of a 2nd layer is also concept of an app which contains all the configuration needed to deploy your application tier instances the are also using the new a to be assessed a cave group uh rails region so out of curiosity releases a few weeks if you raise your hand if you've tried that genau before awesome so if you using that in that builds on top of the is this decay for a B V 2 that we released last year we are also going to be covering a little bit about a dubious identity and access management talking about how we can manager credentials safely and best follow the principle of least privilege including I am roles for Amazon E C 2 which the intracystic a rails jam can use and were also under review Amazon SES apart from so we have a Rails application what do we do so we can actually deployed to a the results works right here is the death of care 1 see it might be it so all this review what it is it's a change the gem file in production we use the Unicorn In the mice equal to database adapter Jan and we create a file called before symlink In a deploy folder on a Rails application which essentially pre compiles are static assets during the deployment phase so before symlink as a chef cook I have here somewhere which epochs God so this is already provided for you in the Repo or deploying so we have to make these changes is just a review of the changes you would have to make to take a Rails application you have and get it so will deploy and run unaided USB ups works so now we're getting the 1st exercise we're going to take our sample application and deploy to AWS with OPS works so the star and creator sack when you create the application and database layers and then we're going to create deploy in applications the so the 1st exercise and instruction she does have a length can jump around the different exercises is to create not work stack so Olivia a few minutes to do that and if you have any questions feel free to let me know sure this so just tiny world com
slash rails comp 2015 dash of US and if you're watching this on video I'm going to keep that link up after the conference and its like is not up for any reason feel free to get a hold of us so I can remedy remedial that's the 1 had the now phrase ahead don't have the instruction sheet of and yes and what we I varied don't instructions which raise a hand if you don't have at the core of the the the 1 thing I wanna call out
outlier you're making your stacks as well is to check your BPC option so if you do not have a default the PC so if I look at these TPCs are have a default BBC and 1 that I created earlier I would choose the default BBC because our work right out of the box and if you do not have a default BBC option available please raise your hands so travelogue help if you don't have a default the PC but what region are you in this suggests that what for the yeah so the question was what is the the PC and so PC stands for Virtual Private Cloud so you're instances inside a VPC you can have control over what kind of inbound and outbound traffic outbound traffic is allowed for example instead of different subnets of sort of a way to handle networking fear instances so for example as you could were to expand on the SAP you might say that your app and database instances should not be accessible from the public Internet they can only be accessed through a load balancer instance or SSH traffic through bastion server and if you have a VPC makes it easy to set that up so for the purposes of the slab adjust deploying in it and enemy fairly permissive the instances will be publicly accessible but all the discussion at the end is how you could further production IC application is yeah it on
and what
I the so in additionally wire creating the
saccule notice instruction sheet it has a instruction 1st to make an SSH key strictly speaking you don't have to do this but it's definitely recommend in case something goes wrong will be able to SSH under the instances and cedar logs and if you have an existing SSH key you can import or use that when you're creating the stack of of chips chose the the and so so of frequently question has been what should I name my key pair so you can name it anything you like in the mind reels Conf we can write the trick is you wanna make sure that you know the key here using is on your machine and then when you add that to the Sacramento means will be able to SSH two-year instances of the so for the purposes of allowed were using a database layer that OPS works provides for you in the Appendix section of the instructions I've shown how you can you Amazon RDS for either post press Microsoft sequel server oracle or even of my sequel instances with RTS and over so they're further instructions about how you could do that you can follow along with that after the Latin and then in other cases so what offers will do is it will wire up your connection to your database so if you want to use a different type of database instance you could configure that in your Rails application and rails just connect to that the the the the show hands who our has the stacked created so only a few more minutes for that the no you don't agree the whole thing just having created the stack and the next exercise is going to be to create the layers yes Assad as they get raise your hand if you have not maybe if you've not gone through the ad stack form yet if you haven't made the layers yet that's OK that's annex exercise and then raise your hand if you need help getting that set so our working do you have a question and was the the so so the question was if creating a key is necessary and again you don't need to create an SSH key but if something goes wrong later with your application and you don't have an SSH key we don't have a way to look at your logs so I would highly recommend it and then if you have created your stack and you'd like to move on to the next exercises feel free I think this 1st exercise probably takes the longest with all the initial set up we have gone so for the abstract form most of the fields at any use the defaults but if you look in the exercise instruction and lists out a few that you want change 1 that is important is you want to create a new I am instances for a new I am roles because we're going to edit them if you don't create a new role your change could be you get multiple stacks to be changing the permissions on all them of what's so it's a best practice to create a new role anytime you're creating new stack so the question was if we need to create an elastic load balancer so were not creating an elastic load balancer during this lab I go back to the the
so in this lab simply for time purposes were going to directly connect to your application server it is a best practice to have a load balancer but for the sake of time or simplifying the architecture we'll talk a bit about it the end about how you would design things as you iterate on this design so the next step is
exercise 1 B on the instruction sheet which is we're going to create the op 1st layers and launch an instance in each of them and again where were using
non-default options that should be in your instruction sheet but also added for many these a screenshot even compare against shirt so the question
was what would be the difference of choosing an instance store verses in EVS back store for the sake of this lab there is no difference the difference you would find if for example you're running a database on instance storage if that instance goes down you lose your database and everything on it unless you have snapshots and back up your created if it's an EBS backed instance if the instance where go down you would still have the EBS instance of the harbor of on it that you could attach to a new instance you create replace your failed instance that answer question so you could choose
the so the question is when would you choose instance store and the recommended default In is to choosing EBS back sense but for example if you feel that the storage on your instances enough safe your application server in you don't care about anything on it because it's stateless you could choose an instance store and of the so if the server goes down it doesn't then the thing to remember is were creating my sequel of works layers were not creating RTS layers but this is simply a matter of the fact that using yes instance pixel that more time and for the sake of lab we're going with the quicker time option but we do have instructions in instruction sheet or a link to a blog post that will show you how you could switch this over to use RTS note also
recommend you keep an eye on the instance size you select and as you can see here the default is a C. 3 large which is going to be a little bit more expensive than a T 2 a T 1 micro but the smallest instance types from on enough to run a simple application and then once you get to this point where you have both layers created in your instances a spinning up then you're done with this exercise the instances will take a few minutes to set up and you can work on the next steps while they do so the question was about the 5 instructions say to create the instances in the PC so this is based on a stack settings whatever bpcu assigned here stack is the art of the PCB instances will be launched or if you are in the US it's 1 without the PC FIL this be launched and easy to class so be take look the instance creation screen you'll notice you can choose the subnet that goes into of the default subnet is been be fine for all of these and this is where in the PCB instances go that answer questions yet so the question
was that I mention this is running on shaft and so what is going on during the running set up phase so I'm that go to different screen on here for a moment that thing will help demonstrate that so when you look at your layer configuration remember that layers are telling you how everything is configured so if you look at the recipes page for a given layer it shows you during set up configure deployments and so on what chef recipes are running and if you click through a lot should take you to the OPS works get have repo and you can see the source of all the chef Iraq and you could also add your own recipes during these processes you can add or remove anything that you want to customize higher-layer works if we take a look here that the mice equal layers 1
have different recipes running than the Rails apps server layer what's so 1 thing layers do is define what type a recipes and be
run on any instances that are made in that way
so that is configured at the this year Stacker the layer level In you do have a drop-down selection of what has been since er what type of Linux distribution running on for for the sake of lab using the most recent Amazon Linux will work fine call right sort of move on
to the next exercise here and there will be a bit of a possibly and while we wait for some of instances to catch up and create so next for moving on to exercise 1 which is creating and deploying the OPS works application so 1 quick note
when you get to the AP creation about the secret key base environment variable normally you're going to want to run rake secret on your Rails repo but for the sake of what will actually work for deployment any string of letters and numbers that isn't made entirely of numbers will work so right your favorite sentence about spaces Our that wouldn't be a production safe thing to do before the lab if you can't run rake secret copy that value at this will do but you would also want to make this a protected values since once seceded his said you don't want people to be able to see what it the the thing to note is works mostly not enabling SSL so this is purely a time-saving thing and also since the unexpected wandering around certificates so obviously in a production setting you absolutely do want to have SSL set up instances since otherwise you're sending things like user registration from passwords plain text or a wire but for the sake of a sample application it will work just fine without a cell enables and then once you have your application
created you're waiting for this to be the result of the instances screen where both instances are online and running and once you have that you go on to deploy the so while
everyone's working on that the 2 most common mistakes we had when you're testing out these instructions were not setting a secret key base but you don't set that you'll get a white screen travel replication to be completely blank as rails will fail to start running and failing to migrate a database since this is this'll ployment we get database changes we need to run so when you go to the place cranial turn migrate database T x and then run rate DB migrate against a database instance if you don't do that you'll get the generic rails error screen travel interact right so once you have your deployment successfully completed to find your page you would click through your app servers hosting and you can click through the the public DNS or the public IP to get to the and this is what you should see and once you get to this point you're done with exercise 1 and if you have a few minutes so maybe play around register an account make a few tasks when you make an account it will be helpful for future tasks if you using e-mail you actually own this doesn't do e-mail verification but you won't be able to send e-mail to an account that you don't possess with the test account and SES it's also worth noting that at this step if you tried to subscribe to a task update and send mail it's not going to work yet because we haven't configured the yeah and for the sake of I I'm actually not sure how as test accounts handle aliases if you have to explicitly verify each 1 of about actually in this and see how that works out if you try yeah for the sake of a demo of registering 1 account on an e-mail address you own little work to demonstrate everything we need to do have so you don't have to get too complicated 3 males if you don't want to so just for a quick check can you raise your hand if you've gotten to the running application page but can you raise your hand if you haven't gotten that far but you gotta deployment started you raise your hand if you're still waiting fear instances the boot OK so that's not very many people so we'll probably do in those cases is just scared deployment started as soon as a instances boots and we're in and take a few minutes explaining warranted due on the SCS exercise and that can happen while you're waiting for instances get so we'll leave another minute for that that so the question was if there is a post layer so it stops works only provides a my sequel database layer as far as the EC to managed instances if you use an Amazon RDS layer you can use any of the database offerings that RTS house you can use my sequel post-crisis Microsoft sequel server oracle or someday in the future the Aurora database for RTS that Amazon's but so the question was if you can create your own custom layers I'm actually not sure on that front I think that maybe more designed for can fit you can customize the configuration of layers within your stack but that's actually a question I'm going to get the definitive answer on that and I will post that up after the talk so the question was if you have a my sequel instance running on E C 2 are how do you get it so that the app can use it so the way that pops works set things up for you so that the database just works when you deploy is it uses the configuration values of the instance in the database layer in the database layer itself to create your database thought why molfile so if you don't have your my sequel instance inside the mice equal layer then it's not going to work but I believe I can check this for you you might be able to actually take that
instance and register but maybe not for that so like bring your own database that why
molfile for the sake of love I wouldn't recommend it because he I think you have to change some of the underlying chef recipes they're going to try to write it and given enough time you could do that but for the sake of the slab of nature clean and ops works owned my sequences right so we did a show hands who has not started deploying the at OK so we're in a start on the explanation of the next exercise and there should be time to catch up there so the next exercise is sending e-mails using Amazon SES and the new to reassess decay rails jet so some exercises here are the during the configuration necessary to run the id of assess the k rails jam verifying an e-mail so you can send to and from male for that with SES in talk about how we can figure in office works I am instance role profile so the STK has permissions to use Amazon SES to deliver your mail so how do we change are application to be able to use the ADA cystic decay rails jam again apologies for the size of the screen shot here but it's a one-line chains likeness explain it to you if you require the aid of BSS as the KDS rails jam I prefer that you have the dependency locked version 1 0 of that's all you have to do all of the as I have to do encode the configuration creating the delivery handler that will all be done for you by the SEK as you unique and exercise all you need to provide is an environment variable for the aid of this region you want desiccator right so if you moved to exercise to aid in your instruction sheet I were in a pick up from there
so no you don't have to so this is actually good question when we repeat that the question was if you using the AWS STK in your genome filed you have to remove it so there's 2 possible cases here 1 is the using the AWS that's SEK GEM version 2 in which case that is also with the aid of a stochastic a Dutch rails gem users and there's nothing you have to do with all this work if you're using a devoiced decay version 1 it will still work the V 2 in V 1 st case can coexist in the same project and the reason this works is the aid of decay rails jam does this dependency on the highest level sub gem of data decays the mediators as key resources jam so even if you depend on a is that's SEK version 1 you can use both in the same project that answer questions to give me so 1 question us that it can you raise your hand if you did not create your stack in the organ regions goal so pay attention when you're creating the AWS Region environment variable it should work in any region although Italy sending e-mails from a different region than your app is running an but it's a good practice to have a diverse region b the region a stack is running so so the so the created in Northern Virginia which is probably the 2nd most popular option other than the reason you're looking for is US Darcy steps 1 if you created in something other than that then let us and then you don't need to do a deployment for this step because we're not using decay at so once you change your application you're done with this exercise so a
quick note if you're writing here from another talk welcome make sure you raise your hand so Trevor and lawn confined you and give you credits I have known people who can catch up pretty quickly on what we're doing but if you're just behind on the explanations go ahead and work through the instruction sheet which to 1 of your see Table made should be all give you and then this lovely CB upon videos you can catch up on what we've been talking about up until now so the is raise a hand if you have not added the ATBs region variable to your application yet so that is a availability zones so the question was as a matter of its US West to a a to B those are available the sounds we wanna set is the region so you do not want a or B on the and that won't work so for organ again I would be US dash West that's to so the next exercise to be is to set up your e-mail for testing with Amazon SES the so unless you have an existing production account users you have to validate every e-mail address that you send from or send to were going to set an environment variable for what addresses sending your e-mail from which should be 1 the validate and on and for the e-mail you sent to that's going to be any account that you register inside a sample applications so that's the next exercise will have a few minutes from so when so the question was what you have to do for this so you go 1st to the Amazon SES consul under the verified e-mail addresses like there's a direct link to that inside the inside the instructions all the fair warning verified addresses are per region she wanna make sure using the same region you set a Zoraida this region variable and once you request verifying e-mail address you have to go to that e-mail account and clickthrough blank once you've done that they should show verified verified the council the note that it had yet so then the next step you're going to do it is the e-mail handler inside our source code expects you to set the environment variable from e-mail so that the action handler knows what e-mail your sending mail from so you just can't figure that out to be verified e-mail address that you are right so I'm the show how we do that here so if you go to your application and you click edit you would add a environment variable from e-mail and have a be e-mail you verified and the the I'm sorry of you don't need to stop the act but
before will take effect you'll have to redeploy it and so you can deploy the up because it's running the that is strange because that's working for me it's on take a 2nd come look at that for any application edit the instance or the application so just to follow along if we go to the AP screen in your editing application positive to stop that the so my my best guess before I can and take a look at it as you probably trying to stop the instances which you don't have to do this so just a recap the kind I think my instructions were turnabout unclear on the spot when you are editing your application you're not editing your application server instance you're editing the autopsy ops works application itself so if it's telling you that you need to stop an instance you're on the instances editing screen follow the navigation
bar to the APS editing screen
tha
but
in any exercise is done as soon as you click this link and have started
deployment tha
so I see a couple questions so sandbox access means you have to verify every single e-mail address the from a to that it's it just means you do not have production access so if you have production accessed Amazon SES a certain responsibilities about things like how often you year reported for spam how often your e-mails bounce and you have to apply for that with the test account you just verify ever be you on every e-mail you send from a to B and I the so you just go to the drop down and moved to the northern Virginia Region C 1 of verify e-mail address in the same region you created your app and the so if you look at the SES consul upon spring there
is a drop down really can pick which region you wanna run from and this region should match the AWS region that you set in your application Williams here I have the same sandbox access on this account so when you change did you subscribe to
the task 1st that means you haven't configured e-mail yet so and tried to send e-mail the application blew up so that should stop happening as soon as we finish this exercise as so by default you have test accesses access to Amazon SES so the API will check the e-mails the ascending from sending to in requires that they are all verified by you so in this way with the sandbox account you can send e-mail to random other e-mail addresses the have so in Amazon SES you can no it's so within Amazon SES you'd ask your account be authorized to send e-mail and production so there's a form within SES re can do that and it had to take it was support yeah yeah you I believe you still have to verify your from address for then you'll be able to send to anyone as long as you follow the rules associated with that like the in the the right so in this application if you register an e-mail address that you don't own it just won't work to send e-mail to this of course is as long as you have also verified the to address if you had production access then you can send to anyone as long as you're from e-mails 1 you that makes sense the production of attract the the so who is got to the point where they deployed with the aid of US region and from e-mails set as valid in e-mail address OK so just a bit more than half of you still have a few more minutes for that the yeah question the back so have you gotten to the identity and access management step yet so you're not going to get e-mails after finishing this exercise because by default the instance profile arena talk about next has permissions to send to absolutely nobody or to it cannot make any API calls it's kind of a principle of least privilege freer instances so we're going to explicitly authorize are application server instances to make calls the Amazon SES seriously k the so once we finish the entire exercise to that's when e-mail sending will work n so if you're running into a problem that you can identify so the 1st thing a frame the problem is raise your hand so you know 1 of us recover can come and see if it's a known issue otherwise you'd use the SSH key you created and you can SSH on the instance and look at the Rails application locks e-mails will not work
at after exercise to see their work so raise your hand if you have not been able to deploy the new environment variables called so were in a move on to the next exercise so we'll look at now is giving the OPS works I am instance role permissions to use Amazon SES and this is the last thing that you might be getting errors on if you've tried to send e-mail to this point so for a bit of background the reason that this is necessary remember in the beginning we created a stack we created I am instance roles that were attached to each instance in your stack by any aid this STK can you find in use that instance role as credentials but by default you have permissions to make absolutely no API calls the only permissions it has is a trust relationship with OPS works pretty OPS works agent to run the operations it needs to run so any API calls you want to enable instance to run you have to explicitly allow and that's forward doing with this exercise and then remember on the screen and you have a screenshot this we're looking for GOP short CC to roll not the OPS work service for all the because this is the role that the STK is using to get its credentials tha
and then as soon as you attach the Amazon SES full access policy you're sending an e-mail should work you don't have to you redeploy it takes effect immediately and tha
I Ch tha tha so once you subscribe to task updates in change a task state but so I
may have done something wrong myself so ODBC to
role of applied the full access the and I
I use the wrong e-mail here that is not an existing amazon . com e-mail address but so let's try that again the dangers of alive demos so now that is working and if I check my e-mail
we have a task update e-mail sent so when you go to Amazon SES you verified yourself as a center and that should be the same e-mail the user can you sent to so my attempt broke because I accidentally autopilot in road at Amazon . com and said at gmail dot com which is not a verified address so did not work the so really quickly we have about 20 minutes left some take a minute to finish some explanations and then we'll be hanging around around in this room and then on the hall so if we want to keep going so I wanted talk really quick about what we did in the application In order to configure rails to use the STK as a action Miller delivery method when you require the AWS SDK rails jam it creates a symbol US underscore STK delivery method and that is configured to use the of reassess decays Amazon SES client specifically the send right e-mail method as the delivery method fraction mailer and that will work that's only change after make you do that the configuration for an environment that you want this to work on that and making sure your e-mail addresses are verified in the you have permissions on your role to make this call so there is another exercise which we don't have time for in this lab but it doesn't take long to do so I recommend checking it out In that's configuring Ruby on Rails asset pipeline to use Amazon CloudFront as a seedier the code change in there is really simple we look for the acid host as the environment variable CDN domain this is working your deployment because right now you can set it so it's no so just uses replication so if I look at if you look at your source HTML you'll see it's pulling from the host they're running so if you look at the bonus
exercise and work on that you'll end up creating a cloud from distribution which does take about 15 to 20 minutes which is the reason we're not doing it now and then you configure the CDN domain to be the domain name of the distribution you created and then once set set up you will see that the html is pulling your static assets from city to city and the you've created and we have a blog post about this if you're interested so we mention that we're
making a few simplifications for the sake of a laugh it is worth noting that you can take this a lot further so what I can a diagram about here is a bit more of a productionised ops works creation she could have this CloudFront CDN you could use a product like Amazon RU 53 to set up the NRC can clear cut from distribution behind a CDN domain you point other domains 2 parts replication you can use elastic load balancing to load balance across many app server instances instead of a single instance you can set up a time-based ceiling of your app server instances so if you know that every nite at midnight you get a ton of traffic you can set that up to scale up you instances in anticipation of that traffic or a load based scaling so if you get hit really hard new instances are created as needed so question at the I'm sorry so the question was what is the CDN and that's a content distribution network so when you use Amazon CloudFront you can set up your application as the origin server so Amazon CloudFront had the last time I checked the and I say that because last time I said it I was wrong in it added more edge locations since last time I checked they had 53 edge locations around the world so you could be running your application server in Oregon and you can have a person from Australia busier website and the static assets you have such as large images could be cast in edge location in Australia significantly reducing the load on your servers and the page load time the other thing you could set up is RTs as your database and you could have for example automatic failover to a standby instance in another available zone so in the off chance that entire availabilities on goes down your app can failover and keep running so this is where you can build and what I hope you get out of this is that what we did build gives you the knowledge you need to keep iterating on it In build production-ready systems using Amazon Web Services in Ruby on Rails the so deftly keep in touch with
us would love to hear your questions we have a Ruby developer blog and new love to hear your ideas for what you'd want us to cover in weighted want to talk about and thank you very much you know
the bands and all of that some of the ones in the presence of an original some
Resultante
SCI <Informatik>
Atomarität <Informatik>
App <Programm>
Gruppenoperation
Kartesische Koordinaten
Dienst <Informatik>
E-Mail
Twitter <Softwareplattform>
Homepage
Message-Passing
Datenmanagement
Code
Stichprobenumfang
Datentyp
E-Mail
Caching
Gebäude <Mathematik>
Systemaufruf
Parser
Binder <Informatik>
Rechenschieber
Dienst <Informatik>
Mereologie
Codierung
Multi-Tier-Architektur
Wort <Informatik>
Message-Passing
Innerer Punkt
Instantiierung
Resultante
Bit
App <Programm>
Web-Applikation
Mathematisierung
Gruppenkeim
Datenmanagement
Gebäude <Mathematik>
Fortsetzung <Mathematik>
Kartesische Koordinaten
Identitätsverwaltung
Datenhaltung
Datenmanagement
Stichprobenumfang
Zoom
COM
Elastische Deformation
E-Mail
Konfigurationsraum
Auswahlaxiom
Phasenumwandlung
Software Development Kit
Einfach zusammenhängender Raum
Trennungsaxiom
Zentrische Streckung
Nichtlinearer Operator
App <Programm>
Dicke
Ruby on Rails
Datenhaltung
Stichprobe
Einfache Genauigkeit
Quellcode
Biprodukt
Elektronische Publikation
Konfiguration <Informatik>
Dienst <Informatik>
Grundsätze ordnungsmäßiger Datenverarbeitung
Identitätsverwaltung
Dynamisches RAM
Gamecontroller
Server
Ultraviolett-Photoelektronenspektroskopie
Repository <Informatik>
Instantiierung
App <Programm>
Subtraktion
Virtualisierung
Datenhaltung
Keller <Informatik>
Kartesische Koordinaten
Binder <Informatik>
Biprodukt
Quick-Sort
Computeranimation
Keller <Informatik>
Videokonferenz
Internetworking
Lastteilung
Konfiguration <Informatik>
Code
Server
Gamecontroller
Speicherabzug
Default
Streuungsdiagramm
Hilfesystem
Instantiierung
Code
IRIS-T
Keller <Informatik>
Public-Key-Kryptosystem
Bit
Subtraktion
Mathematisierung
Keller <Informatik>
Gebäude <Mathematik>
Kartesische Koordinaten
Fortsetzung <Mathematik>
Login
Lastteilung
Virtuelle Maschine
Bildschirmmaske
Datentyp
Elastische Deformation
Hilfesystem
Einfach zusammenhängender Raum
Nichtlinearer Operator
Datenhaltung
Keller <Informatik>
Datenfeld
Menge
Server
Garbentheorie
Computerarchitektur
Lateinisches Quadrat
Schlüsselverwaltung
Instantiierung
Orakel <Informatik>
Subtraktion
Datenhaltung
Speicher <Informatik>
Datenhaltung
Konfiguration <Informatik>
Instantiierung
Server
Bit
Punkt
Pixel
Web log
Kanal <Bildverarbeitung>
Klasse <Mathematik>
Kartesische Koordinaten
Fortsetzung <Mathematik>
Binder <Informatik>
Konfiguration <Informatik>
Menge
Datentyp
Server
Speicher <Informatik>
Default
Touchscreen
Instantiierung
Server
Prozess <Physik>
Momentenproblem
Quellcode
Computeranimation
Homepage
Differenzkern
Datentyp
Server
Konfigurationsraum
Repository <Informatik>
Phasenumwandlung
Touchscreen
Distributionstheorie
Bit
Server
Zellularer Automat
Zahlenbereich
Kartesische Koordinaten
Raum-Zeit
Datenhaltung
Übergang
Lesezeichen <Internet>
Trennschärfe <Statistik>
Datentyp
Stichprobenumfang
Passwort
Digitales Zertifikat
Systemaufruf
Biprodukt
Quick-Sort
Rechter Winkel
Registrierung <Bildverarbeitung>
Programmierumgebung
Repository <Informatik>
Schlüsselverwaltung
Instantiierung
Zeichenkette
Resultante
Aliasing
Server
Demo <Programm>
Punkt
Adressraum
Mathematisierung
Kartesische Koordinaten
Fortsetzung <Mathematik>
Netzadresse
Homepage
Task
Task
Migration <Informatik>
Direkte numerische Simulation
Datenreplikation
Konfigurationsraum
E-Mail
Touchscreen
Softwaretest
App <Programm>
Booten
Datenhaltung
Programmverifikation
Bitrate
Generizität
Differenzkern
Server
Fehlermeldung
Orakel <Informatik>
Instantiierung
Folge <Mathematik>
Datenhaltung
Natürliche Zahl
Konfigurationsraum
Versionsverwaltung
Profil <Aerodynamik>
Kartesische Koordinaten
Identitätsverwaltung
Instantiierung
E-Mail
Office-Paket
Variable
Softwaretest
Verkettung <Informatik>
E-Mail
Konfigurationsraum
Exakte Sequenz
Instantiierung
Touchscreen
Selbst organisierendes System
Adressraum
Gruppenoperation
Versionsverwaltung
Schreiben <Datenverarbeitung>
Kartesische Koordinaten
E-Mail
Blu-Ray-Disc
Übergang
Videokonferenz
Variable
Softwaretest
Task
Existenzsatz
Stichprobenumfang
E-Mail
Softwaretest
App <Programm>
Quellcode
Biprodukt
Binder <Informatik>
Zeitzone
Dialekt
Menge
Projektive Ebene
Schlüsselverwaltung
Programmierumgebung
Exakte Sequenz
Tabelle <Informatik>
Soundverarbeitung
Open Source
Quellcode
App <Programm>
Server
Kartesische Koordinaten
American Physical Society
Touchscreen
Instantiierung
Quelle <Physik>
Softwaretest
App <Programm>
Linienelement
Adressraum
Einfache Genauigkeit
Binder <Informatik>
Biprodukt
Computeranimation
Quellcode
Open Source
Whiteboard
Endogene Variable
Tropfen
E-Mail
Exakte Sequenz
Bit
Punkt
Rahmenproblem
Adressraum
IRIS-T
Kartesische Koordinaten
Computeranimation
Task
Bildschirmmaske
Tropfen
E-Mail
Default
Gewebe <Mathematik>
Softwaretest
Profil <Aerodynamik>
Systemaufruf
Schlussregel
Biprodukt
Rechter Winkel
Einheit <Mathematik>
Identitätsverwaltung
Server
Mehrrechnersystem
Schlüsselverwaltung
Exakte Sequenz
Instantiierung
Nichtlinearer Operator
Bit
Punkt
Gewichtete Summe
Datenmanagement
Betrag <Mathematik>
Identitätsverwaltung
Instantiierung
E-Mail
Dienst <Informatik>
Variable
Softwaretest
Bitrate
Programmierumgebung
E-Mail
Default
Exakte Sequenz
Instantiierung
Touchscreen
Task
Soundverarbeitung
Task
Mathematisierung
Betrag <Mathematik>
Vorzeichen <Mathematik>
E-Mail
Computeranimation
Aggregatzustand
Demo <Programm>
Task
Adressraum
COM
Vorzeichen <Mathematik>
E-Mail
Computeranimation
Distributionstheorie
Web log
Atomarität <Informatik>
Adressraum
Mathematisierung
Gruppenoperation
Kartesische Koordinaten
Identitätsverwaltung
Code
Task
Hydrostatik
Domain-Name
Variable
Client
Datenreplikation
COM
Konfigurationsraum
E-Mail
Caching
Distributionstheorie
Bruchrechnung
Konfigurationsraum
Systemaufruf
Symboltabelle
Quellcode
Instantiierung
Web log
CDN-Netzwerk
Rechter Winkel
Ordnung <Mathematik>
Programmierumgebung
Exakte Sequenz
Streuungsdiagramm
CDN-Netzwerk
Distributionstheorie
Web Site
Web log
IRIS-T
Kartesische Koordinaten
Homepage
Lastteilung
Domain-Name
Datenreplikation
Softwareentwickler
Schnitt <Graphentheorie>
Bildgebendes Verfahren
App <Programm>
Nichtlinearer Operator
Ruby on Rails
Datenhaltung
sinc-Funktion
Laufzeitsystem
Stichprobe
Physikalisches System
Biprodukt
Ultraviolett-Photoelektronenspektroskopie
Zeitzone
Web log
Diagramm
Last
Mereologie
Server
URL
Instantiierung
Videokonferenz
Gruppe <Mathematik>
Eins

Metadaten

Formale Metadaten

Titel Deploy and Manage Ruby on Rails Apps on AWS
Serientitel RailsConf 2015
Teil 78
Anzahl der Teile 94
Autor Segal, Loren
Rowe, Trevor
Wood, Alex
Lizenz CC-Namensnennung - Weitergabe unter gleichen Bedingungen 3.0 Unported:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen und nicht-kommerziellen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen und das Werk bzw. diesen Inhalt auch in veränderter Form nur unter den Bedingungen dieser Lizenz weitergeben.
DOI 10.5446/30657
Herausgeber Confreaks, LLC
Erscheinungsjahr 2015
Sprache Englisch

Inhaltliche Metadaten

Fachgebiet Informatik
Abstract In this hands-on lab, we will get you started with running your Rails applications on AWS. Starting with a simple sample application, we will walk you through deploying to AWS, then enhancing your application with features from the AWS SDK for Ruby's Rails plugin.

Ähnliche Filme

Loading...