It would be very useful for future contributors if it was possible to develop and execute Mentat modules from within the cloned Git repository. Currently the development process is little bit awkward. Part of this task is also writing the manual for developer and contributors.
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
Radko, could you please walk through these installation instructions and attempt to install working Mentat instance from Debian package and local Git repository to verify the installation instructions. I am striving to make the installation process as simple as possible and if you are not able to have working instance in half an hour this task should be improved further.
I have tested the instructions for manual installation.
Here are some other remarks:
What I am missing is a mention that the steps have to be run as root. Using sudo (in various places where required) will not result in a working installation as the environment is very different from what seems to be expected. (I have not tested this thoroughly, I might have been trying to install the stable version [2.3.2] at the time).
I advise to include the installation commands for postgresql and ip4r and the mention that the server must listen on port 5432. For a clean installation, it would be highly beneficial. We should not expect the Mentat admin to be a PostgreSQL admin also (or to read the documentation to a third-party extension).
The development documentation should probably reference the development repositories for mentat, not the stable ones (steps 2 and 3).
In step 9, the /etc/mentat/scripts/sqldb-migrate.sh stamp head command has to be run inside the venv, otherwise it fails with alembic: command not found
Unfortunately it took me quite a bit longer than the agreed limit of half and hour to get the mentat working.
I have not yet tried the git repository instructions.
I have tested the instructions for manual installation.
Here are some other remarks:
What I am missing is a mention that the steps have to be run as root. Using sudo (in various places where required) will not result in a working installation as the environment is very different from what seems to be expected. (I have not tested this thoroughly, I might have been trying to install the stable version [2.3.2] at the time).
Done.
I advise to include the installation commands for postgresql and ip4r and the mention that the server must listen on port 5432. For a clean installation, it would be highly beneficial. We should not expect the Mentat admin to be a PostgreSQL admin also (or to read the documentation to a third-party extension).
Done, added section about installation of prerequisites.
The development documentation should probably reference the development repositories for mentat, not the stable ones (steps 2 and 3).
Sadly, this is not possible. To my knowledge and according to my research RST does not allow variable substitutions in code blocks.
In step 9, the /etc/mentat/scripts/sqldb-migrate.sh stamp head command has to be run inside the venv, otherwise it fails with alembic: command not found
Done.
Unfortunately it took me quite a bit longer than the agreed limit of half and hour to get the mentat working.
I have not yet tried the git repository instructions.
Pavel, during our conference you have volunteered to perform another test installation. Do you still have time to do it? If not, we can close the issue a polish the instructions later. I think, that all changes at this point should be purely cosmetic, as I have already tested the installation many times.