[01:55] <greg-g> cmaloney: just to double check my thinking: for your pelican blog you have, which bits in git? just the content dir? or the whole pelican dir but excluding a bunch of stuff?
[02:05] <greg-g> did people see this? Next total solar eclipse in the US is in 7 years, really close to michigan: https://www.timeanddate.com/eclipse/map/2024-april-8#
[02:05] <greg-g> totality that is, A2 will get 98% coverage
[02:05] <greg-g> I think I need to plan a trip to Carrie's parents (in Chelsea) then drive down to Oberlin or something for the 4 minutes of totality
[02:05] <greg-g> we should all meet up :)
[02:06] <greg-g> what are YOU doing in 7 years? :P
[02:21] <_stink__> probably just dicking around on irc
[02:24] <greg-g> _stink__++
[12:28] <jrwren> greg-g: planning on similar if the world still exists in 2024. See you there.
[13:35] <greg-g> jrwren: word
[14:40] <brousch> jrwren: You did pretty well against your bees http://woodtv.com/2017/08/10/man-hospitalized-after-accidentally-setting-self-on-fire/
[14:41] <jrwren> lol, that idiot tried to kill a nest using fire. that is just foolish.
[15:15] <cmaloney> greg-g: We've already consoled ourselves with the next totality being in 7 years
[15:15] <cmaloney> :)
[15:15] <cmaloney> re: Pelican: I have it all in git, but I publish bia rsync
[15:15] <cmaloney> s/bia/via/
[15:16] <greg-g> cmaloney: the whole venv?
[15:16] <cmaloney> no, I have the venv in a separate dir
[15:16] <cmaloney> but that's how my home setup is
[15:16] <greg-g> can you give me an example?
[15:16]  * greg-g is inexperienced with real use of venvs
[15:17] <greg-g> (tell me if now isn't a good time, i can wait for delayed responses ;) )
[15:19] <cmaloney> Nah, it's alright
[15:19] <cmaloney> JoDee was just offered a full-time position at Mid Michigan Community College and we finished running hte numbers. She's not taking it.
[15:19] <cmaloney> so it's a little emotional over here
[15:19] <greg-g> Yay & :(
[15:19] <greg-g> totally, do your thing
[15:20] <greg-g> I'm happy she was offered the position though!
[15:20] <cmaloney> Yeah, they really want her, but I don't think she could grow the program the way they want
[15:20] <greg-g> :/
[15:20] <cmaloney> Oh totally. She's a God-Damn professional
[15:20] <cmaloney> but it's a small pond (mostly made up of locals and kids who majored in alcohol)
[15:21] <cmaloney> who flunked out of CMU
[15:21] <greg-g> got it
[15:21] <jrwren> bummer.
[15:21] <cmaloney> and that's not a way to grow an astronomy program
[15:22] <cmaloney> we ran the numbers and she'd have to pull more students from CMU
[15:22] <cmaloney> anywho, I have pelican in a directory
[15:22] <cmaloney> and I use a script called mkvirtualenv that keeps the venv in ~/.virtualenvs
[15:23] <cmaloney> but you could put the venv wherever you want
[15:23] <cmaloney> I prefer to keep venvs out of git repos though
[15:23] <cmaloney> because #1: Python venvs don't work across machines without effort, and b) git isn't great for binaries.
[15:24] <greg-g> yeah, that's what I was imagining (to keep it out) so I was just curious how to separate appropriately
[15:24] <cmaloney> So that's two strikes against putting the venv in git
[15:24] <cmaloney> one way would be to use .gitignore to ignore the venv directory
[15:25] <cmaloney> another would be to put the venev in .. from the pelican install
[15:25] <cmaloney> so it could be pelican_ve/pelican
[15:25] <greg-g> gotcha
[15:25] <greg-g> that last part makes more sense to me
[15:25] <cmaloney> where the binaries are in pelican_ve and the content is in pelican
[15:26] <cmaloney> that last part was how we deployed at Morpace
[15:26] <greg-g> cool
[15:26] <cmaloney> The only downside is you have to be careful if you decide to rebuild the ve
[15:26] <cmaloney> rm -rf ve directory is not going to end well. :)
[15:27] <cmaloney> and if you decide to script this using Ansible it can make things a little difficult
[15:27] <greg-g> right right
[15:28] <greg-g> I was starting down the path of puppetizing it, but, I stopped :)
[15:28] <cmaloney> Yeah
[15:28] <cmaloney> The only link you need between the ve directory and pelican is the environment activation
[15:28] <cmaloney> so it can live anywhere
[15:29] <cmaloney> Pelican uses a makefile for making content
[15:29] <cmaloney> so you can tell it where the Python EXE is by modifying the Makefile
[15:30] <greg-g> cmaloney: taha, this is helping so much man, thanks
[15:36] <cmaloney> np. Glad I can give some insight
[15:36] <cmaloney> I use this for three of my sites (decafbad.net, cinciclassic.org, and physastro.com)