13 KiB
Management
Providing Assets
Although not essential, you will most likely want to provide several assets to Dashy. All web assets can be found in the /public directory.
For example:
./public/conf.yml- As mentioned, this is your main application config file./public/item-icons- If you're using your own icons, you can choose to store them locally for better load time, and this is the directory to put them in. You can also use sub-folders here to keep things organized- Also within
./publicyou'll find standard website assets, includingfavicon.ico,manifest.json,robots.txt, etc. There's no need to pass these in, but you can do so if you wish
This is easy to do using Docker Volumes, which lets you share a file or directory between your host system, and the container. Volumes are specified in the Docker run command, or Docker compose file, using the --volume or -v flags. The value of which consists of the path to the file / directory on your host system, followed by the destination path within the container. Fields are separated by a colon (:), and must be in the correct order. For example: -v ~/alicia/my-local-conf.yml:/app/public/conf.yml
Running Commands
The project has a few commands that can be used for various tasks, you can find a list of these either in the Developing Docs, or by looking at the package.json. These can be used by running yarn [command-name].
But if you're using Docker, then you'll need to execute them within the container. This can be done by preceding each command with docker exec -it [container-id], where container ID can be found by running docker ps. For example docker exec -it 26c156c467b4 yarn build. You can also enter the container, with docker exec -it [container-id] /bin/ash, and navigate around it with normal Linux commands.
Healthchecks
Healthchecks are configured to periodically check that Dashy is up and running correctly on the specified port. By default, the health script is called every 5 minutes, but this can be modified with the --health-interval option. You can check the current container health with: docker inspect --format "{{json .State.Health }}" [container-id], and a summary of health status will show up under docker ps. You can also manually request the current application status by running docker exec -it [container-id] yarn health-check. You can disable healthchecks altogether by adding the --no-healthcheck flag to your Docker run command.
To restart unhealthy containers automatically, check out Autoheal. This image watches for unhealthy containers, and automatically triggers a restart. This is a stand in for Docker's --exit-on-unhealthy that was proposed, but not merged.
Logs and Performance
Container Logs
You can view logs for a given Docker container with docker logs [container-id], add the --follow flag to stream the logs. For more info, see the Logging Documentation. There's also Dozzle, a useful tool, that provides a web interface where you can stream and query logs from all your running containers from a single web app.
Container Performance
You can check the resource usage for your running Docker containers with docker stats or docker stats [container-id]. For more info, see the Stats Documentation. There's also cAdvisor, a useful web app for viewing and analyzing resource usage and performance of all your running containers.
Management Apps
You can also view logs, resource usage and other info as well as manage your entire Docker workflow in third-party Docker management apps. For example Portainer an all-in-one open source management web UI for Docker and Kubernetes, or LazyDocker a terminal UI for Docker container management and monitoring.
Advanced Logging and Monitoring
Docker supports using Prometheus to collect logs, which can then be visualized using a platform like Grafana. For more info, see this guide. If you need to route your logs to a remote syslog, then consider using logspout. For enterprise-grade instances, there are managed services, that make monitoring container logs and metrics very easy, such as Sematext with Logagent.
Auto-Starting at System Boot
You can use Docker's restart policies to instruct the container to start after a system reboot, or restart after a crash. Just add the --restart=always flag to your Docker compose script or Docker run command. For more information, see the docs on Starting Containers Automatically.
For Podman, you can use systemd to create a service that launches your container, the docs explains things further. A similar approach can be used with Docker, if you need to start containers after a reboot, but before any user interaction.
To restart the container after something within it has crashed, consider using docker-autoheal by @willfarrell, a service that monitors and restarts unhealthy containers. For more info, see the Healthchecks section above.
Securing
SSL
Enabling HTTPS with an SSL certificate is recommended if you hare hosting Dashy anywhere other than your home. This will ensure that all traffic is encrypted in transit.
Let's Encrypt is a global Certificate Authority, providing free SSL/TLS Domain Validation certificates in order to enable secure HTTPS access to your website. They have good browser/ OS compatibility with their ISRG X1 and DST CA X3 root certificates, support Wildcard issuance done via ACMEv2 using the DNS-01 and have Multi-Perspective Validation. Let's Encrypt provide CertBot an easy app for generating and setting up an SSL certificate
ZeroSSL is another popular certificate issuer, they are free for personal use, and also provide easy-to-use tools for getting things setup.
If you're hosting Dashy behind Cloudflare, then they offer free and easy SSL.
If you're not so comfortable on the command line, then you can use a tool like SSL For Free to generate your Let's Encrypt or ZeroSSL certificate, and support shared hosting servers. They also provide step-by-step tutorials on setting up your certificate on most common platforms. If you are using shared hosting, you may find this tutorial helpful.
Authentication
Dashy has basic authentication built in, however at present this is handled on the front-end, and so where security is critical, it is recommended to use an alternative method. See here for options regarding securing Dashy.
Updating
Dashy is under active development, so to take advantage of the latest features, you may need to update your instance every now and again.
Updating Docker Container
- Pull latest image:
docker pull lissy93/dashy:latest - Kill off existing container
- Find container ID:
docker ps - Stop container:
docker stop [container_id] - Remove container:
docker rm [container_id]
- Find container ID:
- Spin up new container:
docker run [params] lissy93/dashy
Automatic Docker Updates
You can automate the above process using Watchtower. Watchtower will watch for new versions of a given image on Docker Hub, pull down your new image, gracefully shut down your existing container and restart it with the same options that were used when it was deployed initially.
To get started, spin up the watchtower container:
docker run -d \
--name watchtower \
-v /var/run/docker.sock:/var/run/docker.sock \
containrrr/watchtower
For more information, see the Watchtower Docs
Updating Dashy from Source
- Navigate into directory:
cd ./dashy - Stop your current instance
- Pull latest code:
git pull origin master - Re-build:
yarn build - Start:
yarn start
Web Server Configuration
The following section only applies if you are not using Docker, and would like to use your own web server
Dashy ships with a pre-configured Node.js server, in server.js which serves up the contents of the ./dist directory on a given port. You can start the server by running node server. Note that the app must have been build (run yarn build), and you need Node.js installed.
If you wish to run Dashy from a sub page (e.g. example.com/dashy), then just set the BASE_URL environmental variable to that page name (in this example, /dashy), before building the app, and the path to all assets will then resolve to the new path, instead of ./.
However, since Dashy is just a static web application, it can be served with whatever server you like. The following section outlines how you can configure a web server.
Note, that if you choose not to use server.js to serve up the app, you will loose access to the following features:
- Loading page, while the app is building
- Writing config file to disk from the UI
- Website status indicators, and ping checks
NGINX
Create a new file in /etc/nginx/sites-enabled/dashy
server {
listen 80;
listen [::]:80;
root /var/www/dashy/html;
index index.html;
server_name your-domain.com www.your-domain.com;
location / {
try_files $uri $uri/ =404;
}
}
Then upload the build contents of Dashy's dist directory to that location.
For example: scp -r ./dist/* [username]@[server_ip]:/var/www/dashy/html
Apache
Copy Dashy's dist folder to your apache server, sudo cp -r ./dashy/dist /var/www/html/dashy.
In your Apache config, /etc/apche2/apache2.conf add:
<Directory /var/www/html>
Options Indexes FollowSymLinks
AllowOverride All
Require all granted
</Directory>
Add a .htaccess file within /var/www/html/dashy/.htaccess, and add:
Options -MultiViews
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^ index.html [QSA,L]
Then restart Apache, with sudo systemctl restart apache2
cPanel
- Login to your WHM
- Open 'Feature Manager' on the left sidebar
- Under 'Manage feature list', click 'Edit'
- Find 'Application manager' in the list, enable it and hit 'Save'
- Log into your users cPanel account, and under 'Software' find 'Application Manager'
- Click 'Register Application', fill in the form using the path that Dashy is located, and choose a domain, and hit 'Save'
- The application should now show up in the list, click 'Ensure dependencies', and move the toggle switch to 'Enabled'
- If you need to change the port, click 'Add environmental variable', give it the name 'PORT', choose a port number and press 'Save'.
- Dashy should now be running at your selected path an on a given port
Authentication
Dashy has built-in authentication and login functionality. However, since this is handled on the client-side, if you are using Dashy in security-critical situations, it is recommended to use an alternate method for authentication, such as Authelia, a VPN or web server and firewall rules. For more info, see Authentication Docs.