My story of interacting withĀ glitch.comĀ began not so long ago, but in this short time, I really loveš„° this coolly invented service. So, in this article, I wrote the story of my experience with glitch UI.
This project is developed and supported by theĀ FogCreekĀ team led byĀ Joel Spolsky, who co-founded services such asĀ TrelloĀ andĀ StackOverflow. Here is hisĀ blog.
This story has two parts:
- The first part (current) will discuss Glitch.com itself and its features and benefits.
- In the second part, the experience of delivering your node.js application to glitch.com will be described in a non-standard way:
In fact, this is actually a remote workstation, with the ability to edit code, add files, and the ability to execute necessary commands in the console.
And this service stands out with its unusual and cool design. It mainly focuses onĀ node.jsĀ and static pages. So this is just a paradise for aĀ JavaScriptĀ developer.
At the first visit, we are greeted by the main page, which is decorated very funny.

The following authentication types are supported:
- GitHub
- And regular login with e-mail and password.
- And there is an inconspicuous button at the bottom āUse a sign-in codeā

Which way to choose is up to you. For the developer, of course, it is more convenient to use the input through GitHub.
In general, this service impressed me with the fact that it provides enough resources for your web application, and the console most impressed me. And now letās talk about the important components of this service.
About UI
After entering your account, if your projects are available, a list is displayed from which you can immediately select a project. The rest of the information about the work of other people is below. It is very convenient and does not force you to make unnecessary actions.

You can click on your project and then a preview is shown to you.
You can immediately click on the buttons:
- Edit ProjectĀ āin order to open a convenient and simple IDE in the browser, which can reboot after you make changes.
- ShowĀ ā to open the project in a separate window for viewing, as if you were users.
This is how theĀ mad-fake-slackĀ application looks like for example ā if I click on Show.


This is how the mad-fake-slack application launched on glitch.com looks like.
Well, if I click onĀ Edit Project, then I get into a mini improvisedĀ IDE. It is very convenient for quickly fixing problems in the browser.

IDE view for your project
IDE Features
- View file contents
- Upload files
- Creating files nested in folders by specifying not only the name of the file but also the path
- Delete files
- To load resources, there is a special folder called āassetsā, which is logical. It can serve as a transshipment base ā a kind of file exchanger. Next, you will see how you can take this opportunity
- Reaction to changes gives you the opportunity to see how they affect the UI of your web application

- Very convenient notification of new packages for your dependencies

This is how convenient notification of new versions of packages comes in.
There are also disadvantages in the IDE, but they are easily bypassed through the console. In the IDE, you cannot load a binary file such as a picture or font directly into the desired folder, all downloaded files will be placed in the āassetsā folder. But as I said, this is not a problem.
Metrics available at IDE
How about metrics. They are very important since all your web products run in the container. And I will tell you honestly, they really saved me, becauseĀ node.jsĀ library forĀ @slack/rtm-api
gets crazy if it tries to connect to address that is not listened by any service, which leads to processor loading atĀ 80%. I think it would be difficult to notice if there were no container status.
This is how the container status looks in the interface:

It is hidden in the Tools menu and does not bother you, but as soon as something goes wrong, you will receive a notification directly in the IDE. By clicking on Container Status, you will see the following section:

Here in real-time metrics are displayed:
- CPU utilization
- Memory usage
- Disk space usage
In principle, everything is very convenient. Well, now letās talk about the features of the console.
Console features
You can go to the console from the Tools menu by clicking on the āFull Page Console ->ā item.

Menu item to go to the console
And it is a black page with valuable tips and capabilities of the native console.

Thatās how the console meets us
What can this console do?
- Respond to the standard carriage return commandsĀ
Ctrl-E
Ā andĀCtrl-A
Ā to move to the end and beginning of the line. Very comfortably! - You can startĀ
htop
Ā andĀtop
Ā and close them by standard pressing theĀq
Ā key

Running `htop` in console
- TheĀ
clear
Ā command clears the console screen. Also, a very comfortable feature. curl
Ā andĀwget
Ā are installed and available on the system.

Very useful curl and wget tools
- You can also see theĀ
env
Ā that are installed in the docker

Without problems, you can see what is happening in the environment variables.
- In general, we can say that this is a full-fledged console, with a set of shortcuts, which I really liked! In this case, all statuses, when usingĀ
wget
Ā andĀcurl
, work fine. You can see the progress and you are in the know of the full picture. - All changes made in the console will not be immediately applied for logical reasons. This approach gives you the opportunity to think, understand your changes, and when you are ready, just type theĀ
refresh
Ā command in the console and pressĀEnter
. Your changes will be applied immediately and the UI will reboot. In the IDE you will see files or changes made in the console.
Conclusion
The capabilities of the service impress with its simplicity and the ability to perform deployment and make changes for the least number of actions. A full-featured console in a web browser is also a very cool feature, which pleases not only with the high-quality display of data but also with an abundance of default tools, which helps you to easily perform the actions necessary to deploy the application inside the docker.
See you in theĀ second part!

Migrating From Vue 2 to Vue 3 with Vue Composition API
Migrating From Vue 2 to Vue 3 with...
Migrating From Vue 2 to Vue 3 with Vue Composition API
As we know, the official release of Vue 3 was on September 18, 2020, itās been almost a year, and I think itās time to move on to it. Buuuut⦠itās...

Software Architecture 101 - Introduction to the World...
Software Architecture 101 -...
Software Architecture 101 - Introduction to the World of Application Design
Hello, everyone!Today, I would like to introduce you to the world of application design.Designing applications can be called a multidisciplinary...

Strapi: Things to Keep in Mind Before Migrating to...
Strapi: Things to Keep in Mind Before...
Strapi: Things to Keep in Mind Before Migrating to This CMS
When it comes to CMS, the modern market has already stepped so much that the choice is becoming increasingly difficult. There are so many options for...