Add the following to your ~/.bashrc
:
alias g='git'
# Postgresql | |
# ------------------------- | |
version: "3" | |
services: | |
app: | |
env_file: | |
- .development.env | |
container_name: awesome_nest_boilerplate | |
restart: always | |
build: . |
Using setDate()
const today = new Date()
const tomorrow = new Date(today)
tomorrow.setDate(tomorrow.getDate() + 1)
Rails 6 is full of fun awesome new features and some new ways of compiling our assets. Heroku is one of the easiest way to deploy your rails application but things between development and production can get a little hairy if you’re not careful with a couple of gotchas that exist with the way we compile and use assets in production making your site look weird by having missing pictures or css that just don’t load. Throw in two ways off compiling assets now with Webpacker and Sprockets and things getting even more complicated.
The first thing you need to do with any asset your you want to use like images that are in your assets folder is to use the asset_path helper or asset_url helper instead of a hardcode link to the path.
So image tag that might look like this in your erb file:
CREATE TABLE "posts" ( | |
"id" serial NOT NULL, | |
"title" character varying(255) NOT NULL UNIQUE, | |
"body" TEXT NOT NULL, | |
CONSTRAINT posts_pk PRIMARY KEY ("id") | |
) WITH ( | |
OIDS=FALSE | |
); | |
// Place your key bindings in this file to override the defaultsauto[] | |
// Place your key bindings in this file to override the defaultsauto[] | |
[ | |
{ | |
"key": "ctrl+k ctrl+u", | |
"command": "-editor.action.transformToUppercase", | |
"when": "editorTextFocus" | |
}, | |
{ | |
"key": "ctrl+shift+7", |
This is source code crawl data vietnamnet paper using Scrapy
const express = require('express');
const path = require('path');
const app = express();
// Allow dotfiles - this is required for verification by Lets Encrypt's certbot