Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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 what to do, I’d say you’ll need a custom dockerfile, install node, run webpack in there and collect static.

If you are not using collectstatic in that process then given the lack of details I’d say why are you doing it in the same repo at all. But again – you provided very little details.

So if it is a website(server rendered pages, SEO is important,etc) - you should have node and do optimisations before pushing to s3.

If it is an app (RIA,SPA) then I’d say don’t mix frontend and backend. Decouple it and ship frontend separately.

Appliku Interface is built and served with Netlify. I still remember those dark times when I had frontend inside the main repo. It was largely inconvenient.

Either way happy to chat about your issues in our discord server. I am more than happy to help you figuring this out.



Yes well separation of frontend/backend is of course a good idea, but most of the projects are mostly django templates with some React sprinkled on top to make interaction and interfaces nicer. It's also a good idea if you have just a single project or a few of them.

I'm talking about maybe 30-40 projects with django as base so it would make my job so much more complicated if I would split them all up in repos.

The frontend code is mostly isolated but is shipped in the same repo to be built and distributed for django to find.

So your answer about a custom dockerfile is probably what would be needed.


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.com/KostjaPalovic or in our discord https://appliku.com/discord




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: