Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
If you can, have the repository locally and/or in a Git server. Use rsync to deploy updates to public_html. If the repository still needs to live in that same server, same applies (rsync, just loca...
Answer
#2: Post edited
by
. .
·
2020-09-03T19:44:16Z (over 4 years ago)
- If you can, have the repository locally and/or in a Git server. Use `rsync` to deploy updates to `public_html`.
If the repository still needs to live in that same server, same applies (`rsync`), but the repository lives under `$HOME`, not in `public_html`.
- If you can, have the repository locally and/or in a Git server. Use `rsync` to deploy updates to `public_html`.
- If the repository still needs to live in that same server, same applies (`rsync`, just locally and not remotely), but the repository lives under `$HOME`, not in `public_html`.
- You might replace `rsync` for `scp` (or `cp` locally) but when you can afford it because very small sites with negligible transfer times.
#1: Initial revision
by
. .
·
2020-09-03T19:42:23Z (over 4 years ago)
If you can, have the repository locally and/or in a Git server. Use `rsync` to deploy updates to `public_html`. If the repository still needs to live in that same server, same applies (`rsync`), but the repository lives under `$HOME`, not in `public_html`.