emil
Sun Jul 15 2018
You can use a tool called Telepresence to create a 2-way proxy between your local dev machine and a k8s cluster. Uses : be able to inherit env vars and other configs from k8s locally, make use of other services running in the cluster when running your dev instance of a service you want to test
akshay
Thu Jul 12 2018
Arel is a SQL abstract syntax tree manager for ruby. It helps to simplify creating complex SQL queries and interfaces with various RDBMS. Arel modifies it's AST nodes based on the methods you call on it and ActiveRecord makes use of this to build composable chainable queries and then executes them. A detailed post on Arel: https://jpospisil.com/2014/06/16/the-definitive-guide-to-arel-the-sql-manager-for-ruby.html
emil
Fri Jul 06 2018
You can speed up image builds by making use "--cache-from". This is useful when 1) you already have a previous version of the image which you can pull 2) docker pull is faster than docker build 3) intermediate layers in the previous version can be reused. This is useful for speeding up builds in docker container builder
yuva
Thu Jul 05 2018
There is something called QoS for pods using which we can prevent unwanted rescheduling of pods
emil
Tue Jun 26 2018
you can use GCP cloud shell and use it to run kubectl commands instead of having to create a k8s context on your local kubectl CLI tool. This is very useful for doing some adhoc debugging on a k8s cluster you have access to. Just login to google cloud using google auth, and then click on "Connect" next to the cluster you want to connect to, then use cloud shell.
akshay
Tue Jun 26 2018
We can leverage structs in ruby to encapsulate and hold internal class data into a struct object. Since struct saves us from writing attr_accessor methods or initializer method, we can easily leverage it when in need of a temporary data structure and need to have the data grouped.
kamal
Tue Jun 26 2018
If you are using materialize, you need to initialize the select element with material_select()
. Otherwise the select box will not get rendered.
akshay
Mon Jun 25 2018
Elixir and Erlang has a limit on the number of atoms that can be created. We can view the atom limit using :erlang.system_info(:atom_limit). Atom's text value is stored in the atom table and this is not garbage collected. This explains why user inputs to phoenix routes are to be matched with strings rather than atoms.
Showing 50 to 52 of 66 results