Skip to main content

Going Serverless!

So most of you have probably heard about this particular concept - "Serverless".  I can't say I completely get the name of it, there is a server that is running it, the main difference is it only runs for the length of it to take to complete the computing of the function.  As far as the big players go - I generally have all of my stuff running out of Amazon - so for the purpose of this article, this is what I'm referring to.

Lambda is the service of AWS where you can run your serverless functions.  Now sadly for us PHP developers, it does not support natively support PHP and until now, I haven't found a simple and easy to grasp guide without the need to use some elaborate framework that sits on top of it.  Until now...

Be sure to take a look in to this guide from Amazon.  I was genuinely impressed.  The one thing it left out was that I got about up to the very end when I found my functions could not be invoked properly, and the reason being is that my particular AMI I had selected was not quite compatible.  The support guy's said to try the instance called ami-035b3c7efe6d061d5 - Look for the name "Amazon Linux AMI (HVM / 64-bit)" in the Community Marketplace.

 Further to this, there is a very simple guide on how you can hook your lambda functions to your S3 buckets here.

 Happy Coding!
Labels:

Comments

Post a Comment

Popular posts from this blog

Running NodeJS Serverless Locally

 So it's been a long time, but I thought this was a neat little trick so I thought I'd share it with the world - as little followers as I have.  In my spare time I've been writing up a new hobby project in Serverless , and while I do maintain a staging and production environment in AWS, it means I need to do a deployment every time I want to test all of the API's I've drafted for it. Not wanting to disturb the yaml configuration for running it locally, I've come up with a simple outline of a server which continues to use the same configuration.  Take the express driven server I first define here: And then put a index.js  in your routes folder to contain this code: Voila! This will take the request from your localhost and interpret the path against your serverless.yml and run the configured function.  Hope this helps someone!
Post a Comment
Read more

question2answer Wordpress Integration

 Today I want to journal my implementation of a WordPress site with the package of "question2answer".  It comes as self-promoted as being able to integrate with WordPress "out of the box".  I'm going to vent a small amount of frustration here, because the only integration going on is the simplicity of configuration with using the same database, along with the user authentication of WordPress.  Otherwise they run as two separate sites/themes. This will not do. So let's get to some context.  I have a new hobby project in mind which requires a open source stack-overflow clone.  Enter question2answer .  Now I don't want to come across as completely ungrateful, this package - while old, ticks all the boxes and looks like it was well maintained, but I need every  page to look the same to have a seamless integration.  So, let's go through this step by step. Forum Index Update This step probably  doesn't need to be done, but I just wanted to mak...
Post a Comment
Read more

Getting all deltas from Auth0

Before I get in to the solution of this article, let me tell you how it started and fill you in on the problem that arose.  I wrote a procedure to get daily deltas of users - those of which who had created/updated their account on the given day (and including the day before for good measure on the GMT timestamp).  The simple search criteria was just the following: updated_at:[yyyy-mm-dd TO yyyy-mm-dd] Simple, right?  the []'s being the dates are inclusive, while using {} would mean exclusively.  Auth0 lets you mix these on either side depending on your use.  While this is all well and good, Auth0 will limit the number of results (even with paging) to 1000 only. So, your first option is that you could have your procedure create a user export job, and then parsing through the results and eliminating those which do not meet your updated_at search criteria.  I can tell you first hand that eventually the amount of users will just get to be too much and cumb...
Post a Comment
Read more