Forem: Goon Nguyen

Introducing DigiCord: The Ultimate All-in-One AI Discord Bot

Goon Nguyen — Sun, 28 Apr 2024 10:11:19 +0000

Are you tired of juggling multiple AI tools and subscriptions? Do you want to experience the power of AI in a single, convenient platform? Look no further than DigiCord, the revolutionary AI Discord bot that's changing the game.

What is DigiCord?

DigiCord is an all-in-one AI Discord bot that integrates over 40 Large Language Models (LLMs), including GPT-3.5, GPT-4, Claude, Gemini Pro 1.5, Meta Llama 3, Mistral, MythoMax, DataBrick, and many more. This means you can access a wide range of AI capabilities in a single bot, without the need for multiple subscriptions or platforms.

How to Use DigiCord

Using DigiCord is easy and intuitive. Simply tag the bot's name @JojoAI to start chatting. You can also use the following commands to customize your experience:

/ask to select a specific LLM or assign a custom role
/prompt to input a long, complex prompt and customize further
/vision to analyze images and generate code for UI designs
/draw to create stunning art using Leonardo.AI
/summarize to summarize content, web pages, or YouTube videos

And many more helpful commands.

Why I Built DigiCord

I built DigiCord to address the limitations and costs of existing AI tools. As an individual, I found the basic package of ChatGPT to be expensive, with limitations on requests and difficulty in coordinating with team members. With new AI models emerging all the time, it's not feasible to subscribe to each one individually. That's why I created DigiCord - to bring all these capabilities together in one convenient platform.

Benefits of DigiCord

By using DigiCord, you can:

Save costs: Our company of 40 people reduced their costs to $20-$30 per month (instead of $200 for 10 ChatGPT accounts as before), and individual users can only spend around $5-10 USD/month.
Improve collaboration: DigiCord integrates with other useful tools, making it easier to work with your team.
Access a wide range of AI capabilities: With over 40 LLMs integrated, you can experiment with different models and use cases.

Get Started with DigiCord

Ready to try DigiCord? Follow these steps:

DM the bot: https://zii.vn/3UXZU703
Invite to your server: https://zii.vn/HVGw3GqO
Join our community server: https://zii.vn/digicordserver

✨As a special offer, use the code "DIGICORDSOFTLAUNCH" at LemonSqueezy checkout to receive 10% off your subscription.

We also offer "Free Trial" option so you can give it a try!

New users will receive $1 credits (around 500 AI requests) for FREE TRIAL. Don't miss out on this opportunity to experience the power of DigiCord for yourself.

👉 Check out my website as well: https://DigiCord.Site/?ref=devto

UX is becoming less important in the age of AI?

Goon Nguyen — Wed, 24 Jan 2024 04:52:27 +0000

The greatest invention of Sam Altman or OpenAI is not AI itself, but the natural conversational experience they created.

AI has been around for decades, and perhaps those who have been involved in the industry from the early days, when they first met ChatGPT, may have thought, “This is normal, I can do it too.” That’s right, what they couldn’t do was the idea of humans being able to talk to machines, just like the way humans talk to each other on the internet.

Humans are social creatures, and language and communication are the keys that make us superior to all other species on Earth.

To say this, you have to click your tongue, a simple-looking idea that is actually so amazing!

Will UX disappear?

In the software industry, UI & UX are of paramount importance.

Humans love beauty, and a software with a beautiful UI (user interface) will easily win the favor of users. UI is in the “look” part, not the “communication” part, so UI will still be there.

But UX is quite different. The role of UX emerges when users notice the difference between two apps that are equally beautiful, but one side is easy to use, and the other side is “some-kind-of-stupid”. UX shows the importance of communication between humans and software/computers. And it also makes some software developers stand out from the rest.

But with the advent of AI, the way humans interact with computers will change a lot.

Let’s try to answer this question: “Why are CMS, CRM, CDP software, project management tools (todo, kanban, …) very useful but very difficult to introduce into businesses? Kind of like everyone sees it as important, the company that applies it successfully will see clear results, but to put it into the process requires a lot of effort from the leadership and cooperation from the departments.”

Because they look complicated, right?

