Sign inSign up

davewalker5/droneflightlogmvc

By davewalker5

•Updated about 2 months ago

SQLite based drone/UAV flight logging application : ASP.NET Core MVC UI component

Image
0

1.4K

davewalker5/droneflightlogmvc repository overview

⁠droneflightlogmvc

The Drone Flight Log is a personal UAV flight logging application implemented using .NET Core. It has the following components:

NameGitHubComments
DroneFlightLogDbDroneFlightLogDb⁠Business logic, entities and database implementation
DroneFlightLog.ApiDroneFlightLog.Api⁠REST API for reading and writing to the database
DroneFlightLog.MvcDroneFlightLog.Mvc⁠ASP.NET MVC UI for accessing the database via the service

The application provides facilities for recording and querying the following data:

  • Operator details
  • Drones, models and manufacturers
  • Flights, flight locations and flight properties

The droneflightlogmvc image contains a build of the web-based MVC user interface.

⁠Getting Started

⁠Prerequisities

In order to run this image you'll need docker installed.

⁠Usage
⁠Service Container Parameters

An instance of the dronefilghtlogapisqlite image must be started first in order for the UI to work. The recommended parameters are:

ParameterValuePurpose
-d-Run as a background process
-v/local:/var/opt/droneflightlog.apiMount the host folder containing the SQLite database
--namedroneflightlogserviceName the service so the UI can find it
--rm-Remove the container automatically when it stops

The "/local" path given to the -v argument is described, below, and should be replaced with a value appropriate for the host running the container.

The "--name" parameter is mandatory as the service URL is held in the application settings for the UI image and is expected to be:

http://droneflightlogservice:80⁠

⁠UI Container Parameters

The following "docker run" parameters are recommended when running the droneflightlogmvc image:

ParameterValuePurpose
-d-Run as a background process
-p5001:80Expose the container's port 80 as port 5001 on the host
--linkdroneflightlogserviceLink to the drone flight log service container
--rm-Remove the container automatically when it stops

For example:

docker run -d -p 5001:80 --rm --link droneflightlogservice davewalker5/droneflightlogmvc:latest

The port number "5001" can be replaced with any available port on the host.

⁠Volumes

The description of the container parameters, above, specifies that a folder containing the SQLite database file for the Drone Flight Log is mounted in the running container, using the "-v" parameter.

That folder should contain a SQLite database that has been created using the instructions in the Drone Flight Log wiki⁠.

Specifically, the following should be done:

The folder containing the "droneflightlog.db" file can then be passed to the "docker run" command using the "-v" parameter.

⁠Running the Image

To run the images for the service and UI, enter the following commands, substituting "/local" for the host folder containing the SQLite database, as described:

docker run -d -v  /local:/var/opt/droneflightlog.api/ --name droneflightlogservice --rm  davewalker5/droneflightlogapisqlite:latest
docker run -d -p 5001:80 --rm --link droneflightlogservice davewalker5/droneflightlogmvc:latest

Once the container is running, browse to the following URL on the host:

http://localhost:5001⁠

You should see the login page for the UI.

⁠Find Us

⁠Versioning

For the versions available, see the tags on this repository⁠.

⁠Authors

See also the list of contributors⁠ who participated in this project.

⁠License

This project is licensed under the MIT License - see the LICENSE⁠ file for details.

Tag summary

Content type

Image

Digest

sha256:5c8744d8b…

Size

143.4 MB

Last updated

about 2 months ago

docker pull davewalker5/droneflightlogmvc