You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Updating-the-Project.md
+27-3Lines changed: 27 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,33 @@
1
1
# Updating the project
2
-
**If you ran the git checkout -- 'git ls-files -m' as suggested in the old wiki entry then please check your duck.sh because it removed your domain and token**
3
-
4
2
5
3
Periodically updates are made to project which include new or modified container template, changes to backups or additional features. As these are released your local copy of this project will become out of date. This section deals with how to bring your project to the latest published state.
6
4
5
+
Quick instructions:
6
+
7
+
1. backup your current settings: `cp docker-compose.yml docker-compose.yml.bak`
8
+
2. check `git status` for any local changes you may have made to project files. Save and preserve your changes by doing a commit: `git commit -a -m "local customization"`. Or revert them using: `git checkout -- path/to/changed_file`.
4. get latest images from the web: `docker-compose pull`
11
+
5. rebuild localy created images from new Dockerfiles: `docker-compose build --pull --no-cache`
12
+
6. update running containers to latest: `docker-compose up --build -d`
13
+
14
+
*Troubleshooting:* if a container fails to restart after update
15
+
* try restarting the whole stack: `docker-compose restart`
16
+
* backup your stack settings: `cp docker-compose.yml docker-compose.yml.bak`
17
+
* Check log output of the failing service: `docker-compose logs *service-name*`
18
+
* try googling and fixing problems in docker-compose.yml manually.
19
+
* try recreating the failing service definition using menu.sh:
20
+
*`./menu.sh`, select Build Stack, unselect the failing service, press enter
21
+
to build, and then exit.
22
+
*`./menu.sh`, select Build Stack, select the service back again, press enter
23
+
to build, and then exit.
24
+
* Try starting now: `docker-compose up -d`
25
+
* Go to the IOTStack Discord and ask for help.
26
+
27
+
## Details, partly outdated
28
+
29
+
**If you ran the git checkout -- 'git ls-files -m' as suggested in the old wiki entry then please check your duck.sh because it removed your domain and token**
30
+
7
31
Git offers build in functionality to fetch the latest changes.
8
32
9
33
`git pull origin master` will fetch the latest changes from GitHub without overwriting files that you have modified yourself. If you have done a local commit then your project may to handle a merge conflict.
@@ -18,4 +42,4 @@ With the new latest version of the project you can now use the menu to build you
After your stack had been rebuild you can run `docker-compose up -d` to pull in the latest changes. If you have not update your images in a while consider running the `./scripts/update.sh` to get the latest version of the image from Docker hub as well
45
+
After your stack had been rebuild you can run `docker-compose up -d` to pull in the latest changes. If you have not update your images in a while consider running the `./scripts/update.sh` to get the latest version of the image from Docker hub as well
0 commit comments