For an accountant, a manager who often goes to the field (works outside the computer more than on the computer), or a business leader, opening an application with a row of columns, buttons above and below, pages this page that, groping, … wow, this is clearly a very hard job!
Instead of doing those things themselves, they choose to ask someone more knowledgeable to query or perform the tasks they want.

Now, try replacing the phrase “more knowledgeable person” above with “AI”.

Voilà!

“How many customers have birthdays this month? Send them a birthday promotion.”
“What was the revenue for this month of last year?” -“How are the business results of the new product line? Propose optimization?”
“Remind customers to use vouchers that are about to expire!”

Even if automation is applied, AI can also proactively notify and propose to the relevant people.

All are wrapped in “conversational snippets” — query and command — much simpler! (and does not encounter the barriers of “emotion” and “transparency” compared to doing it with humans)

In conclusion

UI & UX are still there and play an important role in product design, AI can’t replace UX either, because UX is a job that requires human-centric empathy, humans don’t even understand humans, let alone machines, AI is still a long way from reaching the level of “empathy”. But “optimizing UX” will no longer be the top priority, and will be forced to give way to the new king named AI.

Looking for useful AI products?

Goon Nguyen — Tue, 10 Oct 2023 16:57:44 +0000

We're living in the era of AI, hundreds of AI-powered products released every day, so I create a place to share and upvote for the most useful AI products, we don't have to dive into the AI sea anymore.

https://topranking.ai

Let build this place together! Because, life is all about sharing, my friends.

P/S: what do you think should be improved? 🤔

Speed test building Next.js T3 App with Github Actions, Circle CI, Vercel & Diginext

Goon Nguyen — Mon, 03 Jul 2023 06:14:20 +0000

Since when I started building my own open-source cloud resouce platform - Diginext, although I had never done a benchmark, I kept thinking that I had built it for personal purposes only, to serve my teams and enhance their daily workflow. However, I must admit that I was not confident until today, the tests were supprising myself.

() If you wanna check if I made incorrect configurations, here is the source code: https://github.com/digitopvn/t3-app-starter*

Now, let’s get the party started!

First time, with no cache:

1. Docker Engine on my Macbook M1 Pro

Took 4 mins and 33 secs (~273 seconds)

(with docker system prune and docker volume prune excecuted before running docker buildx)

2. Github Actions

Finished in 3m 56s

3. Circle CI

They said they are nearly 2x faster than Github Actions, let’s see…

Huh?… 5m 48s

…not like the advertisement.

This is the .circleci/config.yml

version: 2.1

jobs:
  build-and-push:
    docker:
      - image: cimg/base:stable
    steps:
      - setup_remote_docker:
          version: 20.10.11
          docker_layer_caching: true
      - checkout
      - run: docker login -u "$DOCKER_USERNAME" -p "$DOCKER_PASSWORD"
      - run: docker buildx build --push -t digitop/t3-app-starter:circleci-v1 .

workflows:
  version: 2
  docker-build-push:
    jobs:
      - build-and-push

4. Diginext

Not so bad… 3m 11s! (even faster than my macbook)

Triggered by dx build command.

5. Vercel

Is the winner with… 1m 3s (incredible!)

I guess because Vercel platform doesn’t have to spin up a Docker container, they just built the Next.js app natively, that’s why it didn’t take a lot of time for Docker cold start.

Alright, let’s do another round!

Second build, cached!

Notes that I changed nothing, just built them again.

1. My macbook M1 Pro

Great! when the cache hit, it only took 39 seconds

2. Github Actions

Wait… 4m 10s ?

(WTF? it’s even slower than the first run?)

I followed this guide: https://docs.docker.com/build/ci/github-actions/cache/

I tried again a few time but sometime it was fast (~1min), sometime it was not (>3mins). It seems like the cache didn’t work or the workflows are just not stable. Not sure why.

3. Circle CI

Well, about 2x faster than the first run, completed in 2m 40s

5. Vercel

Again, very impressive: 38 seconds (~40% faster than the first run)

4. Diginext

Woohoo… 21 seconds! When the cache hit, Diginext is the winner with ~90% faster than the first run.

This is so surprising… even with me, its creator.

Summary

GitHub Actions and Circle CI were originally designed for purposes other than building apps. Considering their primary functions, it's understandable that the current build speed is deemed acceptable.

