DietPi-Software | TasmoAdmin

[svh1985]

Creating a software request

Formal software information

• Software title | TasmoAdmin
• Short description | TasmoAdmin is an administrative Website for Devices flashed with Sonoff-Tasmota.
• GitHub URL (if available) | https://github.com/reloxx13/TasmoAdmin

How can DietPi make the installation easier or compatible, than following the install instructions or do APT installation, if available?

• Via dietpi-software is always better :)

Can you provide the installation steps that you would suggest DietPi-Software to do?

1. Install webserver stack
2. Install php-curl php-zip

Are you willing to help maintaining the software installation, e.g. in case of needed setup changes due to updates etc.? This is not needed, but could speed up our decision to implement it, as man power is always a topic :wink:.

Yes!

Vote for this software on FeatHub: https://feathub.com/MichaIng/DietPi/+79

[svh1985]

I think I can implement this myself just need some help here and there :)
Especially with the webserver virtual dir config :)

Will be my first software title.

I'll start a PR if you like it and give the thumbs up

[MichaIng]

@svh1985
Sounds interesting. Jep feel free to send a PR, which will speed up implementation of course. Btw regarding your post in the other topic, I added an updated HowTo to the wiki about how to implement software: https://github.com/MichaIng/DietPi/wiki/How-to-add-a-new-software-title

[svh1985]

@MichaIng So I've been working on this but for some reason my DietPi Fork is a bit messed up. My previous pull requests were already merged for the v2.26, is it safe to delete my Fork on github and fork it again for the TasmoAdmin pull request?

ps. I made sure I had the latest files :) did a double check to make sure.

[MichaIng]

@svh1985
If you want to be sure that everything has been merged, you could open a test PR.
Indeed if everything has been merged, cleanest would be a fresh fork.

[MichaIng]

@svh1985
Modules cannot be enabled per-dir, since those need to be enabled on initial daemon start. There are many other webserver applications which require mod_rewrite, so simply enable it server-wide.

The rewrite rules however should be added to a separate config file, usually this would be:

• /etc/apache2/sites-available/dietpi-tasmoadmin.conf on Apache + a2ensite dietpi-tasmoadmin
• /etc/nginx/sites-dietpi/dietpi-tasmoadmin.conf on Nginx
• /etc/lighttpd/conf-available/99-dietpi-tasmoadmin.conf on Lighttpd + lighttpd-enable-mod dietpi-tasmoadmin

The rewrite rules then often need to be placed outside of any location/directory block (although depends on if those are internal rewrites when accessing the web UI already or API-kind redirects so that external clients are redirected to the correct endpoints from base domain/URL), other permission-like directives then inside the /var/www/tasmoadmin directory, respectively /tasmoadmin location/URL block.

Just as an example check out the Nextcloud configs: https://github.com/MichaIng/DietPi/tree/dev/.conf/dps_114

However would be okay if you just add the config for the webserver(s) you are familiar with or have docs from TasmoAdmin, I can translate those for the other webserver(s) then.

[svh1985]

@svh1985
Modules cannot be enabled per-dir, since those need to be enabled on initial daemon start. There are many other webserver applications which require mod_rewrite, so simply enable it server-wide.

The rewrite rules however should be added to a separate config file, usually this would be:

• /etc/apache2/sites-available/dietpi-tasmoadmin.conf on Apache + a2ensite dietpi-tasmoadmin
• /etc/nginx/sites-dietpi/dietpi-tasmoadmin.conf on Nginx
• /etc/lighttpd/conf-available/99-dietpi-tasmoadmin.conf on Lighttpd + lighttpd-enable-mod dietpi-tasmoadmin

The rewrite rules then often need to be placed outside of any location/directory block (although depends on if those are internal rewrites when accessing the web UI already or API-kind redirects so that external clients are redirected to the correct endpoints from base domain/URL), other permission-like directives then inside the /var/www/tasmoadmin directory, respectively /tasmoadmin location/URL block.

Just as an example check out the Nextcloud configs: https://github.com/MichaIng/DietPi/tree/dev/.conf/dps_114

However would be okay if you just add the config for the webserver(s) you are familiar with or have docs from TasmoAdmin, I can translate those for the other webserver(s) then.

I've pushed the config for Apache: https://github.com/MichaIng/DietPi/pull/3143/commits/3a16b5a9f75f56d00e6b68049d1ec3c65bd33f2b
For lighthttpd I found this: https://github.com/reloxx13/TasmoAdmin/issues/155

[MichaIng]

@svh1985
Ah yeah its .htaccess based, so Lighttpd + Nginx configs should be based on: https://github.com/reloxx13/TasmoAdmin/blob/master/tasmoadmin/.htaccess

• Largest parts are indeed the rewrites, the issue you posted handles some of them, but not all. Requires some fiddling to get this running, so from my side nothing I can do for v6.26 release anymore, but will definitely start working on it for v6.27. We can then also contribute this to TasmoAdmin project, at least Wiki.
• What I really like, is the robots/search crawler protection. This is something we can add to other web applications as well, where you don't want content to be listed on search engines or simply reduce server load.

[MichaIng]

Implementation has been merged into development branch: #3143
Changelog: https://github.com/MichaIng/DietPi/commit/b0df302cc11abc81ae73cfdbd1ae4a0ef0921387
Online docs: https://dietpi.com/phpbb/viewtopic.php?p=20584#p20584