DEV Community: Chetan Dhongade

Setting Up a Custom Domain with AWS Amplify Without Using AWS Route 53

Chetan Dhongade — Mon, 17 Feb 2025 06:18:54 +0000

1) Make sure you have your site deployed on AWS Amplify. For demonstration purposes, I have deployed a simple index.html page with the content shown below.

2) Go to the Hosting section in the sidebar, where you will see the Custom Domain option. Click on it, and then click on Add Domain.

3) On the Add Domain screen, enter the domain or subdomain name. After that, select Manual configuration and click on the Configure domain button.

4) On the next screen, keep everything at the default settings and click on Add Domain.

5) Wait for 5 minutes, and you will receive 3 CNAMEs that you need to set in your domain's DNS manager.

6) My domain registrar is Porkbun, and I have set the CNAMEs as follows:

7) You may need to wait a few minutes for DNS propagation, depending on your domain registrar. In my case, it took just 3 minutes.

8) After that, the domain activation process will begin, and within 7-10 minutes, you will be able to visit the site using your custom domain. In my case, it was https://app.davesidewalk.com.

Once the domain activation is complete, your custom domain will be fully functional. You can now access your site seamlessly with your new domain. If you face any issues, ensure the DNS settings are correct and allow time for propagation. Enjoy using your custom domain with AWS Amplify!

Managing Docker Contexts to Prevent Image Disappearance and Permission Issues

Chetan Dhongade — Tue, 29 Aug 2023 03:36:22 +0000

Introduction

In the world of containerisation, Docker has become an integral tool for developers to manage and deploy applications seamlessly. However, occasional hiccups in the Docker environment can lead to perplexing issues, such as vanishing local Docker images and unexpected permission requirements. In this article, we'll delve into a recent experience that sheds light on this phenomenon and explore the solutions to mitigate such occurrences.

The Mysterious Disappearance

Imagine a scenario where you've just installed Docker Desktop, and suddenly, your locally built Docker images have vanished into thin air. Additionally, executing basic Docker commands prompts an unexpected request for sudo privileges. Without elevated permissions, an error message resembling the following surfaces:

"Cannot connect to the Docker daemon at unix:///home/xyz/.docker/desktop/docker.sock. Is the Docker daemon running?"

Perplexing as this may seem, the root cause of this anomaly lies in Docker's inherent architecture and its management of different contexts.

Docker Context: Unveiling the Culprit

Docker Desktop, upon initiation, crafts a dedicated context to serve as a target for the Docker Command-Line Interface (CLI). This context is set as the active one for the CLI's use. This seemingly innocuous process serves a vital purpose: it prevents conflicts with a local Docker Engine that could potentially be operational on the Linux host and utilizing the default context.

The purpose of this context isolation becomes apparent during shutdown. When Docker Desktop closes, it restores the previously employed context to ensure a smooth transition between different Docker environments.

Solving the Mystery: Unveiling the Solution

Now that we've dissected the cause, let's unravel the solution. The Docker website itself offers insights into this quandary, suggesting a course of action to restore normalcy. If you find yourself grappling with Docker images mysteriously disappearing and unexpected permission requirements, consider these steps:

One initial remedy is to add yourself to the 'docker' group using the following command:

User Group Addition:

sudo usermod -aG docker $USER

Context Exploration:

To comprehend the current context at play, utilize the command:

docker context list

Context Switching:

When you are not using docker desktop if you suspect that Docker Desktop might have altered your context, manually switch back to your original context using:

docker context use <context-name>

Python and Google Drive: How to List and Create Files and Folders : 2023

Chetan Dhongade — Sun, 14 May 2023 10:47:43 +0000

Google Drive is a popular cloud storage service that allows users to store, share, and access files from anywhere with an internet connection. With the help of the Google Drive API, developers can integrate Google Drive functionality into their applications, allowing users to perform a wide range of file operations programmatically. In this article, we'll explore how to use Python to interact with Google Drive, specifically focusing on listing files, creating files, and creating folders.

Project setup:

On the Google Cloud Dashboard dashboard start by creating new project, in the below image I created the project with name 'test-drive'

After the project is created you need to select it.

Enable the google Drive API for the project

Create the credentials by selecting the service account for the project.

Name the service account

Give editor access to it

click Done to finish creation.

Select newly created service account and create new keys selecting Json option from prompt. Put the downloaded file in the project directory.

Rename the file "credentials.json".

Create the New folder inside your google drive account where you want to create the file. I have created the folder with name "Test Drive". Note down the Id of the folder from the URL we need it in the script.

Share this folder with the service account email address.

Below given script create the folder inside the shred folder Name "Test Upload" , then it upload the file "image.webp" inside of that folder. And finally it list all the files inside of that folder.

Link to code with requirements.txt https://gist.github.com/binary-ibex/eea137f2794fe3161959e77c2b34ea1e

from googleapiclient.discovery import build
from googleapiclient.http import MediaFileUpload
from google.oauth2 import service_account



# Replace 'FOLDER_NAME' with the name you want to give your new folder
folder_name = 'Test Upload'


# setup google drive
credentials = service_account.Credentials.from_service_account_file(
        'credentials.json', scopes=['https://www.googleapis.com/auth/drive']
    )
service = build("drive", "v3", credentials=credentials)
folder_metadata = {
    'name': folder_name,
    "parents": ['1Wsp5VthsToAWA3eF9wXCNcZPcL_JZFAi'],
    'mimeType': 'application/vnd.google-apps.folder'
}

# create folder 
new_folder = service.files().create(body=folder_metadata).execute()


#upload file inside the folder
file_metadata = {'name': 'image.webp', 'parents': [new_folder['id']]}
media = MediaFileUpload('image.webp')
file = service.files().create(body=file_metadata, media_body=media).execute()

