Skip to content

Conversation

@Ryuno-Ki
Copy link
Contributor

No description provided.

@kootenpv
Copy link
Member

I think we should probably move this to a separate README specifically for the details?

Btw, if you install sysdm in the same virtualenv before using sysdm d, then it will automatically work by just running sysdm create (as it automatically uses the already activated virtualenv/python)

@Ryuno-Ki
Copy link
Contributor Author

I did.
Dependencies for projects are installed in the same virtualenv as the project (to avoid conflicts between projects).
However, the target was outside the virtualenv.

I'm using the standardlib virtualenv command to create it (instead of one of the pipenv etc. out there).

@kootenpv
Copy link
Member

But so if you would install sysdm in that venv wouldn't it work then 🤔?

@Ryuno-Ki
Copy link
Contributor Author

🤷

I can tell with another package if you want me to.
Shall I split this PR into one part regarding the Exec stuff and one for enabling the service?

@kootenpv
Copy link
Member

Whatever is more convenient! I only saw the notification now :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants