Re: Changing .ssh/authorized_keys script
Hi Mads, Thanks for the quick response. Yes, that was exactly what was needed. And yes, I wanted to steer clear of the warning about manually editing the file. All the best --Louis From: Mads Kiilerich Sent: Thursday, May 20, 2021 5:01 PM To: Louis Bertrand; kallithea-general@sfconservancy.org Subject: Re: Changing .ssh/authorized_keys script [EXTERNAL EMAIL] On 5/19/21 4:21 PM, Louis Bertrand wrote: > Hello, > > When I upgraded Kallithea, I somehow changed the venv directory from > ~/kallithea-venv to kallithea/venv. In other words, instead of a venv > directory beside the kallithea directory, it's now under the directory. > > Everything is fine except for ssh access because the cli script has moved. I > updated the path > > kallithea_cli_path = > /srv/web/sites/hg.set.durhamcollege.org/kallithea/venv/bin/kallithea-cli > However the .ssh/authorized_keys file needs to be updated. There is a way to update authorized_keys. See the last section in https://kallithea.readthedocs.io/en/default/setup.html#using-kallithea-with-ssh : The ``authorized_keys`` file can be updated manually with ``kallithea-cli ssh-update-authorized-keys -c my.ini``. > Is there a way to edit the file without invalidating it? (I'm not sure what is meant with "edit without invalidating" - is it "make it rewrite the file even though nothing changed that could trigger it"?) /Mads This message is intended only for the named recipients. This message may contain information that is confidential or exempt from disclosure under applicable law. Any dissemination or copying of this message by anyone other than a named recipient is strictly prohibited. If you are not a named recipient or an employee or agent responsible for delivering this message to a named recipient, please notify us immediately, and permanently destroy this message and any copies you may have. Warning: Email may not be secure unless properly encrypted. ___ kallithea-general mailing list kallithea-general@sfconservancy.org https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
Re: Issue reading configuration from .hg/hgrc inside project
On 4/21/21 1:50 PM, Mads Kiilerich wrote: On 4/21/21 2:09 AM, Felipe Cardoso Resende wrote: Hi, I'm experimenting with kallithea but I'm having trouble making it read from the .hg/hgrc inside the project. Looking through the history, I found the revision 802fdeefc8cc linking to Issue #246 [1] that changes how the configuration is read. I looked into mercurial.ui.ui.readconfig and it expects a filename instead of the repo_path. There is a Note there that seems to imply that .hg/hgrc will be read elsewhere, but I'm not that familiar with mercurial. Does anyone knows if its really a bug or if I'm missing something? Yes, it could seem like I made a mistake in https://kallithea-scm.org/repos/kallithea/changeset/f83326e2e66c . A fix has been pushed to the stable branch: https://kallithea-scm.org/repos/kallithea/changeset/c9834271cd066d4f734b0f7c56e94866057a789f Some additional cleanup in this area has been pushed to the default branch and will probably soon be released in 0.7 . Thanks for the report. /Mads ___ kallithea-general mailing list kallithea-general@sfconservancy.org https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
Re: Changing .ssh/authorized_keys script
On 5/19/21 4:21 PM, Louis Bertrand wrote: Hello, When I upgraded Kallithea, I somehow changed the venv directory from ~/kallithea-venv to kallithea/venv. In other words, instead of a venv directory beside the kallithea directory, it's now under the directory. Everything is fine except for ssh access because the cli script has moved. I updated the path kallithea_cli_path = /srv/web/sites/hg.set.durhamcollege.org/kallithea/venv/bin/kallithea-cli However the .ssh/authorized_keys file needs to be updated. There is a way to update authorized_keys. See the last section in https://kallithea.readthedocs.io/en/default/setup.html#using-kallithea-with-ssh : The ``authorized_keys`` file can be updated manually with ``kallithea-cli ssh-update-authorized-keys -c my.ini``. Is there a way to edit the file without invalidating it? (I'm not sure what is meant with "edit without invalidating" - is it "make it rewrite the file even though nothing changed that could trigger it"?) /Mads ___ kallithea-general mailing list kallithea-general@sfconservancy.org https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
