Having access to your application directory can be crucial when you are doing things wrong want to check your production environment in detail. Maybe you need direct access to the database or want to check if a file is really there. Who knows? Maybe you have your reasons to rm -rf that repo or hijack that live app*.
Whatever the case, you can now launch an interactive terminal that gives you access directly inside your app's container. To do so, just navigate to your app's settings page and find the relevant button under the Remote Commands section. The amount of headache and frustrating chat-gpt sessions we had to go through to bring this feature to life was probably more frustrating than a parent vacuuming on a Sunday morning, when you had no school. The work behind it is pretty interesting though (for the tech-savvy people at least), and will probably make a very strong blog post, to which we will leave a link 👉 here 👈 (in the future).
Without further ado, go experience the terminal, go experience the future!
Other updates:
Fixed broken deploy instructions page, when no app is set
Improved the way next steps (add-database and set-config-variable) are tracked
Normalized warning and error icons in activities and app processes
Improved sub-activities display and added name-breadcrumbs
Fixed bug: Sub-activities are not individually displayed in the activities side-panel upon creation now (since they wouldn't show up if you refreshed the page anyway)
*This actually won't work, because each terminal spins up the latest version of your app in a new container, not the one that is actually receiving web traffic.
As we are riding the waves towards leaving Beta, we are focusing on the most critical features first, like learning how to swim (👀 patiently 👇 at /changelog). Secondary tasks like implementing payments and billing can definitely wait. Who cares about scaling to multiple servers or load balancing? Just look at that thing swim and be happy!
But seriously, when I am working on given designs, I always ship results very close to the original Figma design. Like *at least* 14.3% accuracy. So today, 5 minutes after I deployed the new changelog pages, news have traveled far and wide to reach our designer's ears. Need I say more? I spent 2 more hours fixing paddings, line-heights, extending the tailwind config, realigning everything, etc., but mostly watching our logo swim across the screen.
Even though it can be frustrating, it has been a humbling and learning experience every time. These minor (in my eyes) changes I am so reluctant to dig back into and fix, always end up adding up to a very significant difference (for the better) when I compare before and after screenshots. TL;DR: Trust your designers.
This week we took some time to revisit the navigation structure, the organization of cards and where everything is supposed to be. It was that familiar time when dev-ing stands in the corner and takes a beating from the ux-ing. Ux-ing won, but dev-ing came out stronger than before. It was worth it, so let's take a quick look at each bruise the punches left us with:
Navigation improvements: Navigating to internal pages (or frames as called in the Rails world), now adds "back" links with contextual titles. This is supposed to give you a better feeling of where you are or something. I don't know I wasn't paying attention, but I think it works?
We moved a bunch of cards from the overview page into the app settings page. One such example is the Domains section, which also got evicted from the app sidebar menu.
We also added a track-changes feature for some forms, so the submit buttons get enabled only when you make changes to one of the form's fields. Additionally, buttons that load remote frames which take a bit longer, now have a loader icon. I contemplated if we should solve this by offering yoga and meditation classes to improve impatience, but the look I got from our designer when I made that suggestion, was all I needed to move that idea back to the backlog.
Improved the structure and styles of the remote commands section (also moved into settings), to feel a bit more like an ACTUAL console. Aww don't cry fake-console, you'll get your upgrade soon! [👉 It did get its update about a month later; read the relevant changelog]
Added the option to set a domain as "primary". The primary domain will now be used as the default url when opening the app, via the relevant button in the status card.
Of course we saved the most important new feature for last. Make sure you are sitting in a sturdy chair cause this one might be the one that knocks you out (!):
With the new dashboard everything is more organized. You now have a page where you can quickly see your most recent actions per app/day. This is also your go-to place to stay updated (and excited, which of course you already are... right?) with what happens in our ecosystem, view our roadmap or just check the latest changelog (like this one!).
You also now have an overview of all your services in a single page. We improved link/unlink functionality so you can move services between different apps.
Last but not least, navigation got a mini boost. We moved everything into a single navigation area that spans horizontally across your screen. Going into an app page, changes the navigation context to be app-centered (hooray for breadcrumbs), but you can easily go back to your dashboard or apps panel.
Hope you find the update useful. Welcome to the new dashboard. Welcome home *spotlights dramatically fade out*
TL;DR
New activities overview page (dashboard)
New services overview page
Improved service link/unlink functionality
Improved navigation and breadcrumbs
Various other improvements
Deploy apps in minutes
Streamline the process of launching robust web solutions, ensuring efficiency and reliability throughout the development lifecycle.