On the other hand, the immensely popular Vercel is gaining significant traction. As a frontend cloud platform, it supports a wide range of the most popular frontend frameworks, and there's a good chance they will expand their support to include backend frameworks in the future.

In contrast, Diginext is an open-source cloud platform that caters to any types of applications. Its philosophy is encapsulated in the motto, “if it can run on your computer, it can run on Diginext”, and the platform's mission revolves around “making coding great again” by simplifying app deployment and cloud resource management.

I appreciate the boost in my confidence as these tests have helped me reconsider the value of Diginext. While it may be deemed unacceptable to compare it directly with renowned platforms like Vercel, it's encouraging to think that if it proves beneficial for my teams, it could potentially benefit the wider developer community as well.

Update: As I pen this article, I observe that Render and Railway are currently making strides towards the same objectives as Diginext. Witnessing their well-established services and robust financial backing does dampen my spirits slightly. However, I refuse to give up. I firmly believe that with the advantages of an open-source platform, Diginext can deliver value to the developer community, particularly to those of us who are financially challenged— much like myself, haha.

“GitDevSecOps”

Goon Nguyen — Fri, 23 Jun 2023 03:42:48 +0000

You probably heard DevOps, GitOps and even GitSecOps. If not:

DevOps

DevOps is a software development approach that emphasizes collaboration and integration between software development (Dev) and IT operations (Ops). It aims to streamline the software delivery process by automating and improving communication, coordination, and efficiency among development teams, operations teams, and other stakeholders. DevOps practices involve continuous integration, continuous delivery/deployment, infrastructure automation, and monitoring, enabling faster and more reliable software releases.

GitOps

GitOps is an operational framework that leverages the Git version control system to manage and automate the deployment and operation of infrastructure and applications. It promotes the idea of declaring desired states for infrastructure and applications in Git repositories, and using Git workflows for managing changes and updates. With GitOps, the entire system's configuration and deployment details are versioned, auditable, and reproducible, enabling easy collaboration and traceability.

GitSecOps

GitSecOps, on the other hand, extends the GitOps principles to incorporate security practices into the software development and deployment lifecycle. It emphasizes integrating security into the GitOps workflows, ensuring that security controls and best practices are applied throughout the software development process. GitSecOps involves implementing security checks, vulnerability scanning, code analysis, and access controls as part of the GitOps pipeline to maintain a secure and compliant software environment.

Why is one or another?

Choosing one approach over another depends on the specific needs and goals of an organization. DevOps is a broad methodology that focuses on collaboration and automation between development and operations teams. GitOps extends DevOps by using Git for managing infrastructure and application configurations. GitSecOps further enhances DevOps by integrating security practices into the development and deployment process. The choice between these approaches may depend on factors such as the organization's size, existing infrastructure, security requirements, and the level of automation desired.

"Git-Dev-Sec-Ops"

By taking the git repository as the source of truth, it is possible to enhance collaboration, transparency, and traceability across development, operations, and security teams.

This approach can help reduce errors, improve delivery times, and increase the overall quality of the software being produced. Additionally, actively deploying software can help identify and address issues more quickly, leading to a more agile and responsive development process. In the future, we can expect to see more organizations adopting Git-Dev-Sec-Ops methodologies as they strive to develop and deliver software faster and more securely.

While there is no such thing as a "one-size-fits-all" solution, implementing all of these methodologies requires a lot of effort. However, it is definitely worth it.

Automated Deployment & Active Deployment

Automated Deployment is the process of automating the deployment of software to production or other environments. It involves using tools and processes to automate the building, testing, and deployment of code, which can help reduce errors and improve the speed and reliability of software delivery. In practice, this can mean using tools like Jenkins, Travis CI, and CircleCI to automatically build and deploy code to production environments.

On the other hand, Active Deployment is the practice of continuously deploying code to production or other environments as soon as it is ready, and manually by the developers without relying on the CI/CD process based on the git branches or webhook events. Active deployment can help identify and address issues more quickly, more proactive but still maintaining automated process, leading to a more agile and responsive development process.

