Thanks very much! I need to rethink this On Tuesday, August 1, 2017 at 5:00:40 AM UTC-7, Juri Strumpflohner wrote: > > Well to be honest, Docker is much more than just from a developer's > perspective. With Docker you version entire machines while otherwise you > version packages, like your frontend package, backend package which you > then deploy to some existing server. > With Docker you create an image of a machine, containing already > everything you need to run your app and you then deploy the entire > container in production and drop the old one. This involves a lot of > automation at various steps in the pipeline. > > Personally I'd first go with an automated build pipeline such as a build > server. We for instance use Jenkins for that, but there are a load of other > tools available. > The workflow is the following: whenever some developer commits to our > Gitlab server which hosts the src code, a trigger is fired to some build > job on Jenkins (which we configured before) which then takes care of > fetching the latest version from GitLab, doing the build, running the tests > for then either creating a deployable package or in some case even > deploying automatically via SSH to the server itself. > > To get an idea, here's a video lesson I recently published on Egghead of a > possible setup for an Angular application with GitHub as the src server, > Travis as the build server and Firebase as the hosting location. > > https://egghead.io/lessons/setup-automated-deployment-with-angular-travis-and-firebase > > > On Mon, Jul 31, 2017 at 7:49 PM Tito <yos...@gmail.com <javascript:>> > wrote: > >> thanks folks for the feedback! My aim is for developing locally then >> deploying in an automated fashion. Yes indeed a huge jump from the way we >> are doing things now :) but the docker thing is more from dev tools pov >> >> >> On Monday, July 31, 2017 at 2:43:32 AM UTC-7, Zlatko Đurić wrote: >>> >>> I agree with Juri. Docker can be quite useful. But the question is, is >>> it useful to *you*? What specific job you want it to do? Develop your >>> angular apps, and only deploy them as docker images? Or maybe use docker >>> images of your backend server for use in local development? Or use some >>> dockerized tools to isolate whatever task in your build pipeline (like >>> building image srcsets) and offload that build task off your meager laptop? >>> >>> It's definitely useful, but don't push it if you don't need it. To >>> finish in the oldest of devops buzzwords, KISS! >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Angular and AngularJS discussion" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/angular/Oa6Cg1wKBhk/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> angular+u...@googlegroups.com <javascript:>. >> To post to this group, send email to ang...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/angular. >> For more options, visit https://groups.google.com/d/optout. >> > -- > Juri > https://juristr.com - @juristr on Twitter >
-- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
