#Jekyll Markdown Quick Reference
####Write in simply awesome markdown
layout: post
title: Markdown Style Guide
---
const http = require('http'); | |
const fs = require('fs'); | |
const hostname = 'localhost'; | |
const port = 8080; | |
const type = 'json' || 'xml'; | |
var server = http.createServer((req, resp) => { | |
resp.statusCode = 200; | |
resp.setHeader('Content-Type', `application/${type}`); |
{ | |
"dependencies": { | |
"com.unity.package-manager-ui": "2.0.3", | |
"com.unity.textmeshpro": "1.3.0", | |
"com.unity.modules.animation": "1.0.0", | |
"com.unity.modules.audio": "1.0.0", | |
"com.unity.modules.imgui": "1.0.0", | |
"com.unity.modules.jsonserialize": "1.0.0", | |
"com.unity.modules.particlesystem": "1.0.0", | |
"com.unity.modules.physics2d": "1.0.0", |
# Standard game dev stuffs | |
[Bb]uilds/* | |
# Unity folders | |
[Ll]ibrary/ | |
[Oo]bj/ | |
[Tt]emp/ | |
[Ll]ogs/ | |
# Rider |
var fs = require('fs'); | |
var path = require('path'); | |
var assetsFolder = '../Assets'; | |
var simpleFolders = ['Scripts', 'Sprites', 'Prefabs', 'Scenes', 'Animations', 'Sounds']; | |
simpleFolders.forEach(function(item) { | |
console.log('Creating folder ' + item + '...'); | |
fs.mkdir(path.join(assetsFolder, item), function(err) { | |
if (err && err.code === 'EEXIST') { |
Sitecore.Data.Database masterDb = Sitecore.Configuration.Factory.GetDatabase("master"); | |
Sitecore.Data.Items.Item item = masterDb.GetItem(new Sitecore.Data.ID(Constants.HomeItemId)); |
public class PromotionsController : Controller | |
{ | |
/// GET /promotions/{id} | |
public ActionResult Details(int id) | |
{ | |
string apiUrl = $"http://strapi.wph.sg:1388/promos/{id}"; | |
using (HttpClient client = new HttpClient()) | |
{ | |
client.DefaultRequestHeaders.Add(name: "Accept", value: "application/json"); |
#Jekyll Markdown Quick Reference
####Write in simply awesome markdown
layout: post
title: Markdown Style Guide
---
A downstream repository (aka a “fork”) maintainer commonly needs to stay current with upstream work (aka "original"). The case is development continues on the upstream
repo while you work on your own origin
fork. You want to fetch
the upstream changes and apply them to your origin
so you don't make conflicts.
The following steps allow you to achieve this on the command line in a local git repository.
Git sees every file in your working copy as one of three things:
Ignored files are usually build artifacts and machine generated files that can be derived from your repository source or should otherwise not be committed. Some common examples are: