The Fastlane Match documentation suggests putting certificates in a private git repo. If my project repo is already private is there any reason to not put the certificates into the project repo? Say in a /certificates directory?
Obviously it would be paramount not to deploy these certificates with any kind of release.
If you use your signing identity for more than one project you would need to store it in every repository. When you need to update it you need to update it in every repository, thus it would be better to have it only in one place. The signing identity is (most likely) not specific to the one project.
Related
I'm working with a Electron project, and now I want to push it to my Github repository, but I don't know what file I should push. Can any body tell me what file should I push?
You can push any files you wish…
You will probably not want to push your IDE settings directory, perhaps unless you are the only person working on your application. Of course, when you make changes to any of your IDE settings, they will be reflected in your GIT status and require pushing as well if not ignored.
Most people do not push their node_modules folder due to the sheer size and frequency of updates it often receives. That said, there is talk that pushing your node_modules folder will prevent future issues should a package maintainer pull a package from NPM that you depend upon.
Lastly, I do not include my build or dist directories as these are quite large, contain binaries and are not really that useful until your final release, after which you will normally distribute it on a platform such as an app store, your own website or update server (or Github).
I've been looking for a solution how to manage my project with git for quite some time now. I want to have one instance as the main repo for connecting the entire project. Each app should be its own git instance.
During my search I found both git submodule and git subtree. For both tools I found an instruction how to insert an existing reppo. However, I am interested in how to proceed from the beginning. I mean here from the command $ django-admin startproject myproject Where do I enter the git init? When I create a new app
$ django-admin startapp new-app and how do I use this as subtree/submodule?
Until now I have always found instructions that refer to a remote repo. Is this always necessary? I am not sure if I want to publish every Django app on Github. But I want a version control system just for me. Is this possible?
I have to say that so far it has been enough to manage my "projects" locally. Now I want to work together with others and I don't want to install the whole Django Project locally but only provide me with single functions or modules.
It would be a great help if you could explain to me how that works.
TL;DR
How to manage (start and expand) a Django Project with git. The apps should be their own git repos.
The purpose of submodules is to allow you to graft an existing repo/library into your git. Rarely do you want to do this. Instead you want to use PIP tools to install your libraries as part of library management.
This is essentially a git question. If you don't have a remote repository, you can still use git. With that said, the reason you want a remote repository is so that you can collaborate with others, and have a stored version of the code separate from your workstation.
There are services that let you have private repos even without a paid account. Bitbucket is the most well known of these services and is comparable to Github in most ways.
I've multiple projects configured exactly the same way using the same VCS root. All that changes for the projects is the project name, so to keep things DRY I share the root with the following fetch url:
git#github.com:<myorg>/%conf.GitProjectName%.git
For one single project this fails with:
List remote refs failed: cannot locate repository at git#github.com:<myorg>/<My project>.git: ERROR: Repository not found.
This is really weird and I can clone the git repo using git#github.com:<myorg>/<My project>.git without any problem. Any idea about how to debug this?
This was not due to teamcity, it was because of github's new way to give teams rights to a repository which wasn't there before I think. Didn't delete the question to help other that might have the problem.
I've failed to add two or more github reps to teamcity using the same private key. I've generated another private/public pair, added public key to github for new repo, then added private key into teamcity. This worked for me. Hope it helps.
I recently inherited a project that used to be setup with Github for version control. However, due to lack of communication from the original developer, I'm left with code base that lives on the production. Question I have is if it's possible to recover a code repo in Github given that I have the .git folder that contains all git related files?
If there's an existing .git folder, it's probably an existing git repository. You could just follow the instructions for adding an existing project to Github and get it that way.
I have a remote in git
It contains a project already.
I'm using eclipse and sourceTree.
how can I add a newly created project to it?
by project I mean another code folder which depend on the already uploaded project.
You are probably going to run into at least one problem here: Eclipse will expect the existing project in the remote to be rooted at the root of repository (which I assume it currently is?)
I would just create a new repository, it's going to be simpler. On GitHub you can create an organization to group related repositories together.