Both automated deployment and active deployment are closely related to the "Git-Dev-Sec-Ops" methodology. By using Git as the source of truth for infrastructure and application configurations, teams can more easily collaborate and automate the deployment process. Automated deployment can help streamline the software delivery process and ensure that code is deployed consistently across environments. Active deployment can help teams respond more quickly to changes and deploy software more frequently, which is a key aspect of the DevOps philosophy.

Overall, the combination of automated deployment and active deployment can help teams deliver software faster, with fewer errors and greater consistency. This can lead to a more efficient and effective software development process, and ultimately help organizations achieve their business goals.

Both of these processes are built-in inside…

Diginext

is aiming to take care of the “Git-Dev-Sec-Ops” implementation at the begining of time, we all know there is no such thing as “one-size-fit-all”, but at least we can see how Diginext team put their effort to reach, as a Developer-Focused platform, multiple teams can easily work together by using it to manage cloud resources & deploy apps just in one place. It also help to improve the consistency of development process and operation process.

Website: https://diginext.site
Github: https://github.com/digitopvn/diginext/

P/S: The thing I like the most of Diginext is it's utilizing Kubernetes under the hood, and it overcome K8S complexity by stripping K8S away from the developers!

Other blogs

Developer-First Platforms - Overcoming K8S Complexity

Goon Nguyen — Thu, 15 Jun 2023 12:36:21 +0000

As cloud native development continues to evolve, Kubernetes has emerged as the go-to standard for organizations. However, it's important to note that Kubernetes is just the common orchestration framework for now. Many leaders in cloud native development have confirmed that the true challenges lie not in Kubernetes itself, but in the complexities of linking all the components together and making everything work seamlessly.

Against the backdrop of Kubernetes as the developer-first standard, organizations increasingly seek a developer platform concept and platform engineering as the Holy Grail for making the cloud native journey smoother for developers at every level of experience.

While there is no tried-and-true developer-focused Kubernetes platform (yet), this is also the beauty of the whole idea. The tooling landscape is vast, with organizations selecting what works best for their needs to put together their own developer platforms. However, this can also lead to choice paralysis and false starts, negating the speed benefits that going cloud native was meant to introduce.

With this in mind, let’s look at why creating a developer-focused Kubernetes platform makes sense and then explore what components you need to build it.

Developer-First Platforms: Overcoming K8s Complexity

No one denies that the cloud native paradigm introduces new complexity into the development process. The silos of monolithic development are breaking down, and the linear workflow of coding and handing off to someone else is shifting to a decentralized microservices architecture. This shift brings new challenges, such as different dependencies and the shift-left approach of "you build it, you run it" that has accompanied the cloud native revolution.

But how much depth of knowledge about Kubernetes does a developer really need? Should the developer be responsible for the full software life cycle, or just understand critical aspects of it to facilitate faster delivery and feedback loops?

These questions form the foundation of the discussion on developer platforms, which have been the subject of much debate in recent months. While these platforms aim to eliminate frustration, improve productivity, or standardize workflows, one takeaway from the development community (and their colleagues in DevOps and platform engineering) is that a developer-first platform should reduce complexity through standardization, yet still accommodate exceptions.

Developer-Focused Kubernetes Platform

There is no one-size-fits-all developer platform, making room for paving a path that achieves exactly what an individual organization needs for its developers. What do developers need to know to ship software safely, and how will a platform get them there?

Some key considerations for what development teams need from an efficient developer-focused Kubernetes platform include:

Support for developer self-service and visibility. Create a baseline for the necessary tools and required visibility to perform the job. Build in flexibility to ensure that no one is locked into a specific approach. A self-service baseline allows everyone to work from the same set of standards independently. This makes it easier to onboard new developers quickly, which facilitates reliable and efficient production.
Make it simple. Developers should have an understanding of Kubernetes, but only to the extent that it helps them ship software and receive critical feedback faster. Simplify and clarify their work by providing them with enough capabilities to work quickly without worrying about secondary considerations, such as infrastructure and security, which are important but not their primary focus.
Unleash the power of DevOps/PlatformOps. DevOps, PlatformOps, and Site Reliability Engineering (SRE) teams are more than just firefighters and first-line support. By creating a developer-focused self-service platform, these teams can focus on strategic projects while also supporting continuous improvement.
Centralize key data. Teams require real-time data to gain insight into what is working and what isn't. Whether measuring performance or tracking compliance, a centralized platform allows for the collection of operational and resource data.
Focus on faster feedback. The current macroeconomic environment highlights the need for faster and more efficient processes. A reliable developer platform should provide rapid feedback to avoid delays caused by waiting for builds to finish.
Facilitate the developer experience. Anything that can reduce cognitive load and keep developers focused on their core tasks is a good investment, especially when market conditions are challenging.

