4 ms·
I tried deploying my DRF backend[1] + Nuxt.js[2] demo-app on Heroku[3] as one repo but it was a NIGHTMARE. Yes, it sucks to have to open both projects in my IDE
by shibel 7y ago
I tried deploying my DRF backend[1] + Nuxt.js[2] demo-app on Heroku[3] as one repo but it was a NIGHTMARE. Yes, it sucks to have to open both projects in my IDE in development, but it's nowhere near the difficulty I had with the mono-repo. Plus, I can find things much faster within each project when they are split.
[1]: backend → https://github.com/SHxKM/django-vue-ssr https://github.com/SHxKM/django-vue-ssr
[2]: frontend → https://github.com/SHxKM/django-nuxt-ssr-front https://github.com/SHxKM/django-nuxt-ssr-front
[3]: live-app → https://django-nuxt-ssr.herokuapp.com/ https://django-nuxt-ssr.herokuapp.com/ (on a free dyno, could crash on first load)
- nicoburns 7y agoI've settled on a many-repos-in-same-parent-folder pattern, which means that I can open them all in the same editor window if I want to. I've also forgone proper IDE "project" in favour of opening the directory in my editor on an ad-hoc basis from the command line (e.g. `cd frontend && subl .`). It's not perfect, but it avoids the issue of having too many windows, or having to fumble through IDE project switching dialogs.
- deleted 7y ago[deleted]
- shibel 7y agoYeah, the "issue" for me is spinning up the backend-server from the frontend project, or vice-versa, but I should probably stop being lazy and write a simple script to spin up both at the same time.
- is0tope 7y agoI highly reccomend tryi g out docker compose if you are doing this kind of thing.