# list the file inside of the folder
results = service.files().list(q=f"'{new_folder['id']}' in parents", fields="files(name)").execute()
items = results.get('files', [])
print(f"Files inside the folder , {items}")

Output of the code

Files inside the folder , [{'name': 'image.webp'}]

As you can see we have the folder with name "Test Upload" and "image.webp" file inside of it.

Short Code explanation

You can see my project structure in image below.

First we setup the google drive providing the path path of our credentials.json file

credentials = service_account.Credentials.from_service_account_file(
        'credentials.json', scopes=['https://www.googleapis.com/auth/drive']
    )
service = build("drive", "v3", credentials=credentials)

After that we create the folder, but to do that we need the Id of the shared folder, here we will use the Id of the shared folder we note before. Remember weather you are creating the file or folder, we need to specify the metadata for it

folder_metadata = {
    'name': folder_name,
    "parents": ['1Wsp5VthsToAWA3eF9wXCNcZPcL_JZFAi'],
    'mimeType': 'application/vnd.google-apps.folder'
}

# create folder 
new_folder = service.files().create(body=folder_metadata).execute()

After specifying the metadata to create the folder we execute the command

# create folder 
new_folder = service.files().create(body=folder_metadata).execute()

Now we will upload the local image file inside of newly created folder. We will use the MediaFileUpload class provided by the google client. For the parent we will use the ID of the newly created folder.

#upload file inside the folder
file_metadata = {'name': 'image.webp', 'parents': [new_folder['id']]}
media = MediaFileUpload('image.webp')
file = service.files().create(body=file_metadata, media_body=media).execute()

We can list the file using the below code. Note in the below code 'fields' parameter is use to specify selective fields we want in response otherwise google will return lot of data.

# list the file inside of the folder
results = service.files().list(q=f"'{new_folder['id']}' in parents", fields="files(name)").execute()
items = results.get('files', [])
print(f"Files inside the folder , {items}")

That's it.

Simple Drive App using Appwrite and Flutter

Chetan Dhongade — Thu, 12 May 2022 17:53:39 +0000

Overview of My Submission

This is the simple flutter app where users can upload there document on cloud. App has the login and signup feature.

Project setup

Install appwrite in your computer. Follow instruction for your respective operating system. I use Ubuntu OS.
https://appwrite.io/docs/installation.
After installation and setup you can able to access the appwrite dashboard. As you can see in the below image I have created two projects. Similarly create project name it anything you want. I had named it simpledrive.

Add the flutter platfrom. As you can see in below image, I will skip rest of the platfrom setting and filled up detail for Android only.
create storage bucket, with permission settings given in image below
create database to store the relation of the userid, corresponding documentid.

with attributes
Setup the config file in the flutter project according to your setup
Now run flutter and witness magic with your own eyes.

Submission Category:

Mobile Moguls

Link to Code

binary-ibex / simple_drive

flutter app using the appwrite as file storage backend

simple_drive

A new Flutter project using appwrite as the backend.

Description

This is the simple flutter app where users can upload there document on cloud. App has the login and signup feature.

#App Images

View on GitHub

Screenshots

Image if the uploaded files

Image of the database entries

Django basic authentication

Chetan Dhongade — Mon, 10 May 2021 06:37:57 +0000

The Django framework makes it very easy to implement in the basic authentication, let me show you one quick and simple example of it.

let’s start by making the project

django-admin startproject simple_authentication_project

Create “myapp” inside of it

python manage.py startapp myapp

We will make the three views inside of myapp .i.e. login_page , home_page, logout_page

Login Page

# login page
def login_page(request):
    if request.method == "POST":
        user = authenticate(
            username=request.POST["username"], password=request.POST["password"]
        )
        if user:
            login(request, user)
            return redirect(home_page)
        else:
            return render(request, "login.html", {"error": "Invalid login"})
    else:
        return render(request, "login.html", {"error": ""})

In the login view all we have to do is to take the username and password from the simple html form and then pass to the function “authenticate()” with the request object. If the user exists authenticate function will return the user object and if not it will return None. If we get a user object all we have to do is to pass that user object to the “login()” function which will log the user.

Home Page

# home page
@login_required(login_url="/login")
def home_page(request):
    return render(request, "home.html", {})

We have given the login_required decorator to the home page view so that only the login user is able to see the page.If the user is not logged in,then it will redirect him to the login page.

Logout Page

# logout page
@login_required(login_url="/login")
def logout_page(request):
    logout(request)
    return render(request, "logout.html", {})

Logout view is very simple. All we have to do is to pass the request object to it and it will log out the logged in user.

And that’s it..easy-peasy, isn't it? But wait what about “login.html”, “logout.html”, and “home.html”.
Don’t worry there is nothing special about them to explain. I have put the link to github below. Only thing you have to remember is to put the line csrf_token inside the form whenever you are making the “POST” request.

Let's test our simple application,

start by creating user, for the simplicity we will work with superuser for now,

First migrate

python manage.py migrate

create super user

python manage.py createsuperuser

finally runserver

python manage.py runserver

Now our server is running head to the browser and go the address 'localhost:8000'.

DEV Community: Chetan Dhongade

Setting Up a Custom Domain with AWS Amplify Without Using AWS Route 53

Managing Docker Contexts to Prevent Image Disappearance and Permission Issues

Python and Google Drive: How to List and Create Files and Folders : 2023

Project setup:

Short Code explanation

Simple Drive App using Appwrite and Flutter

Overview of My Submission

Project setup

Submission Category:

Link to Code

binary-ibex / simple_drive

flutter app using the appwrite as file storage backend

simple_drive

Description

Screenshots

Django basic authentication

Login Page

Home Page

Logout Page

Login page

Home Page

Logout Page

Link to github Repository