DEV Community: Shunjid Rahman Showrov

ML.NET in Google Colab

Shunjid Rahman Showrov — Wed, 16 Dec 2020 15:48:08 +0000

Today, I was thinking to build and test a classification model using ML.NET. I'm very very curious about new technologies and from my curiosity I asked myself,

"What if I try doing all these things in Colab? Is it even possible?"

From the official documentation of ML.NET I found that there is an option to do all these things from command line using ML.NET CLI.

And guess what? This was as simple as drinking a glass of water 😂. All you need to do is to:

Install .NET Core SDK in Google Colab.
Install ML.NET.
Import dataset.
Use ML.NET CLI to train the model.
Test.

I've added a gist below. You can try directly in colab from the "Open in Colab" badge.

Let's Give it a try 🎉

https://gist.github.com/shunjid/5f633474ba6f4be7db2871fe54e2ef52

Minisauras: A Github action to minify CSS and JS files

Shunjid Rahman Showrov — Mon, 07 Sep 2020 16:42:35 +0000

👋 Hi Everyone,

We are TeamTigers, a group of undergrad students studying Bachelor of Science in Software Engineering. And here is our submission for #ActionsHackathon.

Our Workflow

Minisauras is an open-source CI/CD automation tool based on GitHub Actions that pulls all the desired JavaScript and CSS files from your base branch, minify them and creates a pull-request with a new branch.

How it works

Traverse through a given directory (if not provided, traverse from root), finds all the JavaScript & CSS files within it and it's sub-directories.
Afterwards, Minisauras minify all those files.
Finally, it creates a new branch in your repository, push those changes and creates a pull request that can be merged in your base branch.

Submission Category:

We are submitting this action in following categories:

📌 DIY Deployments (Primary)
📌 Wacky Wildcards (Secondary)

Yaml File or Link to Code

Users' Guideline

Create a personal access token.
Then setup a secret using that personal access token in your desired repository.
Create a workflow. For example: main.yml under (.github/workflows) directory.
In the workflow, provide following things:
- Personal access token. For example: secrets.TOKEN if you set your secret with a name 'TOKEN'.
- The desired directory in which you want to minify CSS and JS files. For example: './' for root and 'src/' for src directory.

- name: minisauras
  uses: TeamTigers/minisauras@v2.0.0
  env:
    GITHUB_TOKEN: ${{ secrets.TOKEN }}
  with:
    directory: 'src/' # all files under 'src' directory

Minisauras Repository :

TeamTigers / minisauras

An open-source CI/CD automation tool based on :octocat: GitHub Actions that pulls all the JavaScript and CSS files from your base branch, minify them and creates a pull-request with a new branch.

Minisauras 🎉

Minisauras is an open-source CI/CD automation tool based on GitHub Actions that pulls all the JavaScript and CSS files from your base branch, minify them and creates a pull-request with a new branch.

How it works

Traverse through a given directory (if not provided, traverse from root), finds all the JavaScript & CSS files within it and it's sub-directories.
Afterwards, Minisauras minify all those files.
Finally, it creates a new branch in your repository, push those changes and creates a pull request that can be merged in your base branch.

Usage

Create a personal access token.
Then setup a secret using that personal access token in your desired repository.
Create a workflow. For example: main.yml under (.github/workflows) directory.
In the workflow, provide following things
- Personal access token. For example: ${{ secrets.TOKEN }} if you set your secret with a name 'TOKEN'.
- The desired directory in which you…

View on GitHub

Additional Resources / Info

💡 Example and output

Here is an example repository that shows the usage of GitHub Action minisauras. You can see there, how minisauras has minified all the CSS & JS files of this repository and sent a Pull Request over there.

TeamTigers / minisauras-example

An example repository to show how to use @TeamTigers/minisauras in a repository.

Below is a pull request sent by Minisauras with changes in some CSS and JavaScript files:

Additionally, in the GitHub Action's console you will see the confirmation of pull request sent by Minisauras.

Our journey 🤗

It was a fun participating in GitHub Actions Hackathon. Usually in academic projects we develop Web or Mobile applications. We've participated in so many national & international Hackathons too. But in #ActionsHackathon we did something really new !!! We've faced so many challenges during the development period. Below is our 'Action Development Life Cycle' (ADLC). Obviously, this journey isn't over yet. We'll still be maintaining this project after the hackathon. So, you can submit issues for improvements and new feature requests at anytime.

Here are some really good resources that helped us building Minisauras:

All 3 Contributors

[Deleted User]

