https://github.com/mhered/ros-test1
https://github.com/mhered/ros-test1
Last synced: 3 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/mhered/ros-test1
- Owner: mhered
- License: other
- Created: 2021-04-08T21:34:33.000Z (about 5 years ago)
- Default Branch: v2
- Last Pushed: 2021-04-08T21:34:34.000Z (about 5 years ago)
- Last Synced: 2025-12-29T07:21:10.630Z (5 months ago)
- Language: Dockerfile
- Size: 72.3 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.pdf
Awesome Lists containing this project
README
# Template: template-ros
This template provides a boilerplate repository
for developing ROS-based software in Duckietown.
**NOTE:** If you want to develop software that does not use
ROS, check out [this template](https://github.com/duckietown/template-basic).
## How to use it
### 1. Fork this repository
Use the fork button in the top-right corner of the github page to fork this template repository.
### 2. Create a new repository
Create a new repository on github.com while
specifying the newly forked template repository as
a template for your new repository.
### 3. Define dependencies
List the dependencies in the files `dependencies-apt.txt` and
`dependencies-py3.txt` (apt packages and pip packages respectively).
### 4. Place your code
Place your code in the directory `/packages/` of
your new repository.
### 5. Setup launchers
The directory `/launchers` can contain as many launchers (launching scripts)
as you want. A default launcher called `default.sh` must always be present.
If you create an executable script (i.e., a file with a valid shebang statement)
a launcher will be created for it. For example, the script file
`/launchers/my-launcher.sh` will be available inside the Docker image as the binary
`dt-launcher-my-launcher`.
When launching a new container, you can simply provide `dt-launcher-my-launcher` as
command.