Appliku Reviews

1. Guest

   almost 3 years ago
   Great for a beginner

   Makes it easy to deploy without binding you to some start-up-company servers. All hosted on Amazon in my case.

StackGres Reviews

Appliku mentions (54)

• Django is for everyone.

  Unfortunately, this is the main downside of choosing Django over other options targeted at personal websites. With Blaze.horse, I’ve tried to set you up for an easy time, but it’s still fiddlier than it ought to be. There are some up-and-coming projects that give me hope, such as Button and Appliku, but I’m personally happy with Fly for now. - Source: dev.to / almost 2 years ago

• Logs of Celery Tasks

  Also you can watch logs for current processes without logging into SSH. Check it out: https://appliku.com. Source: over 2 years ago

• Django api deployment (python 3.11 supported)

  I'm using https://appliku.com/ for my deployments. They have a free tier and it set's up everything for you but you need to be using docker. Source: about 3 years ago

• Any exciting projects/tools

  For 4 years I am grinding on making the best deployment tool for python/Django apps. Still excited about it :) https://appliku.com. Source: about 3 years ago

• Using NextJS for templates a sensible choice?

  We at https://appliku.com went with NextJS + DRF (drf-spectacular, open api codegen) and it is amazing. Source: about 3 years ago

StackGres mentions (10)

• TimescaleDB compresses time-series data

  At StackGres [1] we find Timescale to be one of the most used extensions. Timescale is quite a successful project! StackGres is actually the first solution recommended by Timescale for self-hosting with Kubernetes operators [2]. So if you are into Kubernetes (or if not, consider it, using something like K3s [3] is quite straightforward and lightweight on resources), this is probably a great option to self-host... - Source: Hacker News / 20 days ago

• Show HN: SQL-tap – Real-time SQL traffic viewer for PostgreSQL and MySQL

  * Latency. Yes, yes, yes, they add "microseconds" vs "milliseconds for queries", and that's true, but just part of the story. There's an extra hop. There's two extra sets of TCP layers being traversed. If the hop is local (say a sidecar, as we do in StackGres) it adds complexity in its deployment and management (something we solved by automation, but was an extra problem to solve) and consumes resources. If it's a... - Source: Hacker News / 5 months ago

• Application Less Containers

  This is conceptually similar to what we did for Postgres extensions at the StackGres [1] project. I gave a talk at a Kubecon about it [2]. However, this scheme is not perfect. Some Kubernetes security solutions enforce immutable containers, and once the agent pulls any additional file into the container, it will be flagged. It's also harder to reason about the security of the image (think CVEs, etc), given that... - Source: Hacker News / 11 months ago

• Pg_lakehouse: Query Any Data Lake from Postgres

  I applaud the decision to use AGPL-3.0. For me, it's a license that provides forward guarantees to the Community: no proprietary forks can happen, so any fork will be an OSS fork from which the upstream project may benefit too, which benefits all users. That's the reason we chose this license for StackGres [1], another project in the Postgres space. [1]: https://stackgres.io. - Source: Hacker News / about 2 years ago

• Keycloak with PostgreSQL on Kubernetes

  This is good and interesting recipe to get Keycloak and Postgres on Kubernetes. There is an important improvement, though: the Postgres deployed here is not production ready (high availability, backups, monitoring, etc). We run Keycloak on StackGres [1] which gives us production-ready Postgres setup (disclaimer: it's dogfooding). Happy to share the YAML manifests used to deploy Keycloak with StackGres. Maybe we... - Source: Hacker News / about 3 years ago