3 ms·
> First and foremost is the idea of not tying your site's build process and hosting to a company that could go under. Sounds like you're imposing a complex bui
by seanwilson 7y ago
> First and foremost is the idea of not tying your site's build process and hosting to a company that could go under.
Sounds like you're imposing a complex build process on yourself while getting locked into a web of AWS features to be honest.
Could you not skip generating the PDF resume since you've already got the HTML version to keep life simple?
If you stick to running a basic NPM script to build your site there's little lock-in with Netlify. You could also build your site on a CI platform then push the generated pages + assets to Netlify after.
- xienze 7y ago> Sounds like you're imposing a complex build process on yourself while getting locked into a web of AWS features to be honest. I should elaborate a little. My whole site is contained within a Docker container that has NPM, Yarn, headless-chrome, Hugo, etc. I can generate everything with a single command. The AWS bits are just there for hosting and responding to a GitHub commit. So the build process is portable-ish, but from what I saw Netlify doesn’t just let you do headless-chrome on a free plan[1]. > Could you not skip generating the PDF resume Not really, the point is to automate everything away behind a single Git push. 1: https://community.netlify.com/t/using-zipped-binaries-how-to-actually-use-them/2740/12 https://community.netlify.com/t/using-zipped-binaries-how-to...
- seanwilson 7y agoWhy do you need a PDF resume that's built automatically though? Does it need to be in PDF? Does it change that often? Aren't resumes something you customise per job application?