kopia lustrzana https://github.com/OpenDroneMap/docs
fix code blocks for real
rodzic
b215c3af21
commit
8ef8e8c1b5
|
@ -1001,6 +1001,7 @@ Fork and clone repository
|
||||||
First, let's fork the ODM repo, and checkout a new branch locally that will function as our development branch.
|
First, let's fork the ODM repo, and checkout a new branch locally that will function as our development branch.
|
||||||
|
|
||||||
:: bash
|
:: bash
|
||||||
|
|
||||||
git checkout -b my_clever_new_change
|
git checkout -b my_clever_new_change
|
||||||
# Switched to a new branch 'my_clever_new_change'
|
# Switched to a new branch 'my_clever_new_change'
|
||||||
|
|
||||||
|
@ -1010,6 +1011,7 @@ Set up local NodeODM docker instance
|
||||||
Next, we will set up a NodeODM instance with a locally mounted volume that points to our development branch of ODM
|
Next, we will set up a NodeODM instance with a locally mounted volume that points to our development branch of ODM
|
||||||
|
|
||||||
:: bash
|
:: bash
|
||||||
|
|
||||||
docker run -d --restart unless-stopped -p 3000:3000 -v /path/to/cloned/ODM/repository/data:/code opendronemap/nodeodm
|
docker run -d --restart unless-stopped -p 3000:3000 -v /path/to/cloned/ODM/repository/data:/code opendronemap/nodeodm
|
||||||
|
|
||||||
Modify code
|
Modify code
|
||||||
|
@ -1028,6 +1030,7 @@ Connect to NodeODM instance
|
||||||
Let us find out our container name, in case we forgot:
|
Let us find out our container name, in case we forgot:
|
||||||
|
|
||||||
:: bash
|
:: bash
|
||||||
|
|
||||||
docker ps
|
docker ps
|
||||||
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
|
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
|
||||||
c997a4c5611b opendronemap/nodeodm "/usr/bin/node /var/…" 2 minutes ago Up 2 minutes 0.0.0.0:3000->3000/tcp, :::3000->3000/tcp affectionate_yalow
|
c997a4c5611b opendronemap/nodeodm "/usr/bin/node /var/…" 2 minutes ago Up 2 minutes 0.0.0.0:3000->3000/tcp, :::3000->3000/tcp affectionate_yalow
|
||||||
|
@ -1035,6 +1038,7 @@ Let us find out our container name, in case we forgot:
|
||||||
Now that we know the container name, we will connect to that instance using docker exec as follows:
|
Now that we know the container name, we will connect to that instance using docker exec as follows:
|
||||||
|
|
||||||
:: bash
|
:: bash
|
||||||
|
|
||||||
docker exec -it affectionate_yalow bash
|
docker exec -it affectionate_yalow bash
|
||||||
|
|
||||||
Install and use changes
|
Install and use changes
|
||||||
|
@ -1043,6 +1047,7 @@ Install and use changes
|
||||||
Let us get the environment prepared for our testing:
|
Let us get the environment prepared for our testing:
|
||||||
|
|
||||||
:: bash
|
:: bash
|
||||||
|
|
||||||
root@c997a4c5611b:/var/www# cd /code
|
root@c997a4c5611b:/var/www# cd /code
|
||||||
./configure.sh installruntimedepsonly
|
./configure.sh installruntimedepsonly
|
||||||
mkdir /code/SuperBuild/build
|
mkdir /code/SuperBuild/build
|
||||||
|
@ -1051,7 +1056,8 @@ Let us get the environment prepared for our testing:
|
||||||
|
|
||||||
Next we can rebuild Ceres.
|
Next we can rebuild Ceres.
|
||||||
|
|
||||||
:: code-block:: bash
|
:: bash
|
||||||
|
|
||||||
cmake ../.
|
cmake ../.
|
||||||
make -j$(nproc) ceres
|
make -j$(nproc) ceres
|
||||||
...
|
...
|
||||||
|
|
Ładowanie…
Reference in New Issue