rwnx / piku-dashboard Goto Github PK

• Establish a canonical formattings style and linter (Black?)
• capture version (some format like dev-requirements.txt: do not put this in the main requirements.txt otherwise piku will install it on deploy)
• Add documentation for running the linter
• Run the linter on the project (and commit the result)

piku dashboard already prevents you from stopping & destroying the dashboard application.

To prevent confusion, it should not show these buttons, either.

detect the dashboard app name by looking at the app directory, and remove the requirement to specify this in the environment.

1. add a version to the app in a __version__ var
2. display this somewhere in the app

The new version detection introduced in #34 is showing up when the app is already up to date.

Below: a screenshot of the piku_dashboard app at the current commit, and following the link through shows the same commit sha.

Technical stuff:

• I think this is because short git commit SHAs are actually 7 characters, not 6, like we slice them here
• I think we should avoid this entirely by returning the entire SHA from get_github_sha and use a startswith match in the template.

• piku-dashboard should start with a default admin/password configuration
• should be able to view, create, update and delete users to grant access to the platform
• a use with config/push rights should be able to reset the password state of the dashboard (i.e. by changing a config setting)
• admin should be prompted to reset password on first login

Technicals

• without a database, data could be serialized and stored in piku-dashboard's config variables
• passwords should be stored hashed

It would be nice if the password environment config (or however we're storing it) wasn't just the password in plaintext.

e.g.

made with love by Rowan ✨

or something soppy like that

To prep this project for contribution:

• Add github issue templates
  • e.g. https://github.com/rwnx/pynonymizer/blob/master/.github/ISSUE_TEMPLATE/bug_report.md
• Add CONTRIBUTING.md
  • Include info on code style and linting
    See example https://github.com/rwnx/pynonymizer/blob/master/CONTRIBUTING.md

Keep it lightweight but informative!

• I should be able to remove a config key from the "Manage Config" Screen
• This should be a button for each config item (suggestion pictured)

Add a CHANGELOG.md file in the keepachangelog format.

See example here: https://github.com/rwnx/pynonymizer/blob/master/CHANGELOG.md

It's scary! it's irreversable! it should prompt you!

• Add linting (see #24) checker to a github workflow that runs on PR
• Add test runner (if there are any)

Investigate and add latest hash info from the git repos for each app.

Also: investigate showing git history?

• When a fatal error occurs, page returns a generic 500 error
• It could display more information about the error
• It could display logs from the self_app

• we know the current commit SHA of the dashboard app
• we know the current main/version on the public github?
• The app should be able to tell you if it's out of date
• the app should link you to the latest version

First, sorry for writing an issue about this. But I figured that it would be easiest way to get in touch with you and knowing that code you wrote is being used is a great feeling.

I use this since 5 months and it is really great! I share my server with friends and this gives them easy access to logs and restarts etc. It has been really great so far and thanks for building this.

the piku cli can manage the number of uwsgi workers with the ps:scale command.

you should be able to control this from the dashboard for each application.

See https://github.com/piku/piku for more info.

Requires User Management #20

• it should be possible to grant users permissions to specific applications or

grant list (per app)

• can restart
• can view logs
• can destroy
• can manage config

Technicals

• store this as a bitmask? for size.

You can view and edit existing ones but you can't add a new one

Use an actual login prompt with html and styling!

1. it's prettier
2. it's better for browsers remembering passwords etc

At the moment there's no feedback for a dead link or incorrect appid

At the moment the config page just displays the form values in plaintext.

Ideally, these values should require pressing a button to reveal.