Mgrating a server into a repository
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone/push Build is passing
Details
Closes coop-cloud/organising#323
This commit is contained in:
parent
f0fcef3d18
commit
9ea777de1b
|
@ -82,6 +82,18 @@ Then, tell your collaborators (e.g. in the repository's `README.md`), to run `ma
|
|||
|
||||
We don't currently recommend this, because it might set inaccurate expectations about the security model – remember that, by default, **any user who can deploy apps to a Docker Swarm can manage _any_ app in that swarm**.
|
||||
|
||||
### Migrating a server into a repository
|
||||
|
||||
Even if you've got your existing server configs in version control, by default, `abra server add` will define the server locally. To move it -- taking the example of `newserver.example.com`:
|
||||
|
||||
```
|
||||
mv ~/.abra/servers/newserver.example.com ~/coop-cloud-apps/
|
||||
cd ~/coop-cloud-apps
|
||||
git add newserver.example.com
|
||||
git commit
|
||||
make link
|
||||
```
|
||||
|
||||
## Running abra server side
|
||||
|
||||
If you're on an environment where it's hard to run Docker, or command-line programs in general, you might want to install `abra` on a server instead of your local work station.
|
||||
|
|
Loading…
Reference in New Issue