add FAQ about pushing to a new application #418
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
emirotin
reviewed
Feb 6, 2017
pages/troubleshooting/faq.md
Outdated
| @@ -26,6 +27,9 @@ title: FAQs | |||
| ##### Can I use multiple containers? | |||
| We are planning, and committed, to adding support for having multiple apps/containers running on a device. While the work towards multiple apps is in progress, as an interim solution, we do however have a few users running [multiple containers within an app via docker-compose](https://resin.io/blog/multi-container-with-docker-compose-on-resin-io/) and [have done work with kubernetes](https://resin.io/blog/our-first-experiments-with-multi-container-apps/) in the same fashion. | |||
|
|
|||
| ##### How do I push a new git repo to an Application? | |||
| If you have pushed a repository called `project-A` to your application (called `myapp`) and at a later stage you would like to push a new project called `project-B`, you can do this by adding the application remote (`git remote add resin joesoap@git.resin.io:joesoap/myapp.git`) to `project-B`'s local repository. You can then easily push `project-B` to `myapp` by just doing `git push resin master -f`. The extra `-f` on the command forces the push and resets the git history on the git remote on resin.io's backend. You should now have `project-B` running on all the devices in the `myapp` fleet. | |||
There was a problem hiding this comment.
Would add a line that after this one should normally not use -f anymore and do the regular pushes.
There was a problem hiding this comment.
As above, and maybe link for "more details on "force push" at https://git-scm.com/docs/git-push#git-push--f
imrehg
suggested changes
Feb 7, 2017
| @@ -26,6 +27,9 @@ title: FAQs | |||
| ##### Can I use multiple containers? | |||
| We are planning, and committed, to adding support for having multiple apps/containers running on a device. While the work towards multiple apps is in progress, as an interim solution, we do however have a few users running [multiple containers within an app via docker-compose](https://resin.io/blog/multi-container-with-docker-compose-on-resin-io/) and [have done work with kubernetes](https://resin.io/blog/our-first-experiments-with-multi-container-apps/) in the same fashion. | |||
|
|
|||
| ##### How do I push a new git repo to an Application? | |||
There was a problem hiding this comment.
capitalization of "application" maybe better lowercase??
pages/troubleshooting/faq.md
Outdated
| @@ -26,6 +27,9 @@ title: FAQs | |||
| ##### Can I use multiple containers? | |||
| We are planning, and committed, to adding support for having multiple apps/containers running on a device. While the work towards multiple apps is in progress, as an interim solution, we do however have a few users running [multiple containers within an app via docker-compose](https://resin.io/blog/multi-container-with-docker-compose-on-resin-io/) and [have done work with kubernetes](https://resin.io/blog/our-first-experiments-with-multi-container-apps/) in the same fashion. | |||
|
|
|||
| ##### How do I push a new git repo to an Application? | |||
| If you have pushed a repository called `project-A` to your application (called `myapp`) and at a later stage you would like to push a new project called `project-B`, you can do this by adding the application remote (`git remote add resin joesoap@git.resin.io:joesoap/myapp.git`) to `project-B`'s local repository. You can then easily push `project-B` to `myapp` by just doing `git push resin master -f`. The extra `-f` on the command forces the push and resets the git history on the git remote on resin.io's backend. You should now have `project-B` running on all the devices in the `myapp` fleet. | |||
There was a problem hiding this comment.
As above, and maybe link for "more details on "force push" at https://git-scm.com/docs/git-push#git-push--f
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #317