This ensures that Apache is fully setup before setting up mod-auth-pubtkt.
Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org>
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
There is no need to restart firewalld after the setup steps run.
Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org>
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
- Enable cached results when checking if the user is an admin. Cached results
are only invalid when a user newly get admin permission or when an existing
user loose admin permission. Here the consequence of showing wrong results is
minor.
- Use all small case for variable names.
- When we use a utility method from Plinth, we can trust it to give expected
values. Otherwise, we should fix the method to be more robust.
- Don't recommend the user to go to disks configuration page as there is not
much there to do to free up space. The action might be removing apps, deleting
downloaded content (downloaded via torrents) etc.
- df is unlikely to return '-1' for size of disk.
- Avoid using -1 as error value.
Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org>
- This avoids an issue where it would try to enable the apache conf
possibly before it is generated.
- Added an explicit enable statement since it was missing.
Reviewed-by: Joseph Nuthalpati <njoseph@thoughtworks.com>
Run sudo-required action via actions.superuser_run
Actions related to services those require `sudo` permissions need to
be executed via actions.superuser_run.
NOTE:
If plinth service is started via `sudo ./run --debug` (in dev mode)
all actions will be executed silently. But plinth in user machines
won't be executed with sudo permissions.
- add action commands for managing and running hooks
- adding template, view and url for managing and running hooks
- disable Plinth hook management on domain change
- Removed key generation for mod_auth_pubtkt from first boot.
- Running setup every time plinth starts so that new essential modules
can be setup properly.
Partially fixes#875
- Created basic plinth app which starts an introducer and a storage
node on the FreedomBox.
- Prompt user to set a domain name before creating Tahoe-LAFS nodes.
- Support adding and removing of introducers to the storage node.
- Serve Tahoe-LAFS from a different port.
- Start all nodes and introducers at system startup.
- Add utility class YAMLFile with test cases.
- Install mod_auth_pubtkt and generate public/private key-pair.
- Redirect user to login page if no cookie is presented.
- Add check for authenticated user for login page.
- Temporarily switched to DSA because of a bug in mod_auth_pubtkt
which causes it to accept only DSA and not RSA. Also had to use SHA1
instead of SHA256.
- Enabled SSO for Syncthing, Repro and TT-RSS.
- Using tokens to authorize by user groups.
- Generate keys during first boot.
