$ sudo apt-get update
Err:1 http://archive.ubuntu.com/ubuntu focal InRelease
Temporary failure in name rerolution
$ host google.com
;; connection timed out; no servers could be reached
# delete local tag '12345' | |
git tag -d 12345 | |
# delete remote tag '12345' (eg, GitHub version too) | |
git push origin :refs/tags/12345 | |
# alternative approach | |
git push --delete origin tagName | |
git tag -d tagName |
{ | |
"final_space": true, | |
"console_title": true, | |
"console_title_style": "folder", | |
"blocks": [ | |
{ | |
"type": "prompt", | |
"alignment": "left", | |
"horizontal_offset": 0, | |
"vertical_offset": 0, |
/** | |
* Filters an array of objects using custom predicates. | |
* | |
* @param {Array} array: the array to filter | |
* @param {Object} filters: an object with the filter criteria | |
* @return {Array} | |
*/ | |
function filterArray(array, filters) { | |
const filterKeys = Object.keys(filters); | |
return array.filter(item => { |
find . -type f | xargs -I {} bash -c "iconv -f utf-8 -t utf-16 {} &>/dev/null || echo {}" > utf8_fail |
# Usage: powershell ExportSchema.ps1 "SERVERNAME" "DATABASE" "C:\<YourOutputPath>" | |
# Start Script | |
Set-ExecutionPolicy RemoteSigned | |
# Set-ExecutionPolicy -ExecutionPolicy:Unrestricted -Scope:LocalMachine | |
function GenerateDBScript([string]$serverName, [string]$dbname, [string]$scriptpath) | |
{ | |
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.SMO") | Out-Null |
-- Find the size of all tables in an Oracle schema | |
-- Script by Sergey Stadnik, http://ozmoroz.com | |
-- Licensed under CC BY with attribution required | |
-- Based on Stackoverflow.com discussion | |
-- http://stackoverflow.com/questions/264914/how-do-i-calculate-tables-size-in-oracle | |
DEFINE schema_name = 'replace_with_your_schema_name' | |
SELECT * FROM ( | |
SELECT |
This is work in progress! I need to added titles and descriptions fro each link, and organize them in categories
- API vs Proxy (video): https://www.youtube.com/watch?v=CJdDtiX_CP4
- http://justapis.com/
- Create an API for any website, in any programming language, without writing a line of code: http://jodoglevy.com/jobloglevy/introducing-gargl-create-an-api-for-any-website-in-any-programming-language-without-writing-a-line-of-code/
- Metadata-Driven Design: Building Web APIs for Dynamic Mobile Apps: http://www.infoq.com/articles/mdd-webapi-for-mobile-apps
- https://github.com/WhiteHouse/api-standards
- http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api
- http://reinout.vanrees.org/weblog/2015/06/03/09-restful.html
- https://github.com/interagent/http-api-design
Platform | Design | Code Gen. | Docs | Testing | Management |
---|---|---|---|---|---|
3Scale | Supports Swagger | None | ActiveDocs (Swagger compliant) | Developer Portal | Security, Analytics, Monetization, Dashboard, Traffic Mgmt. |
Akana | Graphical Designer. Supports Swagger, RAML, WADL, WSDL | Build Code | Document | Developer Portal | API Gateway, Security, Analytics, Orchestration, Transformation, Traffic Mgmt. |
Apigee | Edge UI. Supports OpenAPI Specs | None | Developer Portal | Developer Portal | API Gateway, Security, Analytics, Monetization, Orchestration, Transformation, Traffic Mgmt., API Proxy Editor |
Boomi | Mediate | None |
Antes de mais nada: todo o trabalho precisa ser "commitado". Sem mais, nem menos. Esse é o primeiro passo.
Não reinvente a roda e não seja rebelde. Se o projeto que você começou a trabalhar, já tem um padrão definido e que atende a necessidade, não há razão para mudanças drásticas. Se o projeto já tem tempos de vivência, significa que o padrão atual já dá conta do recado (ou ao menos deveria).
O ideal para manter o código bem versionado é, para cada mudança, um commit. Seja adição de nova funcionalidade, correção de bug ou até remoção de uma funcionalidade antiga. Isso nos dá a facilidade de usar uma das principais funcionalidades do versionamento: retroceder ao código antes do commit indicado.