pocket newsletter lambda
1.0.0
Exemplo de Lambda para buscar todas as postagens de "boletins informativos" do Pocket.
Veja o código lambda em ./src/lambda/newsletter.js.
Execute-o em https://pocket-newsletter-lambda.netlify.com/.
Índice:
A maior parte da lógica específica do Pocket é a função fetchBookmarks , que faz o seguinte:
state: 'all' para obter postagens arquivadas e desarquivadastag: 'newsletter' para buscar postagens marcadas com newsletterdetailType: 'complete' significa que a API retorna dados mais completos{ title, url, excerpts, authors } (todos esses campos são strings)Veja o código
async function fetchBookmarks ( consumerKey , accessToken ) {
const res = await axios . post ( 'https://getpocket.com/v3/get' , {
consumer_key : consumerKey ,
access_token : accessToken ,
tag : 'newsletter' ,
state : 'all' ,
detailType : 'complete'
} ) ;
const { list } = res . data ;
// List is a key-value timestamp->entry map
const entries = Object . values ( list ) ;
return entries . map (
( {
given_title ,
given_url ,
resolved_url ,
resolved_title ,
excerpt ,
authors ,
rest
} ) => ( {
... rest ,
title : given_title || resolved_title ,
url : given_url || resolved_url ,
excerpt ,
authors : authors
? Object . values ( authors )
. map ( ( { name } ) => name )
. filter ( Boolean )
. join ( ',' )
: ''
} )
) ;
} O lambda suporta apenas POST com corpo, portanto:
if ( event . httpMethod !== 'POST' ) {
return {
statusCode : 404 ,
body : 'Not Found'
} ;
}
if ( ! event . body ) {
return {
statusCode : 400 ,
body : 'Bad Request'
} ;
}Oferecemos suporte a solicitações POST de formulário codificadas em URL (feitas, por exemplo, quando JS está desabilitado na página de demonstração) e solicitações JSON.
O corpo chega codificado em base64 (se estiver usando uma solicitação de corpo de formulário codificado em URL) ou não. Isso é indicado pelo sinalizador isBase64Encoded no event .
A análise de uma string codificada em base64 no Node é feita usando Buffer.from(event.body, 'base64').toString('utf-8) .
Para converter o corpo do formulário codificado em URL em um objeto, é usada a função a seguir, que funciona para POSTs com campos simples.
function parseUrlEncoded ( urlEncodedString ) {
const keyValuePairs = urlEncodedString . split ( '&' ) ;
return keyValuePairs . reduce ( ( acc , kvPairString ) => {
const [ k , v ] = kvPairString . split ( '=' ) ;
acc [ k ] = v ;
return acc ;
} , { } ) ;
}Aqui está a funcionalidade do lambda:
const {
pocket_consumer_key : pocketConsumerKey ,
pocket_access_token : pocketAccessToken
} = event . isBase64Encoded
? parseUrlEncoded ( Buffer . from ( event . body , 'base64' ) . toString ( 'utf-8' ) )
: JSON . parse ( event . body ) ;Se a chave do consumidor ou o token de acesso estiverem faltando, enviamos um 400:
if ( ! pocketConsumerKey || ! pocketAccessToken ) {
return {
statusCode : 400 ,
body : 'Bad Request'
} ;
} Finalmente, tentamos fetchBookmarks (a funcionalidade dessa função foi detalhada acima).
Se isso falhar em um erro de solicitação (quando o axios falha, ele tem uma propriedade de response no erro), queremos enviar de volta as informações dessa resposta ao cliente, caso contrário, apenas 500 em caso de erro ou 200 em caso de sucesso:
try {
const bookmarks = await fetchBookmarks ( pocketConsumerKey , pocketAccessToken ) ;
return {
statusCode : 200 ,
body : JSON . stringify ( bookmarks )
} ;
} catch ( e ) {
if ( e . response ) {
return {
statusCode : e . response . statusCode ,
body : `Error while connecting to Pocket API: ${ e . response . statusText } `
}
}
return {
statusCode : 500 ,
body : e . message
}
} [
{
"title" : "TechnicalDebt" ,
"url" : "https://martinfowler.com/bliki/TechnicalDebt.html" ,
"excerpt" : "Software systems are prone to the build up of cruft - deficiencies in internal quality that make it harder than it would ideally be to modify and extend the system further." ,
"authors" : ""
} ,
{
"title" : "CannotMeasureProductivity" ,
"url" : "https://martinfowler.com/bliki/CannotMeasureProductivity.html" ,
"excerpt" : "We see so much emotional discussion about software process, design practices and the like. Many of these arguments are impossible to resolve because the software industry lacks the ability to measure some of the basic elements of the effectiveness of software development." ,
"authors" : ""
} ,
{
"title" : "How SQLite Is Tested" ,
"url" : "https://www.sqlite.org/testing.html" ,
"excerpt" : "The reliability and robustness of SQLite is achieved in part by thorough and careful testing. As of version 3.23.0 (2018-04-02), the SQLite library consists of approximately 128.9 KSLOC of C code." ,
"authors" : ""
} ,
{
"title" : "How FriendFeed uses MySQL to store schema-less data" ,
"url" : "https://backchannel.org/blog/friendfeed-schemaless-mysql" ,
"excerpt" : "We use MySQL for storing all of the data in FriendFeed. Our database has grown a lot as our user base has grown. We now store over 250 million entries and a bunch of other data, from comments and "likes" to friend lists." ,
"authors" : ""
} ,
{
"title" : "jlevy/the-art-of-command-line: Master the command line, in one page" ,
"url" : "https://github.com/jlevy/the-art-of-command-line" ,
"excerpt" : "Note: I'm looking for a new (and potentially paid) lead author to help expand this to a more comprehensive Guide. While it's very popoular, it could be both deeper and more helpful." ,
"authors" : ""
} ,
{
"title" : "Project Mezzanine: The Great Migration | Uber Engineering Blog" ,
"url" : "https://eng.uber.com/mezzanine-migration/" ,
"excerpt" : "What happens when you have to migrate hundreds of millions of rows of data and more than 100 services over several weeks while simultaneously keeping Uber running for millions of riders? This is the story of how dozens of engineers helped Uber move to Mezzanine in 2014." ,
"authors" : "Rene Schmidt"
} ,
{
"title" : "8 Protips to Start Killing It When Dockerizing Node.js - NodeSource" ,
"url" : "https://nodesource.com/blog/8-protips-to-start-killing-it-when-dockerizing-node-js/" ,
"excerpt" : "Containers are the best way to deploy Node.js applications to production. Containers provide a wide variety of benefits, from having the same environment in production and development to streamlining deploys for speed and size. Dockerizing your Node." ,
"authors" : "Tierney Cyren"
} ,
{
"title" : "How and Why We Switched from Erlang to Python – Mixpanel Engineering" ,
"url" : "https://engineering.mixpanel.com/2011/08/05/how-and-why-we-switched-from-erlang-to-python/" ,
"excerpt" : "A core component of Mixpanel is the server that sits at http://api.mixpanel.com. This server is the entry point for all data that comes into the system – it’s hit every time an event is sent from a browser, phone, or backend server." ,
"authors" : "mxpnl"
} ,
{
"title" : "Some Were Meant for C - kell17some-preprint.pdf" ,
"url" : "https://www.cs.kent.ac.uk/people/staff/srk21//research/papers/kell17some-preprint.pdf" ,
"excerpt" : "" ,
"authors" : ""
} ,
{
"title" : "API Gateways Are Going Through an Identity Crisis" ,
"url" : "http://blog.christianposta.com/microservices/api-gateways-are-going-through-an-identity-crisis/" ,
"excerpt" : "API Gateways are going through a bit of an identity crisis these days. Are they centralized, shared resources that facilitate the exposure and governance of APIs to external entities?" ,
"authors" : ""
} ,
{
"title" : "Understanding Database Sharding" ,
"url" : "https://www.digitalocean.com/community/tutorials/understanding-database-sharding" ,
"excerpt" : "Any application or website that sees significant growth will eventually need to scale in order to accommodate increases in traffic. For data-driven applications and websites, it's critical that scaling is done in a way that ensures the security and integrity of their data." ,
"authors" : "Justin Ellingwood"
} ,
{
"title" : "Moving from Ruby to Rust" ,
"url" : "http://deliveroo.engineering/2019/02/14/moving-from-ruby-to-rust.html" ,
"excerpt" : "In the Logistics Algorithms team, we have a service, called Dispatcher, the main purpose of which is to offer an order to the rider, optimally." ,
"authors" : "Andrii Dmytrenko"
} ,
{
"title" : "Getting to Know Python 3.7: Data Classes, async/await and More! | Heroku" ,
"url" : "https://blog.heroku.com/python37-dataclasses-async-await" ,
"excerpt" : "If you're like me, or like many other Python developers, you've probably lived (and maybe migrated) through a few version releases. Python 3.7(." ,
"authors" : "Casey Faist"
} ,
{
"title" : "? What does Unsplash cost in 2019?" ,
"url" : "https://medium.com/p/f499620a14d0" ,
"excerpt" : "Since then, Unsplash has continued to grow tremendously, now powering more image use than the major image media incumbents, Shutterstock, Getty, and Adobe, combined." ,
"authors" : "Luke Chesser"
} ,
{
"title" : "PHP in 2019 - stitcher.io" ,
"url" : "https://stitcher.io/blog/php-in-2019" ,
"excerpt" : "Do you remember the popular "PHP: a fractal of bad design" blog post? The first time I read it, I was working in a crappy place with lots of legacy PHP projects. This article got me wondering whether I should just quit and go do something entirely different than programming." ,
"authors" : ""
}
] No meu site, o lambda não lê o token de acesso e a chave do consumidor da solicitação.
Em vez disso, é um GET simples que lê o token e a chave das variáveis de ambiente.
Você deve passar yarn antes de começar.
Os seguintes scripts estão disponíveis:
yarn start : inicia o(s) Lambda(s) e atende o diretório estático usando Netlify Dev . Importante: yarn build:tw é executado antes de start .yarn build:tw : construa o conjunto completo de utilitários Tailwind CSS (úteis para desenvolvimento), certifique-se de verificar a aparência do seu site ao vivo usando yarn build:cssyarn build : execute netlify-lambda build + Tailwind CSS produção build (remove classes não utilizadas usando PurgeCSS)yarn build:css : compilação de produção Tailwind CSS (remove classes não utilizadas usando PurgeCSS)yarn lint e yarn format : executa o XO, o "Linter JavaScript com ótimos padrões" (consulte github.com/xojs/xo) com ou sem o sinalizador --fix respectivamente
