| // TypeScript Fundamentals For JavaScript Developers | |
| /* | |
| Tutorial for JavaScript Developers wanting to get started with TypeScript. | |
| Thorough walkthrough of all the basic features. | |
| We will go through the basic features to gain a better understanding of the fundamentals. | |
| You can uncomment the features one by one and work through this tutorial. | |
| If you have any questions or feedback please connect via Twitter: | |
| A. Sharif : https://twitter.com/sharifsbeat | |
| */ |
| #!/bin/bash | |
| ################################## | |
| # | |
| # THE ARCHIVE TRACKER | |
| # | |
| # REF: https://gist.github.com/markwk/c85a8a72bc8c03d0f510262bb5219a34/ | |
| # | |
| # INTRODUCTION: | |
| # Daily script to navigate to a directory of plain text files, | |
| # add files to git repo, calculate key stats, store stats to csv |
| let UserContext = React.createContext(); | |
| class App extends React.Component { | |
| state = { | |
| user: null, | |
| setUser: user => { | |
| this.setState({ user }); | |
| } | |
| }; |
| tail -f -n 450 storage/logs/laravel*.log \ | |
| | grep -i -E \ | |
| "^\[\d{4}\-\d{2}\-\d{2} \d{2}:\d{2}:\d{2}\]|Next [\w\W]+?\:" \ | |
| --color |
| // Models is sequelize instance | |
| app.use('/smartphones', smartphonesRouter(models)); |
This code for get all information on event in request/response (XHR/Fetch) you can manipulation everything in Request/Response like headers, data, & etc.
i don't want to handle 10++ request for get something in request/response, so overwrite window.fetch (globally) to do it.
const OriginalFetch = window.fetch
window.fetch = (url, options) => {
This guide was written because I don't particularly enjoy deploying Phoenix (or Elixir for that matter) applications. It's not easy. Primarily, I don't have a lot of money to spend on a nice, fancy VPS so compiling my Phoenix apps on my VPS often isn't an option. For that, we have Distillery releases. However, that requires me to either have a separate server for staging to use as a build server, or to keep a particular version of Erlang installed on my VPS, neither of which sound like great options to me and they all have the possibilities of version mismatches with ERTS. In addition to all this, theres a whole lot of configuration which needs to be done to setup a Phoenix app for deployment, and it's hard to remember.
For that reason, I wanted to use Docker so that all of my deployments would be automated and reproducable. In addition, Docker would allow me to have reproducable builds for my releases. I could build my releases on any machine that I wanted in a contai
| import { Dimensions } from 'react-native'; | |
| // Guideline sizes are based on standard ~5" screen mobile device | |
| const guidelineBaseWidth = 350; | |
| const guidelineBaseHeight = 680; | |
| const scale = (size, screen = Dimensions.get('window')) => { | |
| return screen.width / guidelineBaseWidth * size; | |
| }; | |
| const verticalScale = (size, screen = Dimensions.get('window')) => { |
| // | |
| // MIT License | |
| // | |
| // Copyright (c) 2018 Ali Sharif | |
| // | |
| // Permission is hereby granted, free of charge, to any person obtaining a copy | |
| // of this software and associated documentation files (the "Software"), to deal | |
| // in the Software without restriction, including without limitation the rights | |
| // to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
| // copies of the Software, and to permit persons to whom the Software is |