7 ms·

Friendly suggestion: 1. Add the backend under same repo. 2. Add a root docker-compose.yml instead of sending interested party to "install backend". root

by avip 7y ago

oliv__ 7y ago
I agree with suggestion #1 but what do you need to bring docker in for? That's way overkill. Just have the server side serve the Vue.js app on the main route.
- salamander014 7y ago
  I understand why people think Docker is overkill, but Docker is a simplified approach to the most "correct" way to build and deploy applications we've come up with so far. Even though simple projects don't necessarily need Docker to work, they are 100 times better off using Docker than doing things by hand, because that alternative means they are only deploying once and never again (updates, new environment, dev/staging/prod) and that's just not true.
  - dvt 7y ago
    This, of course, sounds good in theory, but then you'll realize that Docker itself can break six ways from Sunday. Deployment should not be part of, or in any way linked to, code. I'm not sure why everyone's starting to bundle what is essentially dev-ops infrastructure with source. I have some old laptops where Docker doesn't even work, for example (due to a lack of VT-x). Why should that preclude me from a simple "yarn run" or whatever? It's insanity.
    - koboll 7y ago
      >Deployment should not be part of, or in any way linked to, code. Why?
      - Ohn0 7y ago
        Probably because deployment is environment specific? So I guess that would be ok for your own project, but not something intended to be shared, where you don't know the target deployment environment.
      - dvt 7y ago
        Because deployment tends to be very context-sensitive[1], but code should almost never be. [1] Are you running this in the cloud? On Google? On AWS? Cloud functions? A containerized VM? Maybe you're running it on an old Mac in your basement. If you're deploying on Linux, you're using lots of bash scripts but -- whoopsie -- those won't work on Windows.
        originalvichy 7y ago
        This is why Docker is suggested. It is the best thing so far even though a more polished system can/should take its place. A well written Dockerfile and docker-compose files contain and describe all the dependencies you need and you can copy them to an Ansible playbook or just a script for your choice of OS/environment.
        slig 7y ago
        ... and that's exactly why Docker shines so much.
        avip 7y ago
        [1] You've basically listed the very reason I'm using docker. It makes my code deployment agnostic. Bash "setup" files? been there. I write Dockerfiles. I think that's the only thing I'm strongly opinionated about as a developer. --- EDIT This is a classic. Reading the backend "how to run" guide I see: DATABASE=<your-mongodb-connection-string> PORT=5000 SERVER_URL=http://localhost:5000 This should settle any debate about docker being "overkill". Developers are notoriously reluctant to install things on their dev machines. As-is this repo has non-trivial setup friction which will reduce # of potential users/testers. TL;DR: docker-compose up
        7y ago
    - MuffinFlavored 7y ago
      > but then you'll realize that Docker itself can break six ways from Sunday Do you know how many billion dollar companies use Docker in production every day with no breaking? > Why should that preclude me from a simple "yarn run" or whatever? It's insanity. because your UI backed by an API is really useless without Postgres :)
      - dvt 7y ago
        > Do you know how many billion dollar companies use Docker in production every day with no breaking? I get that my opinion is controversial (and, in fact, I use Docker daily and it has a cozy spot on my resume), but keep in mind that you can say this about all kinds of mediocre technologies that have become massively popular.
- avip 7y ago
  For this kind of project the Dockerfile is an executable README. It's a reproducible and predictable installation guide.
- deleted 7y ago
  [deleted]
- Fiahil 7y ago
  Overkill ? Maybe. But the amount of time saved by not going through "Just having the server side serve the Vue.js app on the main route" is insane. Simplicity is the metric you want to optimize for, because it really reduces opportunities for breakage. Docker adds a few layers, yes, but it also makes deployment, and local launch easier. The only acceptable alternative to Docker, is, IMHO, a makefile. If I open your project and see a Dockerfile, I'm just going to `docker build && docker run`. If I see a makefile, I'm just going to run `make help ; make run || make`. It greatly reduces the cognitive load if I only want to quickly see what the project does.
rkwz 7y ago
I created something similar to what you described but using React - https://github.com/sheshbabu/starterkit https://github.com/sheshbabu/starterkit Real app built using this - https://github.com/sheshbabu/freshlytics https://github.com/sheshbabu/freshlytics