While all of this provides background and reasoning for why a developer-focused Kubernetes platform makes sense

And that’s the objectives of building…

Diginext

Diginext is creating an environment that makes it easy for developers to build, test, and deploy software quickly and efficiently. It’s also a place where you can manage and monitor all your cloud resources.

Learn more about Diginext:

Website: https://diginext.site
Github: https://github.com/digitopvn/diginext

Thanks for reading!

Kubernetes for the poor

Goon Nguyen — Wed, 14 Jun 2023 14:20:11 +0000

Kubernetes is great, since the last few years, it has proved that it is the best container orchestration software on the market.

However, there is 2 problems, though:

1. It is difficult to learn (and pronouce, lol)

Successfully managing Kubernetes clusters requires a deep understanding of so many concepts, definitions, and practices involved. With so much to consider, it can be difficult for developers to know how to deploy apps in the most effective way.

To deploy apps on Kubernetes you will need a CI/CD process, so you have to learn a little bit about building container images, pushing it to the container registry, telling the cluster to pull & run a container, monitoring the logs,…

2. It’s not cheap

Google Cloud, AWS, Azure,… they are all providing well managed Kubernetes engine service. And they are not cheap, you will be charged for the control plan, and also for the compute engine usage for each nodes of a cluster separately. (Not counting other network & storage costs)

If you're thinking about running your own managed Kubernetes cluster on your infrastructure, then you will back to deal with the first problem - Kubernetes complexity.

But that’s not it, if you don’t monitor your workloads well, such as control, and analyze your resource usage, you may end up having to pay huge Kubernetes bills at the end of the month.

Another issue is deployment, to deploy on K8S, you need to go through many steps as I mentioned earlier in the (1) section, or you can use CI/CD services like Github Actions or Bitbucket Pipeline to automate the tasks.

That brings you to find the DevOps engineers for doing such a job. And trust me, human resources are much expensive than any infrastructure resources.

Additionally, CI/CD services are not free. At first, you might think a thousand build minutes per month is a large number and that you would never reach it. However, in reality, it often ends up being a much higher number.

(Just do a quick math: if you have four people working on a project, and each of them builds three times a day on average, and each build takes three minutes, by the end of the month you will have spent 1080 minutes on builds: 4 x 3 x 3 x 30 = 1080 minutes, see?)

Note that you will likely have more than one project per month, and not all project builds will take less than three minutes!

And guess what? If you want to build app faster or your app requires more compute resource to build, you need to pay more money for extra resource quotas!

How did I deal with these problems?

1. I learned Kubernetes so you don’t have to

Kubernetes is hard. Pushing developers to learn it even harder (and cruel, their life is already really tough nowadays)

So I learned Kubernetes, and I’ve tried to train my team to use it a few times.

After more than 6 years of working with Kubernetes for my clients, partners, and my own teams, I have realized that the most difficult aspect is training others on how to use Kubernetes and deploy applications onto it.

Developers should not have to be frustrated by deploying their apps to the infrastructure, or having to bother DevOps engineers to help with deployment. They should be able to fully focus on developing their apps without needing to understand complex concepts or definitions of servers, domains, and infrastructure-related topics.

So I started building tools, to help my team deploying apps to Kubernetes cluster.

Why not using Jenkin? Because I don’t like Jenkins. Just that, lol. Actually because Jenkins can solve the deployment, but I want more than that, I want to take more control, automation & monitoring my K8S clusters.

It went well… until I started losing control of monitoring workloads when it started growing. Then I still needed someone with DevOps/Kubernetes knowledge to help out, but…

2. I’m poor and I still want to keep adopting Kubernetes…

I faced the challenge by keep evolving the tool I made recently.

My goals are simply summarized in:

