From 25b140fcc94a5b655ee130fd5cce1eaea38a89dc Mon Sep 17 00:00:00 2001 From: Lance Edgar Date: Sat, 15 Feb 2025 22:40:08 -0600 Subject: [PATCH] Add LilSnippets-DevSetup --- LilSnippets-DevSetup.-.md | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 LilSnippets-DevSetup.-.md diff --git a/LilSnippets-DevSetup.-.md b/LilSnippets-DevSetup.-.md new file mode 100644 index 0000000..de415c6 --- /dev/null +++ b/LilSnippets-DevSetup.-.md @@ -0,0 +1,34 @@ +# Setup for Development Environment + +**NOTE:** *Sorry, all this has only been tested on Linux, and some of the tooling used will almost certainly not work on Windows, so for now it's Linux or bust. And to get even more specific, things have only been tested on Debian and Ubuntu thus far.* + +Okay, with that out of the way, we know you have Python already. + +The only other requirement at this stage is [[https://virtualenvwrapper.readthedocs.io/en/latest/|virtualenvwrapper]]. There is more than one way to get that; really the important thing is where we wind up defining the "workon home" folder. For the sake of example, this should work: + +```sh +sudo apt-get install virtualenvwrapper +``` + +Next we'll prep the "workon home" folder a bit: + +```sh +sudo mkdir /srv/envs +sudo chown you:you /srv/envs +``` + +Please note, you're free to use a different path for that, but know that **all** docs for Rattail will assume `/srv/envs` as the workon home. + +Next you should edit your `~/.bashrc` and add the following: + +```sh +export WORKON_HOME=/srv/envs +source /usr/share/virtualenvwrapper/virtualenvwrapper.sh +``` + +Finally, you must logout and then log back in, or perhaps `source ~/.bashrc`, in order to cause virtualenvwrapper to create the initial hook scripts. + +At that point you should have access to some new commands, most important of which are: + + * `workon` + * `mkvirtualenv`