Automatic CDN-enabled deployments with SSL to the cloud. No hassle, no dev-ops!

Auto-deployments

Add custom domain and personalize your site to grow your own brand. We'll do the rest.

Grow your brand

Opt-in to premium publishing and earn by writing and teaching. Engagement-based rewards, coming soon.

Side income

Easy to use, Medium-like article publishing with drafts and granular visibility and SEO controls.

Publish in minutes

Fully-featured course management, including tier-based payments are coming soon.

Manage courses

No matter the type of content you work on we will do the heavy lifting for you! Then tweak as needed.

Baked-in, tasty SEO

Digital nomad essentials

Meet & Greet

Home

I love Postico2, it is super-easy to use and does exactly what I expect and need it to do - connect to a local or remote database, view and edit data.

Postico2 (same as some of the alternative apps) has this handy way of saving some SQL queries for execution. These queries are project-scoped, which means that when you save a query in one, it will not be available in another and you will need to create a new one.

Personally, I rarely work with raw SQL queries, so its syntax is not in my active memory, so if it wasn’t for this ability to save a query I would need to resort to my notes or StackOverflow to  get it right.

With each project you likely will have different needs and with that project-specific queries, but in my experience, two that are always there are:

It's a small thing, but if you do this often, this will save you some minutes and provide more convenience, and if you don't do this often it will save you hassle trying to remember/figure out how to get the minimal setup working for a fresh Postgres DB.

Comments/thoughts/question? Tweet @scottagirs or drop them in the comments below. 🙌🏼

The first steps I take when setting p a fresh Postgres database, with a database user and password, with Postico2.

My Postico2 workflow

My Postico2 workflow

Comments