appliku

8 ms·

31.
by appliku 4y ago
Hey! There is a heroku config vars sync, so you can keep using Heroku Postgres, but moving the app itself out of there. Your vars will be in sync, so when heroku rotates credentials they will be quickly applied to your app deployed with App
32.
by appliku 4y ago
You can get built databases deployed with Appliku as well. No reason to go broke on a small side project
33.
by appliku 4y ago
3 years ago, I tried Heroku and was quite impressed by it. Although the price is prohibitive for a hobby project that needed resources but wasn't generating any revenue, I had to start seeking other options. Ended up developing my own
34.
Show HN: Django REST Framework and Open API 3 Tutorial(appliku.com)
3 points by appliku 4y ago|0 comments
35.
by appliku 5y ago
That's pretty cool. I always thought animation making should look like this, not million of layers and dots. GJ!
36.
Celery Task Queue: Groups vs. Chords(appliku.com)
2 points by appliku 5y ago|0 comments
37.
by appliku 5y ago
Thank you Django. that’s a great news. 14 years ago someone helped me discover Python and Django. I started from django official tutorial and never changed the framework of choice. It was my hobby, my career, my tool to put the food on the
38.
Performance Comparison of Cloud Servers(vitobotta.com)
2 points by appliku 5y ago|0 comments
39.
Scaffold Django rest APIs like a champion(github.com)
6 points by appliku 5y ago|0 comments
40.
by appliku 5y ago
Oh yeah i totally understand what it means having so much projects – every minute spent on manual task becomes an hour if done on all projects. Let me know if you need another set of eyes or discuss it options. https://twitter.co
41.
by appliku 5y ago
In a nutshell it is delegating all this manual work to a service. I was happy with manual deployments for a while too, until i got fed up with this activity. It is just a question of quality of life, automation. Also, yes - there are tutori
42.
by appliku 5y ago
Built during the project build and uploaded to s3 and served via CDN.
43.
by appliku 5y ago
Thanks A LOT for kind words. So first I am thinking what is the best way to offer scaling. There are so many ways how it can be done and in other comment threads there are hot debates happening about that. It is still an open question. I wa
44.
by appliku 5y ago
As a developer you only pick your repo and pick a server size and region. If you need customization you can make your own dockerfile that will be used to build your image. If you need to move to another server - you provision another server
45.
by appliku 5y ago
Please refer to more up to date Djangitos project template. https://github.com/appliku/djangitos I will rewrite ec2 deployment tutorial as soon as possible. Thanks for reminding me about it.
46.
by appliku 5y ago
hey! I have a question. Are you deploying it to your servers/cloud accounts or clients’ accounts? Regarding your questions: it is responsibility of the app to build and upload the static assets where needed. If you want recommendation
47.
by appliku 5y ago
I would like to say that existence of Chris Oliver’s Hatchbox was initial inspiration and validation after finding which i decided to build Appliku. So, Thanks, Chris!!!
48.
by appliku 5y ago
Yes, I can def-ly see it is way better. Question here, as far as i understand Caddy is a paid product, how its licensing works while deploying on customers servers?
49.
by appliku 5y ago
of course it does. Appliku out of the box provides a way to provision redis and rabbmitmq. I have yet to write a tutorial about celery. To specify processes to run you use Procfile. Specify your celery commands and enable them in Process ta
50.
by appliku 5y ago
Tell me more about Caddy vs Nginx. What are the biggest benefits? I honestly not exactly happy with nginx in some corner cases.
51.
by appliku 5y ago
Depending on your requirements build ties in Heroku can be quite long. One app i’ve recently observed take 7 minutes to build because it always had to build both JS and Django parts(buildpacks for both were executed every time). We made it
52.
by appliku 5y ago
One thought I have in mind is ability to provision AWS and/or Digital Ocean managed DB offerings so you don’t have to leave appliku interface to get a production grade DB. But Appliku will keep being deployment solution for apps.
53.
by appliku 5y ago
It happens for a free dyno. For paid dynos they are always up. Appiku doesn’t turn off your servers. Scaling and spinning up/down additional servers is in plans.
54.
by appliku 5y ago
I completely agree :)
55.
by appliku 5y ago
$250/mo per process. And with appliku it is done automatically so there is no need for admin/devops time.
56.
by appliku 5y ago
At this moment we are not fighting for the niche of Production grade databases with failovers and all these valuable things. The feature to back up at least postgres is planned, fail overs , replication, etc is not even planned yet. There a
57.
by appliku 5y ago
Also every provider offers different things, at different costs, etc. So it is up to providers to build solutions that are easy with a given language or framework. We aspire to build a convenient service for Python/Django and there is
58.
by appliku 5y ago
I would correct the last part. Appliku is an automated devops as a service. Heroku is selling you a very much overpriced complete service. And that's where Appliku comes in as a way to fight insane costs. But yes, setting up a server i
59.
by appliku 5y ago
Hey, thanks for kind words! At the moment databases in Appliku are best fit for non-production environments. So while you can enjoy easy and great deployments of your apps, I am not ready yet to compete on the production databases front. So
60.
by appliku 5y ago
It only proves there is market for that. The more solutions the better! Wish you best of luck!

More ›