Background in web design. I write code (predominantly js) to stave off the impending Cylon apocalypse. MERN stack enthusiast. Isomorphic environmentalist. If I don't know it, I'm building something to learn it.
Nothing here yet.
No blogs yet.
Not sure if you’re looking for a faster build in general or if you want a solution other than stopping and recreating the running production container from a newer image. For the second point, I’ve found that using Amazon Web Service’s ECS platform for deploying Docker apps has been rewarding for our team, albeit a tad expensive. This is because it uses the Blue-Green deployment strategy by default, where you deploy the new Docker container to your production environment and it gracefully updates all containers in your “cluster” (there’s a bit of a learning curve with anything AWS, but in this case that’s just a load-balanced set of instances running your Docker app). Although this is an AWS-specific solution, a Blue-Green deployment method can be implemented on any set of load-balanced VPS’s with the right scripts! As for the first point, we’re running CircleCI as our CI solution and have found that the build step can be useful in identifying bugs or issues we didn’t see initially. It won’t push the build live if it fails, so it’s an added layer of protection. Hope this was helpful ¯_(ツ)_/¯
Hey there, One common practice is to build an API server and then use a library such as axios (https://github.com/axios/axios) to make requests to/from the API dynamically. This is often done through initializing state in your React component's constructor and then updating/setting the state in the componentDidMount() component function with your API call's results. Here's a good example phrasing everything much better than me https://daveceddia.com/ajax-requests-in-react/ There are several articles online that can quickly walk you through building a Node/Express API and connecting it to a db of your choice (Mongo, Postgres, MySQL). A cursory glance at this one seems it'd be a good starting point. https://www.codementor.io/olatundegaruba/nodejs-restful-apis-in-10-minutes-q0sgsfhbd
The most challenging trait I've encountered from other devs is hubris. It leads to two issues mentioned below: a reluctance to expand his/her knowledge base and a detrimental sense of having the answer for everything. I try to consistently put myself in check with respect to what I know, which tools I'm using for a particular task, etc. Doing so has made me a better developer and a better teammate.
When I first tackled React, I went through all the best tutorials available online. Joe Maddalone from Egghead , Tyler McGinnis' introductory course on React, the Code School course , even a few PluralSight tutorials. Although these all gave me an excellent working knowledge, nothing really made it click until I took on a project and forced myself to craft a React-based solution. As I'm used to static CSS/HTML with jQuery/JS to manipulate the DOM for simpler portfolio sites, writing the app in React from the onset required me to answer common use-case questions from its perspective. "How do I add CSS styling once a user scrolls?" "How do I add local images?" "How do I hide/show this?" What resulted was a new appreciation for the workflow, as well as a revision to the way I approached building a page in the first place. It's one thing to understand all the inner workings and best strategies for the library; knowing how to use it as a tool is best learned from rolling up your sleeves and pushing through it!
I've experienced a similar drawback as of late—wanting to contribute but not entirely sure of my skills. I think a viable solution for this would be to use JS meetups in your area as an opportunity to start your own open-source project. The group could be relatively small, and the bi-monthly or monthly meetups paired with a Slack channel could get the project off the ground easily. Your first missteps or issues could then be played out in a small, controlled environment. As an aside, a useful resource I've found is the guidelines set forth on this Scotch.io tutorial by Noman Ur Rehman: https://scotch.io/tutorials/contributing-to-open-source-software-with-git