Zubayer HimelFollow

Software engineering student 🧍, front-end developer 💻and designer 🎨

Md Zinnatul Islam MorolFollow

Software Engineer ⭐ | Open Source Contributor 🔥 | Content Writer ✍

Firebase secrets in GitHub actions (Case Study)

Shunjid Rahman Showrov — Tue, 04 Aug 2020 14:21:53 +0000

Make sure you've:

Some experiences in flutter
Basic understanding of Git & GitHub
Working knowledge of setting-up a flutter app with firebase

Before starting

Let's gather some idea about GitHub Actions. GitHub Actions is a CI/CD tool for automation to build, test & deploy your projects on any platform. The idea behind this scenario is you need to create some workflows & running it in a container or, in a virtual machine. Nowadays, flutter-action - a third party utility is mostly used to build & test flutter applications on GitHub actions.

Let's start 😎

You might have worked with google-services.json during the registration of your flutter application in firebase. In most cases, developers refer it into the .gitignore and avoid committing the google-services.json file in GitHub due to security purpose. Avoiding to commit the JSON file is also considered to be a good practice. But doing so raises some problems too. Before diving deep, let's understand the problem through a case study.

Case Study

Your project manager is "Mr. X" who is very strict in terms of testing. Each branches must pass the CI/CD before merging it into the master/main branch. Your team uses GitHub Actions & the workflows of your project runs all the tests whenever a pull request is created. At some point, your app needs to communicate with firebase. In this situation your project needs to deal with google-services.json both in the development environment & the environment of GitHub Actions to pass the tests on each pull requests. Moreover, you can't expose the JSON file in public.

Seems difficult? Let's deal with it 😎

Solution (Step-by-Step)

tar archive: Usually, the google-services.json is located at android/app directory. Next, we will be creating a tar archive of the JSON file using these options:
- c – creates a new .tar archive file
- v – verbosely show the .tar file progress
- f – file name type of the archive file
Creating tar: We will be naming the tar file as services.tar. Run the command below in your project's working directory to create the archive file:
- tar cvf services.tar android/app/google-services.json
.gitignore services.tar: Add the services.tar file in .gitignore. Don't forget to do this !!
Encryption: Before encryption, make sure you've gnupg installed in your system. Run the command below to encrypt the services.tar file. During encryption, it will ask for password which will be used to decrypt the encrypted file. After running the command, there will be a new file in your project's working directory named services.tar.gpg. The command is :
- gpg -c services.tar
Secrets in GitHub: Replace the required part with your project's repository link in the below URL & head over to it:
- https://<YOUR_GITHUB_REPOSITORY_LINK>/settings/secrets/new
- Or, you can find this by navigating to Settings > Secrets > New Secret of your repository.
Create secrets: There will be two parameters required to create a secret. In the first field name, enter the value FIREBASE_SECRET & in the second field value, enter the password you've previously used to encrypt the tar archive file.
Workflow: In your project's working directory, create a directory named as .github. Inside, the .github directory, create workflows directory. Then in the workflows directory, create a file ci.yml. Lastly, paste the code below in ci.yml. Assuming you have a test program test/widget_test.dart. Modify the test command at the end as your needs.

name: CI
on: [pull_request, push]

jobs:

  build:
    name: build and test
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
    - uses: actions/checkout@v1
    - uses: actions/setup-java@v1
      with:
        java-version: '12.x'
    - uses: subosito/flutter-action@v1
      with:
          channel: 'beta'
    - run: flutter pub get
    - name: Build
      run: |
        mkdir $HOME/private
        gpg --quiet --batch --yes --decrypt --passphrase="$FIREBASE_SECRET" \
        --output $HOME/private/services.tar services.tar.gpg
        tar xvf $HOME/private/services.tar
        flutter build appbundle
      env:
        FIREBASE_SECRET: ${{ secrets.FIREBASE_SECRET }}
    - name: Test
      run: flutter test test/widget_test.dart

Understanding the ci.yml

on: [pull_request, push]: This workflow will work whenever someone push or, make a pull request.
In the steps we are:
- Using required utilities.
- Running flutter pub get command to install required packages defined in pubspec.yaml.
- Decrypting the services.tar.gpg by using the password we have stored in the secrets FIREBASE_SECRET.
- Building & running the tests of our application on GitHub actions.

References:

Last but not the least

To err is human. If you find any mistakes here or, any sentence/word/code-snippet which can be corrected or, improved then feel free to knock me on Twitter. If you find this helpful then share it to help others too.