shift-org / shift-org/shift-docs
update netlify deploy process
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 25
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
we simplified things but now ./shift pull etc won't work, so let's adapt the netlify deploy process to do the right thing around:
- rebuilding hugo (using correct version that server uses)
- connects to new server not old server to restart upon prod deploy
- "does the right thing" upon prod deploy, probably
- not rebuilding dockerfile
- but yes pulling new content, running hugo, and restarting docker container (so node process picks up changes to node code)
- "does the right thing" upon prod deploy, probably
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Netlify deploy process and the ./shift pull workflow, checking how Hugo, the Dockerfile, and the Node process are currently handled. Done means production deploys use the server's Hugo version, pull new content, restart the Docker container, and avoid rebuilding the Dockerfile when appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, hugo, nodejs
- Domain
- build-system, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100