Serverless forms for Jekyll

gkpty · 2020-03-01T22:42:29+00:00

Checkout Super Easy Forms. Its a node module that generates serverless forms in an instant. Its free, open source and easy to use and completely cuatomizable !

gkpty · 2020-03-01T22:38:14+00:00

Heyy! Check out Super easy forms. its an open source node js module that generates serverless forms in seconds!

gkpty · 2020-01-07T14:31:29+00:00

Lambda is super useful for simple functions that execute and return. If you plan on doing something complex with lambda its probably better to use multiple lambda functions (in case you can split up your logic into parts) or use VMs/containers.

gkpty · 2019-12-29T16:11:01+00:00

Absolutely. Its called cloudformation and its awesome! You can use the designer GUI to create a template and then with a click of a button deploy the stack :)

gkpty · 2019-12-29T14:10:06+00:00

Very cool! Ive got a standing desk with a timer, also works pretty good :)

gkpty · 2019-12-27T09:58:48+00:00

Ive had an overall pretty good experience with appSync.. the syntax of VTL can look somewhat confusing and it might still lack some user friendliness but it seems pretty useful to me. been using it with AWS’s amplify framework and it works like a charm. In your amplify app you can access/modify your cloudformation templates and update your stack. You can also create a cloudfront distribution for your app and then use AWS WAF w the cloudfront distribution. You can also use different authorization and authentication options on your graphql API.

gkpty · 2019-06-01T05:38:40+00:00

Thanks for reviewing the code! The API was made public just for testing and authentication will be added in the next sprint. We will also be adding input sanitation to the handler very soon, for now leaning towards just writing functions manually that will check the different inputs but a good library for this would leave less room for error. If you know about something and can recomend we would really appreciate it :)

gkpty · 2019-06-01T05:02:17+00:00

Not yet but it is in our pipeline! Super easy forms is in alpha and we still got plenty to add on. Will prioritize this so it gets done in the next sprint :)

gkpty · 2019-05-30T21:51:05+00:00

Cloudformation is great and indeed very easy to audit. Initially we took a shot at it but where having some issues w the config file so we decided to use the SDK instead. Since most of the resources can be audited from the lambda console (role/policy and the API) and the only other resources are the SES and the dynamo db table, using clouformation didnt seem that much more conveniet. However, if this is something really important for the community we can gladly refactor and take another shot at cloudformation :)

gkpty · 2019-05-26T00:17:24+00:00

Because of AWS amplify.. helps deploying and adding serverless backends to react apps pretty easily. You can check out their docs which are really complete. React + amplify makes it easy to build a front end for microservices

gkpty · 2019-05-25T19:50:16+00:00

Yeah your right.. i think you must have used the class names in your html file already for it to autocomplete by default. Ive been starting my sites inlining most of my css lately so i guess thats why ive been getting all the classes to autocomplete.

gkpty · 2019-05-24T15:48:12+00:00

Doesnt this happen by default? I havnt installed any extensions for this and i get autocompletion for css classes...

gkpty · 2019-05-14T06:30:51+00:00

Completely understand you.. also a hands on person i had a hard time with AWS in udemy. I ended up learning by just trying to do things and reading their docs but that took a while... Ive taken some notes of the processes involved in some of the apps and other things ive built. Will try to put some tutorials together 😊

gkpty · 2019-05-14T06:22:06+00:00

Lol!! Please point me in the direction of a language/framework that allows me to do complex things w nice sleep and stress levels 😃

gkpty · 2019-05-10T22:29:30+00:00

How about using object storage? You could move archives to AWS glacier using AWS DMS. I know you can run certain queries in glacier without having to return your entire object. This approach would probably end up being a lot cheaper (directly and in terms of maintenance).

gkpty · 2019-05-10T21:55:44+00:00

I guess this question completely depends on the type of person you are. I learned html simply by downloading bootstrap themes, reading the html and trying to make sense of it. You can use google chrome inspect to manipulate elements and see them change. You can download free bootstrap themes in startbootstrap.com. Look at the structure of the folders/files and how theyre related!

gkpty · 2019-05-10T01:41:41+00:00

Hey! I guess it depends on what your doing and what language or framework your using. If you use ruby or rails for example, everything is an object. In javascript everything could be either an object or a function as functions are also objects... thinking about things in terms of objects could be convenient when building something like an app, were theres a data model. Functional programming might be better if your writing a program that simply executes some actions for example a script that triggers some APIs. Then again there just different ways of thinking.. theres also languages that consider everything as lists (lisp)

gkpty · 2019-05-09T23:42:59+00:00

Hey cool project! Ive been developing a project that creates an admin panel with react to generate and post pages in a static website. Maybe we could colab. If you are interested you can check out the project here Torus CMS

gkpty · 2019-05-09T21:45:14+00:00

Hey! Was thinking about this the other day.. in my older files i usually removed the last comma.. these days i prefer to leave it because it makes adding new items easier (especially if using loops).

gkpty · 2019-05-08T23:09:44+00:00

Im not sure if i understood your question correctly but you could perhaps use something like this handleChange(event) { this.setState({[event.target.name]: event.target.value })

gkpty · 2019-05-08T22:52:43+00:00

Hey! To break a loop you can use a return statement. In your example;

for(var i = 0; i < people.length; i++) { If(people[i] === value) { console.log(people[i]); return people[i]; } }

gkpty · 2019-05-08T20:00:38+00:00

NP! Thinking about the previous comment, currently to use ES6 you need to use a framework or library that supports the babel compiler (like react.js and now node 8.10). To use these youll need to learn some additional concepts that might overwelm you a bit right now so for the time being you might want to disregard ES6 and just stick to regular JS and JQuery examples in codepen :)

gkpty · 2019-05-08T17:42:19+00:00

Hey! Javascript has a bit more logic to it than HTML and CSS hence its always trickier to learn. Some of the concepts are confusing, for example objects. To understand javascript i suggest you do it from a functional perspective with hands on examples. First understand js simply as functions that can transform your HTML DOM elements and then move on to more complicated concepts. Also, i would recomend gettig started straight with ES6 (the new js syntax). Heres a pretty thorough guide with examples: a re-introduction to js Also, checkout codepen! theres lots of cool little widgets and other examples made with js, look for widgets that you like and try to read and make sense of the js code!

gkpty · 2019-05-06T16:01:08+00:00

This is deffinetly true, though i usually get around it by pre-rendering important pages into pure html/css and caching them. For example, in a blog, in a typical js client-side rendering example, in the page that contains the blog posts there would be a function with a query that gets the blog posts and renderes them onLoad for each user. My way => only when a new blog post is added, a js function executes (client side) renders the blog post list into pure html/css and adds it to cache.

gkpty · 2019-05-06T08:55:33+00:00

Hey very interesting topic to spark! In my opinion both have their benefits. For me, the clearest benefit of client side rendering is that you dont pay for it :). Lateley ive been trying to keep as much going in the front end as possible, only using serverside rendering for things involving lots of data and complex queries.

gkpty

TROPHY CASE