serverless / blog Goto Github PK

When I follow this blog post everything works until I try to run the application locally with dynamodb.

Then I get the error:
ResourceNotFoundException: Cannot do operations on a non-existent table

The last page of the blog should not show the 'Next' link. Currently it just shows empty pages for 6,7,8 ..... pages.

AWS announces that AWS Lambda now supports .NET Core 3.1

I think that it could be a good idea to include that runtime in the language-runtimes section of the next blog.

https://serverless.com/aws-lambda/#languages-runtimes

Is this transparent for the serverless framework or does it requires some code to build the compatibility of the new runtime?

Announcement: https://aws.amazon.com/about-aws/whats-new/2020/03/aws-lambda-now-supports-net-core-3-1/

As title, if I want to add several screen shots in blog, how to add?

Review the exist blog, they use the s3 link, but how to know the link for the image I will upload.

I would like to preview the blog post before submitting a PR. Is there a way to build it locally?

Open up any blog of the serverless site, the background of code snippets looks different than normal. It shows code in the light background and white texts. Ex. One of the blog.

I'm following https://serverless.com/blog/flask-python-rest-api-serverless-lambda-dynamodb/.

When I run sls deploy I receive the following warning:

$ sls deploy
[...]
Serverless: Warning: Please change "wsgi.handler" to "wsgi_handler.handler" in serverless.yml                                                                             
Serverless: Warning: Using "wsgi.handler" still works but has been deprecated and will be removed                                                                         
Serverless: Warning: More information at https://github.com/logandk/serverless-wsgi/issues/84                                                                             
Serverless: Using Python specified in "runtime": python3.7
[...]

I'm using the python3.7 runtime. I'm unsure if this warning is present with python3.6.

My serverless.yml file.

The link to Github at the bottom of the "CLI Autocomplete" section in the most recent 1.15 blog post double-escapes the encoded characters and ends up going to the default Issues page.

The url currently in the page is this:
https://github.com/serverless/serverless/issues?utf8=%E2%9C%93&q=is%253Aissue%20is%253Aopen%20DX%253A%20

But should be this:
https://github.com/serverless/serverless/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20DX%3A%20

I don't think there's an easy way to fix this in the post (I tried by the spaces in the query kill the markdown url). This would probably need to be changed in whatever is rendering the markdown for the site.

I remember you can customize this behaviour. Used to do it for phenomic docs

"Flash of Lorium Ipsum Text"
When initially loading the blog route, I got a page full of lorium Ipsum text, then a server error, then an error page, then a redirect to the actual live blog.
FireFox dev nightly & Chrome current on Win10, T1 over good WiFI.

I'd assume 'serverless' web pages would be prerendered as static pages with real data, or at least 'above the fold' is prerendered, & more is loaded after the initial.

This should have a license, whatever it may be.

I would like to be able to scroll through a bunch of blog post summaries on the blog home page and ⌘ + Click the titles to bring each up in a new tab; however, for me, this functionality is not working. The page opens in the same tab as the summaries. I am using MacOS and the latest Chrome.

I forked the blog repo thinking it was a simple jekyll website but it's not. And it seems more complicated than I thought to add a page which is not a text.

Anyway, I think it could be useful if the blog has a RSS feed ! Like https://serverless.com/blog/index.xml or https://serverless.com/blog/rss.xml

I tried to access one of your provided link looks be broken or invalid URL. Please provide the correct link that relates to "Need to convert HTML to markdown?"

Right now the pagination is kind of "endless" as I can click on "next" at the bottom of the page for as long as I want. The number in the URL increases that way.

Just like in title, see example in video: https://monosnap.com/file/Q9YNHSgVf4wLnqV8WUaxZGCCNoIFPJ (specifically 0:13, 0:33, 1:23)

What's weird that those pages are sometimes present after being accessed from other link. This happens mostly (or always?) when it comes to links inside articles, not links in navbars or breadcrumbs.

macOS 10.13.5, Google Chrome 69.0.3497

It would be very helpful if the date of creation was shown at the top in each blog post.

https://github.com/serverless/blog/blob/master/posts/2018-05-07-how-create-rest-api-serverless-components.md

I am following the above post, getting an error when running 'components deploy'

BadRequestException: Errors found during import: Unable to create resource at path '/\leads': Resource's path part only allow a-zA-Z0-9._- and curly braces at the beginning and the end. Unable to create resource at path '/\leads\{id}': Resource's path part only allow a-zA-Z0-9._- and curly braces at the beginning and the end. at Object.extractError (C:\Users\jento\AppData\Roaming\npm\node_modules\serverless-components\registry\aws-apigateway\node_modules\aws-sdk\lib\protocol\json.js:48:27) at Request.extractError (C:\Users\jento\AppData\Roaming\npm\node_modules\serverless-components\registry\aws-apigateway\node_modules\aws-sdk\lib\protocol\rest_json.js:52:8) at Request.callListeners (C:\Users\jento\AppData\Roaming\npm\node_modules\serverless-components\registry\aws-apigateway\node_modules\aws-sdk\lib\sequential_executor.js:105:20) at Request.emit (C:\Users\jento\AppData\Roaming\npm\node_modules\serverless-components\registry\aws-apigateway\node_modules\aws-sdk\lib\sequential_executor.js:77:10) at Request.emit (C:\Users\jento\AppData\Roaming\npm\node_modules\serverless-components\registry\aws-apigateway\node_modules\aws-sdk\lib\request.js:683:14) at Request.transition (C:\Users\jento\AppData\Roaming\npm\node_modules\serverless-components\registry\aws-apigateway\node_modules\aws-sdk\lib\request.js:22:10) at AcceptorStateMachine.runTo (C:\Users\jento\AppData\Roaming\npm\node_modules\serverless-components\registry\aws-apigateway\node_modules\aws-sdk\lib\state_machine.js:14:12)

I tried removing {id}, but still get the same error.

Please help. My serverless.yml

....
type: rest-api
    inputs:
      gateway: aws-apigateway
      routes:
        /leads:
          post:
            function: ${createLead}
            cors: true
          get:
            function: ${listLeads}
            cors: true
          /{id}:
            get:
              function: ${getLead}
              cors: true
....

https://serverless.com/blog/building-a-serverless-screenshot-service-with-lambda/
I tried to use the Launch stack button provided in the blog post but the template url does not seem to be working.

https://s3-eu-west-1.amazonaws.com/serverless-screenshots-service/2016-09-23T12:50:03/template.yml seems to not exist - I'm getting

Template validation error: S3 error: The specified bucket does not exist For more information check http://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html