Linux Installation - Permissions and Remotes #257
-
|
Hi everybody. I'm trying to set up git-source-control on 2023.1 on Ubuntu 22.04 (x64, not that it should matter) host. I've created a individual namespace directories under /isc/source/. I've set them all with irisusr:irisusr as the owner/group, and used the Configure() tool to set up each namespace to point to its respective directory. After performing an Init from the Interoperability DTL editor, I'm getting the error: warning: unable to access '/root/.config/git/ignore': Permission denied In both the source control output page when I add an class to source control and in a banner at the top of the WebUI page. I'm also not sure how to go about configuring remotes. I know I can configure them in VS Code, but does that somehow update the local repo so they can be interacted with from the DTL/Business Rule editor source control buttons? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Following up ... the issue with the "Permission denied" messages was apparently caused by the systemd service I'd created for running IRIS on startup (and shutting it down gracefully on system shutdown). Although IRIS was running as irisusr, the iris.service configuration started it in root's context and environment. That worked fine until I needed to do something that required irisusr's environment, like use git :/ Adding remotes was done in the linux shell, as linux user irisusr. They're all filesystem-based for now; nothing going to a remote repo in the cloud. Yet. Finally, seems like creating a bare repository for a remote and pushing to that works better than cloning. Not sure why that is. |
Beta Was this translation helpful? Give feedback.
Following up ... the issue with the "Permission denied" messages was apparently caused by the systemd service I'd created for running IRIS on startup (and shutting it down gracefully on system shutdown). Although IRIS was running as irisusr, the iris.service configuration started it in root's context and environment. That worked fine until I needed to do something that required irisusr's environment, like use git :/
Adding remotes was done in the linux shell, as linux user irisusr. They're all filesystem-based for now; nothing going to a remote repo in the cloud. Yet.
Finally, seems like creating a bare repository for a remote and pushing to that works better than cloning. Not sure why th…