A list of CLI generators, starter kits / boilerplates and toolkits to kick start your Next.js apps.
This gist aims to provide a simple solution for managing Heroku Review Apps with GitHub Actions due to the security incident that continues to disrupt Heroku's GitHub integration. Watch the demo to learn more.
.github
├── workflows
│ ├── heroku_review_app_create.yml
| # | |
| # Github Actions for Serverless Framework | |
| # | |
| # Create AWS_KEY and AWS_SECRET secrets in Github repository settings | |
| # If you're using env.yml file, store its content as ENV Github secret | |
| # | |
| # Master branch will be deployed as DEV and every new tag starting with "v**" (e.g. v1.0, v1.2, v2.0, etc) will be deployed as PROD | |
| # | |
| # Learn more: https://maxkostinevich.com/blog/how-to-deploy-serverless-applications-using-github-actions/ | |
| # |
A curated list of arrrrrrrrr!
| const Slack = require("slack-node"); | |
| // Load the AWS SDK for Node.js | |
| const AWS = require("aws-sdk"); | |
| // Set the region | |
| AWS.config.update({region: process.env.REGION}); | |
| // Create EC2 service object | |
| var ec2 = new AWS.EC2(); | |
| function capitalizeFirstLetter(string) { |
Ok. I'm going to list off some ideas for projects. You will have to determine if any particular idea is good enough to include in a portfolio. These aren't creative ideas. They likely already exist. Some are way too advanced while others are simplistic.
I will recommend to post any project you make to github and make a github project page for it. Explain in as much detail as possible how you made it, how it can be improved etc. Document it.
If you pick an advanced idea, setup a development roadmap and follow it. This will show some project management skills.
Another piece of advice for those who are design challenged. Use different front end frameworks and use different themes for those frameworks to provide appealing designs without looking like yet another bootstrap site.
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <title>A simple clock</title> | |
| </head> | |
| <body translate="no" > |
Brought to you by Headjack
FFmpeg is one of the most powerful tools for video transcoding and manipulation, but it's fairly complex and confusing to use. That's why I decided to create this cheat sheet which shows some of the most often used commands.
Let's start with some basics:
ffmpeg calls the FFmpeg application in the command line window, could also be the full path to the FFmpeg binary or .exe file
| var aws = require('aws-sdk'); | |
| var elastictranscoder = new aws.ElasticTranscoder(); | |
| function basename(path) { | |
| return path.split('/').reverse()[0].split('.')[0]; | |
| } | |
| exports.handler = (event, context) => { | |
| console.log('Received event:', JSON.stringify(event, null, 2)); | |
| var key = event.Records[0].s3.object.key; |
| # Set the command-line arguments to pass to the server. | |
| ARGS='-web.listen-address=:9100 -collector.diskstats.ignored-devices="^(ram|loop|fd)\\d+$"' | |
| # Prometheus-node-exporter supports the following options: | |
| # -collector.diskstats.ignored-devices="^(ram|loop|fd|(h|s|v|xv)d[a-z])\\d+$": Regexp of devices to ignore for diskstats. | |
| # -collector.filesystem.ignored-mount-points="^/(sys|proc|dev)($|/)": Regexp of mount points to ignore for filesystem collector. | |
| # -collector.ipvs.procfs="/proc": procfs mountpoint. | |
| # -collector.megacli.command="megacli": Command to run megacli. | |
| # -collector.ntp.server="": NTP server to use for ntp collector. | |
| # -collector.textfile.directory="": Directory to read text files with metrics from. |