by avip 7y ago

oliv__ 7y ago

I agree with suggestion #1 but what do you need to bring docker in for? That's way overkill. Just have the server side serve the Vue.js app on the main route.

salamander014 7y ago
I understand why people think Docker is overkill, but Docker is a simplified approach to the most "correct" way to build and deploy applications we've come up with so far. Even though simple projects don't necessarily need Docker to work, they are 100 times better off using Docker than doing things by hand, because that alternative means they are only deploying once and never again (updates, new environment, dev/staging/prod) and that's just not true.
- dvt 7y ago
  This, of course, sounds good in theory, but then you'll realize that Docker itself can break six ways from Sunday. Deployment should not be part of, or in any way linked to, code. I'm not sure why everyone's starting to bundle what is essentially dev-ops infrastructure with source. I have some old laptops where Docker doesn't even work, for example (due to a lack of VT-x). Why should that preclude me from a simple "yarn run" or whatever? It's insanity.
  - koboll 7y ago
    >Deployment should not be part of, or in any way linked to, code. Why?
    - Ohn0 7y ago
      Probably because deployment is environment specific? So I guess that would be ok for your own project, but not something intended to be shared, where you don't know the target deployment environment.
    - dvt 7y ago
      Because deployment tends to be very context-sensitive[1], but code should almost never be. [1] Are you running this in the cloud? On Google? On AWS? Cloud functions? A containerized VM? Maybe you're running it on an old Mac in your basement. If you're deploying on Linux, you're using lots of bash scripts but -- whoopsie -- those won't work on Windows.
      - originalvichy 7y ago
        This is why Docker is suggested. It is the best thing so far even though a more polished system can/should take its place. A well written Dockerfile and docker-compose files contain and describe all the dependencies you need and you can copy them to an Ansible playbook or just a script for your choice of OS/environment.
      - slig 7y ago
        ... and that's exactly why Docker shines so much.
      - avip 7y ago
        [1] You've basically listed the very reason I'm using docker. It makes my code deployment agnostic. Bash "setup" files? been there. I write Dockerfiles. I think that's the only thing I'm strongly opinionated about as a developer. --- EDIT This is a classic. Reading the backend "how to run" guide I see: DATABASE=<your-mongodb-connection-string> PORT=5000 SERVER_URL=http://localhost:5000 This should settle any debate about docker being "overkill". Developers are notoriously reluctant to install things on their dev machines. As-is this repo has non-trivial setup friction which will reduce # of potential users/testers. TL;DR: docker-compose up
        7y ago
  - MuffinFlavored 7y ago
    > but then you'll realize that Docker itself can break six ways from Sunday Do you know how many billion dollar companies use Docker in production every day with no breaking? > Why should that preclude me from a simple "yarn run" or whatever? It's insanity. because your UI backed by an API is really useless without Postgres :)
    - dvt 7y ago
      > Do you know how many billion dollar companies use Docker in production every day with no breaking? I get that my opinion is controversial (and, in fact, I use Docker daily and it has a cozy spot on my resume), but keep in mind that you can say this about all kinds of mediocre technologies that have become massively popular.
avip 7y ago
For this kind of project the Dockerfile is an executable README. It's a reproducible and predictable installation guide.
deleted 7y ago
[deleted]
Fiahil 7y ago
Overkill ? Maybe. But the amount of time saved by not going through "Just having the server side serve the Vue.js app on the main route" is insane. Simplicity is the metric you want to optimize for, because it really reduces opportunities for breakage. Docker adds a few layers, yes, but it also makes deployment, and local launch easier. The only acceptable alternative to Docker, is, IMHO, a makefile. If I open your project and see a Dockerfile, I'm just going to `docker build && docker run`. If I see a makefile, I'm just going to run `make help ; make run || make`. It greatly reduces the cognitive load if I only want to quickly see what the project does.

rkwz 7y ago

I created something similar to what you described but using React - https://github.com/sheshbabu/starterkit https://github.com/sheshbabu/starterkit Real app built using this - https://github.com/sheshbabu/freshlytics https://github.com/sheshbabu/freshlytics