DEV Community: zivka

How to find repos to contribute to during Hacktoberfest

zivka — Wed, 20 Oct 2021 20:06:38 +0000

I really wanted to be part of Hacktoberfest celebration. Find a repo, understanding the issue and create a pull request that will be merged...

But, it's not so easy when so many people want to do this as well.

So let me share with you a quick tip how to find easily repos that you can contribute to during Hacktoberfest.

In github there is an option for advanced search
I'm using the following filters:

With the labels - hacktoberfest (well, duh)
Written language - javascript (but it's really up to you)
In the state - open
With this many comments - 0 (so no one started to work on them)
With this many stars - > 15 (it's legit repo)

Here's a search link

Good luck...

Hackathon Swags

zivka — Thu, 15 Apr 2021 13:30:33 +0000

Hey,
I'm responsible for the upcoming hackathon swags in my company.

What was the coolest swag you've ever get?
Photo can really help:)

Thanks

Running Puppeteer on Heroku Free Tier

zivka — Tue, 27 Oct 2020 12:03:14 +0000

Heroku is my favorite cloud platform to host my apps.
During Covid-19 I created myself some cool automation(I'm working on another post on it) and was looking for a place to run it for free.

For example, notify me when my restaurant is open in Wolt.

So my requirement was:

Running puppeteer
Easy to create a scheduled task
Easy to deploy
Free

I have experience with Heroku, so it was my first choice.
The free tier is giving you more than 500h per month.

Easy to sync with my GitHub repo already integrated into Heroku.

Scheduled task - There is a simple addon named - Heroku Scheduler which allows you to run commands in scheduled time. Super easy to use, and doesn't require any additional runtime of the instance itself(so we're still in the free tier)

The biggest problem for me was to find the right configuration to run a puppeteer in Heroku.
BTW, if you don't know puppeteer yet. Puppeteer is a Node library which provides a high-level API to control headless Chrome or Chromium over the DevTools Protocol.

I was looking at how to run it, but couldn't find a configuration that worked for me...

So, this is my configuration(it's not necessarily ideal, but it works)

Buildpacks:

https://github.com/jontewks/puppeteer-heroku-buildpack
heroku/nodejs

JS code

const chromeOptions = {
    headless: true,
    defaultViewport: null,
    args: [
        "--incognito",
        "--no-sandbox",
        "--single-process",
        "--no-zygote"
    ],
};
const browser = await puppeteer.launch(chromeOptions);
const page = await browser.newPage();

Use the following flags when you launch puppeteer

"--incognito",
"--no-sandbox",
"--single-process",
"--no-zygote"

Feel free to read more about it...

I hope it solved your problem:)
Good luck

A Gag on a recursion

zivka — Mon, 26 Oct 2020 21:09:09 +0000

Recursion is a method of solving problems in which the solution relies on a simpler instance of the problem.
In order to understand it better press here

Dockerize Create-React-App in 3 minutes

zivka — Sat, 04 Jan 2020 02:17:00 +0000

First of all, I'm pretty excited since it's my first blog post ever... I hope you would like it

Lately I got a full stack home assignment which was included NodeJS micro services in the backend and React for the front-end.

I created a really nice project using Create React App.

If you don't know Create React App, It's creating in less then 20 seconds React App the works Simply by running the following command

npx create-react-app webapp

Ok, once I got my project, I coded my stuff, which was pretty straight forward using the basic templated. Then I wonder, what will be the easiest way to serve this page.
Remember that I need to submit this home assignment.

Since I already have micro-services I had docker-compose file for the rest of the services, so I was looking how to dockerized my React project.

I'm happy to tell you that it's really easy.

Let's say my project name is webapp.

Create two files under the project root folder Dockerfile and .dockerignore.

Copy the content into your files accordingly

Lines 1 - 6 are building the image:

Creating working dir
Copy all the files besides the one in the .dockerignore
Installing react-scripts which is using for serving the project
Running yarn insatll - Get the dependencis
Yarn run build - Build the project in optimized way

Lines 8-12 are the one used to serve the project.
Note the at we are serving this project in port 80.

Let's build this image just run on the Dockerfile folder
docker build -t react-webapp .

And run our container
docker run -it -p 8000:80 react-webapp
Once the container is running, you can open http://localhost:8000 and you'll be able to access the React app running inside the Docker container.

For docker-compose you can copy

That's it...
Now you got a dockerized UI solution in less then 3 minutes.