Simplify those Kubernetes concepts & definitions to something our developers can understand.
Enhance our developer experience with easy-to-remember commands.
Centralized monitoring our K8S clusters no matter where it is and what is its cloud provider.
Build and deploy apps on our own server, so it can take the full compute resource for faster build time.
Manage our cloud resources other than K8S clusters, such as databases, health check,…
Automate whatever tasks I want…

It took me months to build this tool, luckily we've been working with a lot of clients, who have multiple Cloud resources across cloud providers, so I got opportunities to fix and improve the tool day by day.

Until now, my companies have been using this tool for years.

I really want to add more features, but as I've become increasingly busy, the release of new features has been slowing down.

Well, I started considering open-sourcing this project because I believe it can significantly improve the efficiency of those working with multiple Kubernetes clusters and other cloud resources, as it has for me. (and also being poor just like me, lol)

And there it is…

Diginext

is the web app server and command line interface (CLI) client to help developers deploy their projects & interact with their cloud resources easily.

Think of it like your own “Vercel” platform which is running on your own infrastructure, and managing your cloud resources.

Wanna try out?

I have a small K8S cluster for free on https://hobby.diginext.site so you can get your hands dirty right away.

Just follow these steps:

Before creating a new workspace, you will need a key, get one here (no worries, it’s FREE).
Create a new Diginext workspace with your DX key in the previous step at: https://hobby.diginext.site
Connect your Github to that workspace: https://hobby.diginext.site/git
Connect your Docker Hub to the workspace to store the container image: https://hobby.diginext.site/infrastructure/registry
Install Diginext CLI on your computer: npm i @topgroup/diginext --location=global
Connect your Diginext CLI with that workspace: dx login https://hobby.diginext.siet
Create new app with this CLI command: dx new For example:
- Project: Something
- App: Static Site
- Framework: pick “Static Site Framework”
- Git provider: select the one you have connected recently.
Deploy it: cd ./something && dx deploy
- Cluster: pick “Default Cluster”
- Container registry: pick “Your Docker Hub”
- Use generated domain: YES
- Port: 80
Watch the build process at: https://hobby.diginext.site/build/logs?build_slug=...
When it’s finished… Boom! There you go, your website is live at: https://something.dev.diginext.site

