reformated content to work better in wintersmith
This commit is contained in:
parent
8d469ffc1a
commit
defc28c5f1
|
|
@ -5,11 +5,11 @@ date: 2012-06-28
|
|||
template: article.jade
|
||||
---
|
||||
|
||||
##Overview
|
||||
|
||||
Migrations are a convenient way for you to alter your database in a structured and organized manner. You **could** edit fragments of SQL by hand but you would then be responsible for telling other developers that they need to go and run them and where they are located.
|
||||
|
||||
Keeping track of which changes need to be run against which deployment environment also posses an equally challenging situation on every deployment.
|
||||
## Keeping track
|
||||
|
||||
Which changes need to be run against which deployment environment also posses an equally challenging situation on every deployment.
|
||||
|
||||
Migrations **TRIES** to simplify this process by:
|
||||
|
||||
|
|
@ -18,7 +18,7 @@ Migrations **TRIES** to simplify this process by:
|
|||
- And allow you to account for environment variations
|
||||
|
||||
|
||||
##How it works
|
||||
## How it works
|
||||
|
||||
Migrations are specially named CodeIgniter classes saved in the migrations folder…
|
||||
|
||||
|
|
@ -95,8 +95,7 @@ Added for connivence to organize settings based on environment. The return valu
|
|||
}
|
||||
}
|
||||
|
||||
> __NOTE__
|
||||
>> There are a more than few classes that can help with developing migrations:
|
||||
> **NOTE**: There are a more than few classes that can help with developing migrations:
|
||||
__dbforge()__ loaded by the migration class, can be used to create and delete tables
|
||||
- __active record__ can be used to do simple updates/deletes
|
||||
- __log_message()__ to log changes made to the database (console app in mac to watch)
|
||||
|
|
@ -155,16 +154,15 @@ and then run
|
|||
migrate/current
|
||||
---
|
||||
|
||||
|
||||
> There currently is no UI, however one could be build based on the return values of the _migrate_ methods.
|
||||
|
||||
>> Return values:
|
||||
> Return values:
|
||||
- TRUE, If Migration is on the latest version
|
||||
- FALSE, If the migration failed
|
||||
- INT, revision number successfully updated to
|
||||
|
||||
|
||||
##Additional Resources
|
||||
## Additional Resources
|
||||
- [Migrations CodeIgniter Manual](http://codeigniter.com/user_guide/libraries/migration.html)
|
||||
- [DBForge Manual](http://codeigniter.com/user_guide/database/forge.html)
|
||||
- [Active Record Manual](http://codeigniter.com/user_guide/database/active_record.html)
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: ES6 is Evergreen, so Fuck Webpack
|
||||
title: Fuck Webpack, ES6 is HERE!
|
||||
author: geoff-doty
|
||||
date: 2017-12-24
|
||||
template: article.jade
|
||||
|
|
@ -7,21 +7,31 @@ template: article.jade
|
|||
|
||||
I know. I know. Blasphame, but I really hate [Webpack](https://webpack.js.org/), not the idea of it but what it turned web development into - a bloated tangled mess of **shit you don't need**.
|
||||
|
||||
Lets take a jaded closer look...
|
||||
|
||||
## Webpack
|
||||
|
||||
[Webpack](https://webpack.js.org/) became the defacto go-to solution to get the latest [es6](http://es6-features.org) javascript language functionality into a developers pipeline via transpilers like [Babeljs](https://babeljs.io/) and support the overly bloated non-standard web component soultion as the [ReactJS](https://reactjs.org/) framework (batteries NOT included). Sure [Webpack](https://webpack.js.org/) does more or can do more, but in the end developers just want to develop with [es6](http://es6-features.org) features.
|
||||
[Webpack](https://webpack.js.org/) became the defacto go-to solution to get the latest [es6](http://es6-features.org) javascript language functionality into a developers pipeline via transpilers like [Babeljs](https://babeljs.io/) and support the overly bloated non-standard web component soultion as the [ReactJS](https://reactjs.org/) framework (batteries NOT included). Sure [Webpack](https://webpack.js.org/) does more or can do more, but in the end developers just want to develop with [es6](http://es6-features.org) features, **however** this was only supose to be a temporay *polyfill*, until browsers started supporting the next version of Javascript -- ES6.
|
||||
|
||||
This is a web developers handycap and reminds me of those old drug commercials
|
||||
ES6 is HERE
|
||||
|
||||
I work more, so I can do more drugs, so I can work more...
|
||||
99% of the browsers support it, even Microsoft Edge, Safari, Chrome, Opera, Firefox...
|
||||
|
||||
But WebPack left us for this constant jonesing that put a permanent handycap on web developers that reminds me of those old drug commercials
|
||||
|
||||
"I work more, so I can do more drugs, so I can work more..."
|
||||
|
||||
it becomes
|
||||
mantra turned to become
|
||||
|
||||
I work more, so I can add more configuration, so I can work more...
|
||||
"I work more, so I can add more configuration, so I can work more..."
|
||||
|
||||
Dont know about you, but dicking around with configurations all day, and watching build processes move ever S L O W E R is not what I signed up for.
|
||||
|
||||
So...
|
||||
|
||||
**PULL THE FUCKING PLUG!**
|
||||
|
||||
Stop getting distracted by the shiny future that may never come, and focus on the here and now. Here and now we have native es6 language support in all evergreen browsers.
|
||||
Stop getting distracted by the *shiny* future that *may* never come, and focus on the here and now. **Here** and **now** is pretty awesome. We have native ES6 language support in all evergreen browsers.
|
||||
|
||||
No webpack.
|
||||
|
||||
|
|
@ -29,25 +39,28 @@ No configuration.
|
|||
|
||||
No bullshit.
|
||||
|
||||
Write the code you love, and free yourself from the **shit you dont need.**
|
||||
|
||||
### How Does it work
|
||||
|
||||
Everything starts with your `index.html` page, or what ever html page your building, and you turn your `script` includes from this
|
||||
|
||||
```html
|
||||
|
||||
<script src="mycode.js"></script>
|
||||
```
|
||||
|
||||
into this
|
||||
```html
|
||||
|
||||
<script type="module" src="mycode.js"></script>
|
||||
```
|
||||
|
||||
and those lazy import statements you have that dont include the extension
|
||||
```javascript
|
||||
|
||||
|
||||
import Code from './src/Code';
|
||||
```
|
||||
|
||||
should have the extension
|
||||
```js
|
||||
|
||||
import Code from './src/Code.js';
|
||||
```
|
||||
|
||||
and everything is right with the world and we can find peace and happyness for all.
|
||||
|
||||
**FUCK WEBPACK!**
|
||||
**FUCK WEBPACK! ES6 IS HERE**
|
||||
|
|
@ -5,8 +5,9 @@ date: 2012-10-18
|
|||
template: article.jade
|
||||
---
|
||||
|
||||
**What** is Git? **How** does it help developers? **Why** is it killing every other source control management system out there? **When** can I use it?
|
||||
|
||||
Primer on Git source-control management
|
||||
Learn more with this Primer on Git source-control management
|
||||
|
||||
## Overview
|
||||
|
||||
|
|
|
|||
|
|
@ -5,16 +5,14 @@ date: 2015-08-10
|
|||
template: article.jade
|
||||
---
|
||||
|
||||
Understanding CRUD operations, both apparent and implied
|
||||
**CRUD** is an acronym for **Create**, **Read**, **Update**, and **Delete**. Each letter in the acronym translates to an operation performed on data. Understanding CRUD operations, both apparent and implied will help you better understand design needs, how to communicate those needs, and the scopee of work ahead
|
||||
|
||||
## Introduction
|
||||
## CRUD
|
||||
|
||||
CRUD is an acronym for **Create**, **Read**, **Update**, and **Delete**. Each letter in the acronym translates to an operation to be performed, such as
|
||||
|
||||
- Create or add new entries
|
||||
- Read, retrieve, search, or view existing entries
|
||||
- Update or edit existing entries
|
||||
- Delete/deactivate existing entries
|
||||
- **C**reate or add new entries
|
||||
- **R**ead, retrieve, search, or view existing entries
|
||||
- **U**pdate or edit existing entries
|
||||
- **D**elete/deactivate existing entries
|
||||
|
||||
The CRUD operations are at the heart of most dynamic websites, especially popularized by those created during the Web 2.0 era. CRUD is often referred to or most relevant when designing user interfaces for most applications. Those interfaces could be a GUI-based interface or as a low-level Application Program Interface (API)
|
||||
|
||||
|
|
|
|||
|
|
@ -5,13 +5,11 @@ date: 2015-05-14
|
|||
template: article.jade
|
||||
---
|
||||
|
||||
You ever feel like there is a great divide among developers, like the parting of the ocean where on one side you have Windows developers and on the other -- the rest of the entire development world!
|
||||
You ever feel like there is a great divide among developers, like the parting of the ocean where on one side you have Windows developers and on the other -- **THE REST OF THE** *ENTIRE* **DEVELOPMENT WORLD!** -- I did.
|
||||
|
||||
I did.
|
||||
## So, I bought a Mac!
|
||||
|
||||
So, I bought a Mac!
|
||||
|
||||
Then, I figured out how to make **Windows Suck Less™** for development. On this short trip over Windows short comings I'm going to provide the perfect recipe to fix one aspect of Windows to achieve my over-arching desire to make **Windows Suck Less™**
|
||||
*Then*, I figured out how to make **Windows Suck Less™** for development. On this short trip over Windows short comings I'm going to provide the perfect recipe to fix one aspect of Windows to achieve my over-arching desire to make **Windows Suck Less™**
|
||||
|
||||
---
|
||||
##### Fun FACT: The latest Visual Studio 2015 install ships with Google's Chrome Browser, Git, and NodeJS.
|
||||
|
|
|
|||
|
|
@ -5,13 +5,9 @@ date: 2016-08-12
|
|||
template: article.jade
|
||||
---
|
||||
|
||||
*Launch like a start-up, scale like an enterprise*
|
||||
The API design *should* be organized around **REST** principles, however to maintain both user and developer sanity it should *also* be pragmatic, thus we call it **RESTful design**, as it may not conform to *all* the REST architecture design tenets.
|
||||
|
||||
## Introduction
|
||||
|
||||
The API design should be organized around REST principles, however to maintain both user and developer sanity it **should** be pragmatic, thus we call it RESTful design, as it may not conform to *all* the full REST architecture design tenets.
|
||||
|
||||
This document summaries *RESTful* design tenets.
|
||||
## Launch like a start-up, scale like an enterprise
|
||||
|
||||
API's should have predictable, resource-oriented URLs and to use HTTP-based response codes to indicate API errors. Leveraging built-in HTTP features, like HTTP authentication and HTTP verbs, allows off-the-shelf HTTP clients to work out-of-the-box.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue