Skip to content
/ starsky Public

Accelerator to find and organize images driven by meta information. Browse and search images in your own cloud.

License

Notifications You must be signed in to change notification settings

qdraw/starsky

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Starsky · GitHub license PRs Welcome GitHub all releases Docker GitHub Repo stars GitHub issues GitHub release (latest by date including pre-releases)

List of Starsky Projects

What is Starsky?

Check the introduction page to learn more about the scope of the application

Demo app

Starsky has a demo application online.

See the online demo

Is not needed to login, but you can create a new account

Project Readme

Install instructions for the server

This section deals with how to set up a Starsky system on-premises. You will find guides to all Starsky software for installation on-premises here.

General Project

The general application is Starsky solution (sln). You need to install the solution first.

Command line tools

The command tools to sync the database manually use Synchronize CLI to generate thumbnail use Thumbnail CLI. The Importer CLI can be used to copy files in a folder structure based on the creation datetime. The datetime structure can be configured.

To reverse geo code location information in images use the UI or the Geo CLI. Use your photo to track location and match this with your camera.With this tool you add a location trail (gpx) to a folder and match the datetime to images in the folder.

To publish files generate markup and images with a logo use the Web Html CLI. This publish web images to a content package. And when this is done you could copy a content package to a ftp service.

All these projects are separately compiled using the build script and using the same application settings (appsettings) configuration.

GitHub Issues

Pay attention

Please do not open an issue on GitHub, unless you have spotted an actual bug in Starsky.

Use GitHub Discussions to ask questions, bring up ideas, or other general items. Issues are not the place for questions, and will either be converted to a discussion or closed.

This policy is in place to avoid bugs being drowned out in a pile of sensible suggestions for future enhancements and calls for help from people who forget to check back if they get it and so on.

If a feature request is actually going to be built, it will get its own issue with the tag: Feature Request

Latest stable release

Release

Latest prerelease

GitHub release (latest by date including pre-releases)

Build status

Azure pipeline

Build Status

See ./pipelines/azure for details

Github Actions

Windows

Starsky .NET Core (Windows)

Ubuntu

Starsky .NET Core (Ubuntu) ClientApp React Linux CI

Docker

webapp-unstable-docker-buildx

App on Windows and Mac OS

The pipeline below is to test the Desktop build process. The .NET part isn't build in this pipeline, but it's needed to run the Desktop app.

starskyDesktop Electron PR (Missing .NET dependency)

A full build including the .NET dependency

Create Desktop Release on tag for .Net Core and Electron

See the documentation for details

End2End tests on ubuntu github actions ci environment

end2end on ubuntu-ci

See ./starsky-tools/end2end for details

Changelog and history of this project

There is a version log and backlog available on the history and changelog page

Codecov

codecov

Sonarqube

Coverage Bugs Code Smells Maintainability Rating Reliability Rating Vulnerabilities Lines of Code

Licence

MIT License

Authors