You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- This is some great information, thank you. I do have a couple of follow up questions, that may sound a bit noobish. First, why is it not a good idea to deploy with git? I can see how my need to name things differently due to them being on the same server is an issue, but what if my local repo and production repos were on completely separate drives with no chance of naming conflicts? Would there still be issues?confused_nomad– confused_nomad2022-09-08 15:09:06 +00:00Commented Sep 8, 2022 at 15:09
- Second question here for clarity. Due to being self-taught, I'm a bit fuzzy on what you mean by 'deploy the application.' Does this simply mean somehow pushing updates to your live code, or is there some other containment process here that I'm missing? (And I don't mean containers like Docker or anything like that)confused_nomad– confused_nomad2022-09-08 15:10:48 +00:00Commented Sep 8, 2022 at 15:10
- @confused_nomad: deploying typically means moving the files to the servers, applying configuration changes, and perhaps even data updates. This could also include making a backup copy of files, if necessary. Basically all the steps it takes to put updated application code out on to the servers. As for why Git is not good for deployments? That is situational. You can "git pull" from the servers, but that assumes you only need app code changes. As soon as your deployments need more than that, Git becomes useless.Greg Burghardt– Greg Burghardt2022-09-08 15:40:48 +00:00Commented Sep 8, 2022 at 15:40
- I just realized something and don't know why I didn't mention it earlier, but the post-receive hook in the bare repo is a shell script. Does this still go against the steps you were recommending?confused_nomad– confused_nomad2022-09-08 18:51:07 +00:00Commented Sep 8, 2022 at 18:51
- @confused_nomad: it still executes as part of your version control workflow. This couples version control to deployment, and yes, it go against the steps I am recommending.Greg Burghardt– Greg Burghardt2022-09-08 19:40:20 +00:00Commented Sep 8, 2022 at 19:40
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you