💡 Notes:
Since this “hobby” workspace is FREE (and I'm poor), I cannot provide any uptime guarantee or SLA, plus that it will have some limited quotas on number of concurrent builds, amount of apps,…
So please don't use it as a production environment, deployments on this cluster are subjected to be deleted to free up the resources at any time.

🔆 By validating DX API keys, I would be able to limit resources in the workspace, just to make sure my server is having enough rooms for everyone who wanna try out. If you want to get rid of these limits, set up your self-hosted workspaces by following this instruction.

Wanna set up your own workspace?

I wrote some articles to help you getting started below:

I turn my company’s PC into my own “Vercel-like” platform

Conclusion

Any feedbacks are welcome. If you are looking for other features, or wanna give me a hand, below is where you can start:

Thank you!

It's a long article, thanks for getting here. If you find any difficulties (or bugs), please let me know, I'm happy to help.

I turned my company’s PC into my own “Vercel-like” platform

Goon Nguyen — Tue, 13 Jun 2023 12:30:23 +0000

Why?

Because… why not? (it’s FREE, lol)
Utilize the power of my own PC to build web apps faster (with zero build time cost).
Kubernetes is hard & pushing developers to learn it even harder, well, I learned it so you don't have to.
Unlike Vercel, with Kubernetes cluster, I (and my teammates) can deploy ANY apps.

Requirements

A computer (obviously!) with Ubuntu Server OS
- Specification at least: 2 core, 4GB memory
- Recommendation: 4 core, 8GB memory (because MicroK8S will take around 2,5GB of memory to run, but you will also need some for your applications)
- DigitalOcean has some droplets with good pricing tiers.
MicroK8S to spin up a Kubernetes cluster
Lastly, this magical open-source tool: Diginext

Architecture

In this case, I use my company’s PC (Ubuntu Server OS, 1TB SSD drive, 8 core, 32GB of memory)

Install MicroK8S & deploy Diginext Server

curl -sfL https://diginext.site/install/microk8s | sh -

After it’s finished, you can try to access this URL: http://server-ip-address, if you can see the log in / sign up screen, then your cluster is ready!

For example: http://192.168.0.52

Create new account

Navigate to: http://server-ip-address then create a new account.

Then create your first workspace

Give your workspace a name, leave public unchecked if you don't want other people to freely access your workspace, then submit & you’re good to go.

Connect Diginext CLI to your workspace

To be able to deploy webapp to your MicroK8S cluster from your computer, you will need to install Diginext CLI and connect it to your Diginext workspace.

Open the terminal and install Diginext CLI with:

(If you don’t have Node.js 18+ installed, get it first)

npm i @topgroup/diginext --location=global

After it’s finished, you can use dx commands.

But first, let’s connect your Diginext CLI to the workspace:

dx login http://your-ip-address
# the browser will open up, copy & paste the access token here
# you will see a success message

Deploy a static webapp

Diginext Server need permissions to pull the git repository and start building, so let’s navigate to http://server -ip-address/git and connect your Bitbucket or Github account.
Diginext Server also need a container registry to store the build image, I will use Docker Hub in this example. Navigate to http://your-ip-address/infrastructure/registry/ and connect your Docker Hub with username & password.
When it’s done, back to your Terminal and create a new app with dx new command & fill in the form:
- Project: Hello World
- App: Static Site
- Framework: pick “Static Site Framework”
- Git provider: select the one you have connected recently.
Navigate to the directory: cd ./helloworld-staticsite and you will see the source code of the framework, nothing special here, just a static html files and a Dockerfile
Deploy to your MicroK8S cluster using this command: dx up
It will request your Diginext Server to pull the git repo of the webapp, then build the container image from the Dockerfile, and deploy it the MicroK8S cluster.
- Cluster: pick “Default Cluster”
- Use generated domain: YES
- Port: 80
Now check out the link in the Terminal to see the build & deploy process, something like this:

When it’s finished, click on the auto-generated link, you will see your web app now going live, woohoo!

👉 Since I have only set up this server for internal use, if you want to publish it on the internet, you may need to expose some ports on your internet router and configure traffic routing / security guards to your metal server. However, this is beyond the scope of this article.

What’s next?

Learn more about the stories of Diginext.

Forem: Goon Nguyen

Introducing DigiCord: The Ultimate All-in-One AI Discord Bot

What is DigiCord?

How to Use DigiCord

Why I Built DigiCord

Benefits of DigiCord

Get Started with DigiCord

UX is becoming less important in the age of AI?

Will UX disappear?

Because they look complicated, right?

Voilà!

In conclusion

Looking for useful AI products?

Let build this place together! Because, life is all about sharing, my friends.

Speed test building Next.js T3 App with Github Actions, Circle CI, Vercel & Diginext

Now, let’s get the party started!

First time, with no cache:

1. Docker Engine on my Macbook M1 Pro

2. Github Actions

3. Circle CI

4. Diginext

5. Vercel

Alright, let’s do another round!

Second build, cached!

1. My macbook M1 Pro

2. Github Actions

3. Circle CI

5. Vercel

4. Diginext

Summary

“GitDevSecOps”

DevOps

GitOps

GitSecOps

Why is one or another?

"Git-Dev-Sec-Ops"

Automated Deployment & Active Deployment

Diginext

Other blogs

Developer-First Platforms - Overcoming K8S Complexity

Developer-First Platforms: Overcoming K8s Complexity

*Developer-Focused Kubernetes Platform*

And that’s the objectives of building…

Diginext

Kubernetes for the poor

1. It is difficult to learn (and pronouce, lol)

2. It’s not cheap

How did I deal with these problems?

1. I learned Kubernetes so you don’t have to

2. I’m poor and I still want to keep adopting Kubernetes…

Diginext

Wanna try out?

Wanna set up your own workspace?

Conclusion

Thank you!

I turned my company’s PC into my own “Vercel-like” platform

Why?

Requirements

Architecture

Install MicroK8S & deploy Diginext Server

Create new account

Then create your first workspace

Connect Diginext CLI to your workspace

Deploy a static webapp

What’s next?

Developer-Focused Kubernetes Platform