Frequently Asked Questions
Here you can find the most asked questions with answers. If you don't find an answer here, feel free to contact us.
The system is destined for plant parents who want to keep track of their plants in their home. Generally it can be used by any individual or entity, but it does not contain any eCommerce features, as it's solely dedicated to managing your plants.
According to the license you can modify the product to fit your needs and also redistribute it as long as it fits the MIT license.
It is a self-hosted system, so you need to run a web service in order to use the product. You can either run a server in your home or rent a server online. It is both ready for shared hosting as well as a docker environment.
No, as the admin of your workspace you can decide who also gets admin privileges. As opposed to general users, admins can manage the workspace settings, manage users and locations.
The system runs on PHP 8.3 using a custom framework and MariaDBas database. An SMTP mail server is highly recommended. Please see the installation notes for a detailed system requirements list
This is actually a bug in Google Chrome engine and there is already an issue open on Googles Bug Tracker. However, in the meantime, please see this Gist in order to see how to fix the issue:
Put this code in the admin settings under Environment -> Custom code for head section
<script>
document.addEventListener('DOMContentLoaded', function() {
let captElemens = document.querySelectorAll('input[type=file]');
for (i = 0; i < captElemens.length; i++) {
if (captElemens[i].accept.includes('image')) {
console.log(captElemens[i].accept);
captElemens[i].accept = 'image/*,android/force-camera-workaround';
}
}
});
</script>
Put this code in the admin settings under Environment -> Custom code for head section
Edit your docker-compose.yml as follows (using port 3310 as example here):
# In app.environment set port to 3310
DB_PORT: 3310
# In db section add MYSQL_TCP_PORT and expose as well as set new port values
environment:
...
MYSQL_TCP_PORT: 3310
ports:
- 3310:3310
expose:
- 3310
When registering a new API key, it will take some time for the key to be activated by OpenWeatherMap. Sometimes this only takes a few minutes, sometimes this can take up to an hour.
There is already a commit pushed, that will show a more user-friendly error message on the weather page, as well as prevent corrupting the dashboard.
You can read more about the error in the OpenWeatherMap FAQ, specifically the following part refers to that issue:
Your API key is not activated yet. Within the next couple of hours, it will be activated and ready to use.
There is already a commit pushed, that will show a more user-friendly error message on the weather page, as well as prevent corrupting the dashboard.
You can read more about the error in the OpenWeatherMap FAQ, specifically the following part refers to that issue:
Your API key is not activated yet. Within the next couple of hours, it will be activated and ready to use.
Still having questions?