Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: What's your favorite way of getting a web app up quickly in 2018?

news.ycombinator.com

Post reply on HN
Print view View original

251–260 of 569 posts

Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?

#251

Post by JepZ »

marcus_holmes wrote: post #13

I write the server-side in Go, cross-compile to a Linux binary, and set that up as a service on a vanilla Ubuntu box (usually Digital Ocean). Deploying a new version is a matter of sftp'ing the new binary (and any templates, images, etc) over the top of the old one and restarting the service. If I need a database then I use Postgres, and the setup for that can be a pain, so I get it documented/scripted using Ansible.…

For me this is the response to 'how do you build stable/scaleable/.../good web apps in 2018', but sadly not to 'favorite way of getting a web app up quickly in 2018?'.

The whole process of starting a new VM for every little project seems to me like overkill and developing components if you just want to get a prototype out the door can be difficult as the components will most likely have such a poor quality that you can't reuse them for anything else.

With that said, I am 100% pro Golang Server + Vue.js UI when it comes to building something which will be definitely more than a prototype (no shortcuts taken).

Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?

#252

Post by buvanshak »

ramy_d wrote: post #195
buvanshak wrote: post #187

Earlier quoted context omitted.

Ok. But that does not mean that you have to use the worst thing that is out there. Why not Python?

it's worse to you, not the client. client actuality doesn't care and PHP is legacy I guess?

If the client does not not care, why suffer by using something that is worse for you? I mean, you might as well use something that you like.

I don't get the logic here.

Another thing is that, if it it worse for you, it is automatically worse for the client. I am not sure why it is so hard to see. if your tool is bad, then your work ll suffer, and thus the client. So it is worse for them also..

Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?

#253

Post by andrei_says_ »

burlesona wrote: post #100
andrei_says_ wrote: post #47

Rails still rocks, ruby is still beautiful and elegant, Heroku is still incredibly easy to deploy to. Vuejs is a good option for complex data driven ui.

This is my go-to as well, incredibly easy and fast to get going but also scales reasonably well. The only caveat I’d say is I prefer Roda over Rails for APIs and simple projects.

Do you happen to use rodauth with rails? And sequel?

Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?

#254

Post by slow_donkey »

friedman23 wrote: post #131
guessmyname wrote: post #29

Earlier quoted context omitted.

I second this; Go + React.js (Vue.js in my case) I talked about it just a couple of hours ago [1]. [1] https://news.ycombinator.com/item?id=17215658

How do you handle server side rendering? This is one of the reasons I chose to go full Node+React.

Look up express-vue

Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?

#256

Post by IshKebab »

kvm wrote: post #186
marcus_holmes wrote: post #13

I write the server-side in Go, cross-compile to a Linux binary, and set that up as a service on a vanilla Ubuntu box (usually Digital Ocean). Deploying a new version is a matter of sftp'ing the new binary (and any templates, images, etc) over the top of the old one and restarting the service. If I need a database then I use Postgres, and the setup for that can be a pain, so I get it documented/scripted using Ansible.…

How is this setting things up "quickly" when OP is asking to limit complexity? You're suggesting: 1. Server side in Go 2. Cross-compiling it 3. sftp'ing and restarting the service everytime 4. postgres 5. ansible 6. Makefiles 7. Webpack 8. Babel 9. React

Writing web servers in Go is extremely easy. https://golang.org/doc/articles/wiki/

Cross-compiling with Go is done by setting two environment variables. That's it. This is not like the mess of C++ cross-compiling. In LiteIDE it is simply a matter of choosing Linux from a drop-down: https://www.wut.de/pics/screenshot/e-505ww-07-pide-000.png

SFTP is not exactly hard. Nor is `nohup ./server &`.

From 5 on I agree though - is that 4 build systems? Insanity. I would just make a static web page with normal HTML forms or whatever and Go templates. If you really need client-side Javascript, I'd just use jQuery, or something similar and lightweight like minifiedjs.

Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?

#257

Post by slow_donkey »

jsmeaton wrote: post #248
innomatics wrote: post #78

Django, Docker and AWS ECS and ELB. Absolutely worth the effort to learn how to build a Docker image and put together bash scripts to push the image and update an ECS service. We have a base project which includes nginx and uwsgi set up to simply serve the Django app and static files on port 80. Having an ECS Docker cluster with spare capacity greatly assists getting new projects up and running quickly, especially if…

May I ask how you’re managing secrets with this setup? For example, the secret key or database URL. Our current setup deploys an env file which is sourced before starting the process. I’m less sure how this translates to a production docket deployment.

Docker shouldn't affect your secrets management because secrets shouldn't be baked into your image anyways. I tend to expose them as environment vars and currently use Kubernetes to expose a keyvault url/password so the app can automatically grab all the secrets

Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?

#259

Post by buvanshak »

JonoBB wrote: post #241
eagsalazar2 wrote: post #211

Earlier quoted context omitted.

In many areas of the US (the entire west coast for example), PHP is dead - plain and simple. Independent of whether it is good or not, selecting dead or obscure technologies for your clients is completely irresponsible and leaves them with a maintenance catastrophe just because you like php. Yes there is a lot of hipster-ism out there in platform choice but there are plenty of mature, fast, and popular options out th…

PHP is not dead - plain and simple. Independent of whether it is good or not, selecting technologies based on your biases for your client is completely irresponsible. There are plenty of mature, fast and popular options out there. PHP is one of them.

denial!

Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?

#260

Post by Grue3 »

chunkyslink wrote: post #236
Grue3 wrote: post #208

I wrote about it on my blog (that was in 2014 but nothing really changed since then). http://readevalprint.tumblr.com/post/101841449553/its-alive-...

I hope you are being sarcastic when you say, nothing really has changed since then.

I'm saying this regarding my architecture. If I started again, I'd probably use the same technologies. And, I mean, everyone else is recommending Django and Ruby on Rails which are even older so why would you pick on my comment specifically?
Post reply on HN